S4h Analogy Boundary Testing
Finds where an analogy breaks down before it's relied upon. Analogies fail silently — the damage happens when decisions are made on a mapping that doesn't hold in the relevant dimension. Triggers: 'stress-test this analogy', 'where does this comparison break', 'does this really apply', 'test the metaphor', 'where is the analogy wrong'.
Install
npx skills add human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testinggit clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git /tmp/skills-for-humanity
mkdir -p ~/.claude/skills
cp -r /tmp/skills-for-humanity/skills/s4h-analogy-boundary-testing ~/.claude/skills/s4h-analogy-boundary-testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Analogy Boundary Testing Analogies are tools, not truths. The danger is not using an analogy — it is using one past its boundary. Analogies fail silently: the flaw is invisible until a decision has been made that depended on the part that didn't hold. This skill finds the boundary before that happens. --- ## Your Process **Step 1: State the Analogy** Write it explicitly: "X is like Y." Name the analogy being tested, the domain it comes from, and the claim being made on the basis of it. **Framing check:** Confirm the specific analogy before continuing. State what you've identified — the source domain, target domain, and the claim being made — in one sentence, then use `AskUserQuestion`: - **Question:** "I'm reading this as: [your one-sentence framing of the analogy and the claim it supports]. Is that right?" - **Header:** "Framing" - **Options:** - **Yes — proceed** — framing is correct - **Adjust** — one element is off; user will correct it before you continue - **Reframe** — different analogy or claim than read; incorporate the correction before proceeding **Step 2: List Similarities** What does the analogy capture correctly? List every genuine parallel — the aspects where the structural correspondence is real. This is not validation; it's establishing what the analogy is good for before finding what it isn't. **Step 3: List Differences** Every meaningful divergence between X and Y is a potential failure point. List them
Details
- Skill name
s4h-analogy-boundary-testing- Repository
- human-avatar/skills-for-humanity
- Path
skills/s4h-analogy-boundary-testing/SKILL.md- License
- MIT
- Repo updated
- 15 July 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the S4h Analogy Boundary Testing skill do?
Finds where an analogy breaks down before it's relied upon. Analogies fail silently — the damage happens when decisions are made on a mapping that doesn't hold in the relevant dimension. Triggers: 'stress-test this analogy', 'where does this comparison break', 'does this really apply', 'test the metaphor', 'where is the analogy wrong'.
How do I install the S4h Analogy Boundary Testing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is S4h Analogy Boundary Testing popular?
It lives in human-avatar/skills-for-humanity, which has 242 GitHub stars and 25 forks, and is included in 1 curated skill list.
Related skills
S4h
242human-avatar/skills-for-humanity
Master orchestration skill. Takes any situation in plain English, identifies the underlying goal, designs a multi-skill reasoning workflow, and executes it sequentially — feeding each skill's output into the next. Use when you say 'help me think through this', 'I need to figure out what to do', 'where do I start', or any time you want structured thinking applied end-to-end rather than routed to a single tool.
S4h Aesthetic
242human-avatar/skills-for-humanity
Entry point for the aesthetic toolkit. Routes to the right aesthetic skill based on your situation. Use when you say 'aesthetic', 'check the design', 'does this feel right', 'is this elegant', 'is this too complex', 'what pattern is this', 'find the simpler version', or want an aesthetic lens applied without knowing which specific tool fits.
S4h Aesthetic Coherence Check
242human-avatar/skills-for-humanity
Tests whether the parts of something form a unified whole — finding the jarring inconsistencies that accumulate when different contributors work without a shared vision. TRIGGERS: 'coherence check', 'does this feel unified', 'something feels off', 'inconsistent', 'check the whole', 'does this hang together'.
S4h Analogy Structure Mapping
242human-avatar/skills-for-humanity
Identifies the deep structural correspondence between two situations — genuine isomorphism vs superficial similarity. Triggers: 'does this analogy hold', 'map the structure', 'is this really like that', 'structural similarity', 'test the comparison'.
S4h Aesthetic Elegance Testing
242human-avatar/skills-for-humanity
Tests whether a solution is more complex than it needs to be — distinguishing necessary complexity from accidental complexity that accreted over time. TRIGGERS: 'elegance test', 'is this too complex', 'over-engineered', 'is there a simpler way', 'does this feel right'.
S4h Constraint Hardness Testing
242human-avatar/skills-for-humanity
Tests whether a stated constraint is real — distinguishing genuine limits from assumptions, habits, or politics dressed as facts. Triggers: 'is this really a constraint', 'challenge the assumption', 'who says we can't', 'is this actually fixed', 'test the constraint'.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.