Individual skill
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'.
skills/s4h-analogy-boundary-testing/SKILL.md
Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 241
- Repository last updated
- Jul 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- cognitive-frameworks Repository topic
- creativity Repository topic
- decision-making Repository topic
- ethics Repository topic
- mental-models Repository topic
- problem-solving Repository topic
- reasoning Repository topic
- systems-thinking Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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.