Agent skill · Testing & QA

test-assumption

Identify hidden assumptions about users in code that could exclude or harm. A focused analysis asking "What am I assuming about the person using this?

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill test-assumption --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Allowed tools: ReadGrepGlob
Path: skills/analysis/test-assumption/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Test of Assumption A focused analysis to identify hidden assumptions about users that could exclude or harm them. ## Philosophy Every line of code makes assumptions about who will use it. Most assumptions are invisible to the people making them because they match the developer's own experience. > "What am I assuming about the person using this?" This skill makes the invisible visible. Not to judge—but to **see** who we might be leaving out. ## Scope The user may specify a file path, glob pattern, or directory. If not specified, ask what they'd like to analyze. ## Config Integration Before starting, check for `.inclusion-config.md` in the project root. If it exists: 1. **Read** scope decisions and acknowledged findings 2. **Skip** acknowledged findings (note them in output) 3. **Respect** scope decisions (e.g., if US-only, certain location assumptions are intentional) 4. **Note** at the top of output: "Config loaded: .inclusion-config.md" Core dignity checks always run regardless of config. ## Process ### 1. Read and Understand First, **read the code** to understand: - What does this code do? - Who sees or uses this? (developers? end users? both?) - What's the context? (onboarding

What's inside
Steps it walks through
  1. Philosophy
  2. Scope
  3. Config Integration
  4. Process
  5. 1. Read and Understand
  6. 2. Identify Assumptions
  7. 3. Evaluate Each Assumption
  8. 4. Prioritize
  9. Output Format
  10. The Guiding Question
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the test-assumption skill do?

Identify hidden assumptions about users in code that could exclude or harm. A focused analysis asking "What am I assuming about the person using this?

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill test-assumption --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going