examples-audit
Analyze mock data and examples for cultural assumptions, understanding what they communicate about who the product is for. Use when reviewing test data, documentation, or seed data.
npx skills add majiayu000/claude-skill-registry --skill examples-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Examples Audit Analyze mock data and examples for cultural assumptions, with emphasis on understanding what these choices communicate. ## Philosophy This is not about finding "Christmas" and replacing it with "holiday". It's about asking: > "What do our examples say about who we think our users are?" Every example is a choice. When your demo shows a user ordering a hamburger for their Christmas party, paying with a credit card, and shipping to their house in California, you're painting a picture of your "default user." Everyone else is an edge case. ## Scope The user may specify a file path, glob pattern, or directory. If not specified, ask what they'd like to check. ## 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, don't flag US address examples) 4. **Note** at the top of output: "Config loaded: .inclusion-config.md" ## Process ### 1. Read and Understand First, **read the content** to understand: - What is this? (test data, documentation, marketing, UI copy) - Who s
- Philosophy
- Scope
- Config Integration
- Process
- 1. Read and Understand
- 2. Look for Patterns
- 3. Understand the Assumptions
- 4. Assess Impact
- Reference
- Output Format
- What Makes This Different From a Linter
What does the examples-audit skill do?
Analyze mock data and examples for cultural assumptions, understanding what they communicate about who the product is for. Use when reviewing test data, documentation, or seed data.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill examples-audit --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.