analyze
Analyze a collection of documents to build a knowledge map, identify themes, find gaps, duplicates, conflicts, and staleness, then produce an organized analysis with improvement recommendations. Designed for document ecosystems (cross-repo docs, research collections, mixed-format doc repos) where the challenge is understanding the landscape, not auditing against code.
npx skills add majiayu000/claude-skill-registry --skill analyze-tercel-spec-forge --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.
# Analyze — Document Landscape Analysis & Knowledge Mapping Map, understand, and evaluate a collection of documents as a body of knowledge. Identify structure, themes, gaps, redundancies, conflicts, and staleness. Produce an actionable analysis with reorganization recommendations. ## Core Principles 1. **Landscape-first**: Build the map before judging — understand what exists before critiquing 2. **Theme-driven**: Group documents by what they're about, not just where they live 3. **Conflict detection**: Find contradictions between documents that may confuse readers 4. **Staleness awareness**: Identify documents that may be outdated based on content signals 5. **Non-destructive**: Only reads and reports — never modifies source documents 6. **Reorganization as suggestion**: Propose better structures, don't impose them ## When to Use Analyze vs. Audit | Situation | Use | |-----------|-----| | Single project with docs/ and source code | `/spec-forge:audit` | | Docs-only repo with mixed content | `/spec-forge:analyze` | | Cross-repo documentation ecosystem | `/spec-forge:analyze` | | Research notes, ideas, decision records | `/spec-forge:analyze` | | API docs need checking against code
- Core Principles
- When to Use Analyze vs. Audit
- Workflow
- Step 1: Determine Scope
- Step 2: Document Discovery & Inventory
- Step 3: Theme & Cluster Analysis
- Step 4: Conflict & Contradiction Detection
- Step 5: Gap Analysis
- Step 6: Redundancy Detection
- Step 7: Staleness Assessment
- Step 8: Generate Analysis Report
- Step 9: Present Results
- Step 10: Follow-Up Actions (Optional)
- Notes
What does the analyze skill do?
Analyze a collection of documents to build a knowledge map, identify themes, find gaps, duplicates, conflicts, and staleness, then produce an organized analysis with improvement recommendations. Designed for document ecosystems (cross-repo docs, research collections, mixed-format doc repos) where the challenge is understanding the landscape, not auditing against code.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyze-tercel-spec-forge --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.