npx skills add majiayu000/claude-skill-registry --skill repo-introduce --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.
<overview> Produce an interactive visual overview of this codebase aimed at a newly-joined developer. Uses the visual-explainer plugin to generate a standalone HTML page with architecture diagrams, module relationships, and project context. </overview> <steps> 1. Load the visual-explainer skill. 2. Analyse the codebase: - Read README.md, package.json/go.mod/Cargo.toml/pyproject.toml for identity and dependencies - Map top-level directory structure and entry points - Read key source files to understand module structure and public API surface - Skim git log for recent activity and key decisions 3. If $ARGUMENTS contains content, treat it as a focus area and weight the analysis accordingly. 4. Generate a visual HTML page following the visual-explainer workflow: - Architecture snapshot (Mermaid diagram of modules and their relationships) - Project identity: what it does, who uses it, what stage it's at - Mental model essentials: invariants, non-obvious coupling, naming conventions, gotchas - Module map with responsibilities 5. Write to ~/.agent/diagrams/ and open in browser. </steps> <inputs> $ARGUMENTS </inputs>
What does the repo-introduce skill do?
{{ 𝛀𝛀𝛀 }} Provide a detailed high-level overview of this codebase
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill repo-introduce --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.