Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Analyzes a repository's structure, architecture, and conventions through six phases: discovery, architecture mapping, pattern recognition, key file identification, guide generation, and interactive Q&A. Produces an annotated directory tree, ASCII architecture diagram, data flow traces, and a Day 1 checklist tailored to the specific project. Works on any language or stack.
Produces structured, actionable output (architecture diagrams, data flow traces, common task recipes, complexity ratings) rather than just summarizing README files or listing directory contents.
When to use it
- Onboarding a new hire to a large undocumented codebase
- Getting oriented in an open-source project before submitting a first PR
- Generating a handoff document before leaving a team
- Auditing a repository for tech debt and complexity hotspots
- Re-orienting to a codebase after an extended absence
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Can you onboard me to this repository?
- 1Detects languages and frameworks from manifest files (package.json, go.mod, Cargo.toml, etc.)
- 2Classifies the project type and identifies entry points and the boot sequence
- 3Generates an annotated directory tree and ASCII architecture diagram
- 4Traces primary data flows and identifies design patterns, naming conventions, and error handling style
- 5Outputs a structured onboarding guide with a project-specific Day 1 checklist and common task recipes
A complete onboarding document covering architecture, key files, data flows, gotchas, tech debt hotspots, and copy-paste setup commands