Stress Test Analogy

Stress-tests a proposed analogy by finding the edge where the mapping breaks, then frames that break as a teaching opportunity the writer can fold into the post. Every analogy has a boundary; the writer's style treats that boundary as a feature. Use after generate-analogy-set and map-analogy-to-concept, for each framing. Trigger keywords — where does it break, stress-test, boundary, edge case, fold the break, analogy limits.

200 stars 25 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill stress-test-analogy
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/stress-test-analogy ~/.claude/skills/stress-test-analogy

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Stress Test Analogy

## Table of Contents

- [Workflow](#workflow)
- [Where-it-breaks taxonomy](#where-it-breaks-taxonomy)
- [Worked example](#worked-example)
- [Guardrails](#guardrails)

**Related skills:** Called by the Intuition Builder per framing. Input is one framing (source + target + mapping from `map-analogy-to-concept`). Output feeds the final artifact's "Where it breaks" section for each framing and the Technical Reviewer's `flag-boundary-break` on drafts.

## Workflow

```
For one framing (source → target + mapping):
- [ ] Step 1: Identify the mapping's weakest link — which source-component-to-target-component pairs are forced?
- [ ] Step 2: Generate 2-3 edge cases where the forced pair fails
- [ ] Step 3: Write the boundary as one or two sentences — specific and named
- [ ] Step 4: Propose a "fold" — how the writer turns this break into content in the draft
- [ ] Step 5: Rate fold value: high | medium | low (high = the break is its own paragraph or sub-section)
```

### Step 3: Boundary phrasing

The boundary sentence should be specific enough that the reader could verify it. Good: "The drawer metaphor implies physical contiguity in memory, but a KV cache is logically indexed, not physically contiguous." Bad: "The analogy doesn't quite work at scale."

### Step 4: The fold
Read the full skill on GitHub

Details

Skill name
stress-test-analogy
Path
skills/stress-test-analogy/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Stress Test Analogy skill do?

Stress-tests a proposed analogy by finding the edge where the mapping breaks, then frames that break as a teaching opportunity the writer can fold into the post. Every analogy has a boundary; the writer's style treats that boundary as a feature. Use after generate-analogy-set and map-analogy-to-concept, for each framing. Trigger keywords — where does it break, stress-test, boundary, edge case, fold the break, analogy limits.

How do I install the Stress Test Analogy skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Stress Test Analogy popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Symmetry Validation Suite

200

lyndonkl/claude

Provides empirical test protocols and metrics to validate whether hypothesized symmetries actually hold in data or models before committing to equivariant architecture. Includes invariance/equivariance testing, group structure verification, and distribution analysis under transforms. Use when testing invariance, validating equivariance, checking symmetry assumptions, debugging symmetry-related model failures, or needing data-driven validation before architecture decisions.

Testing & QA25

Scout Mindset Bias Check

200

lyndonkl/claude

Detects and removes cognitive biases from reasoning using Julia Galef's Scout Mindset framework. Provides reversal tests, scope sensitivity checks, status quo bias tests, confidence interval audits, and full bias audits. Use when a prediction feels emotional, stuck at 50/50, or when validating forecasting process. Use when user mentions scout mindset, soldier mindset, bias check, reversal test, scope sensitivity, or cognitive distortions.

Testing & QA25

Synthesis and Analogy

200

lyndonkl/claude

Synthesizes information from multiple sources into coherent insights and applies analogical reasoning to transfer knowledge across domains. Use when conducting literature reviews, integrating stakeholder feedback, reconciling conflicting viewpoints, identifying cross-source patterns, creating explanatory analogies ("X is like Y"), finding creative solutions through cross-domain transfer, or testing whether analogies hold (surface vs deep). Use when user mentions "synthesize", "combine sources", "analogy", "similar to", "transfer from", "integrate findings".

Testing & QA25

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.