using-system-archaeologist
Use when analyzing existing codebases to generate architecture documentation - coordinates subagent-driven exploration with mandatory workspace structure, validation gates, and pressure-resistant workflows
npx skills add majiayu000/claude-skill-registry --skill using-system-archaeologist --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.
# System Archaeologist - Codebase Architecture Analysis ## Overview Analyze existing codebases through coordinated subagent exploration to produce comprehensive architecture documentation with C4 diagrams, subsystem catalogs, and architectural assessments. **Core principle:** Systematic archaeological process with quality gates prevents rushed, incomplete analysis. --- ## Context Conservation (CRITICAL) **You are a COORDINATOR, not an analyst.** Your primary context is precious - preserve it for orchestration decisions, not detailed code reading. ### The Delegation Imperative | Task Type | Your Role | Subagent Role | |-----------|-----------|---------------| | Subsystem analysis | Spawn `codebase-explorer` | Read files, produce catalog entries | | Validation | Spawn `analysis-validator` | Check contracts, produce reports | | Diagram generation | Spawn diagram subagent | Generate Mermaid/PlantUML | | Quality assessment | Spawn quality subagent | Analyze patterns, produce assessment | | Security surface | Spawn security subagent | Map boundaries, flag concerns | ### What You DO (Coordinator): - Create workspace and coordination plan - Make orchestration decisions (parallel vs sequent
- Overview
- Context Conservation (CRITICAL)
- The Delegation Imperative
- What You DO (Coordinator):
- What You DO NOT Do (Delegate Instead):
- Rationalization Blockers
- When to Use
- How to Access Reference Sheets
- Mandatory Workflow
- Step 1: Create Workspace (NON-NEGOTIABLE)
- Step 1.5: Offer Deliverable Menu (MANDATORY)
- Step 2: Write Coordination Plan
- Step 3: Holistic Assessment First
- Step 4: Subagent Orchestration Strategy
mkdir -p docs/arch-analysis-$(date +%Y-%m-%d-%H%M)/temp
What does the using-system-archaeologist skill do?
Use when analyzing existing codebases to generate architecture documentation - coordinates subagent-driven exploration with mandatory workspace structure, validation gates, and pressure-resistant workflows
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill using-system-archaeologist --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.