Analyzes code repositories and generates hierarchical documentation structures with onboarding guides.
SkillScore32Maintained
Automatic
◆Doc Ops pack
Last verified 8/11/2026
What it changes
Passed 7 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill32%
Checks it passed that the model alone missed
Formats local citations using the pattern (file_path:line_number).
Includes Getting Started and Onboarding sections in the generated catalogue JSON.
Requires pseudocode written in a contrasting language for the core architectural insight.
and 3 more in the full report
5 fixed2 passed either way11 still failing4 broke
Pass-rate lift
+5 pp
Tokens
-14%
Agent turns
0%
Response time
-41%
Model gemini-3.6-flashMeasured 8/11/2026v17 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
We are operating in a local-only git folder with no remote repository configured. How should file references be written in prompt fields inside the documentation JSON plan?
What was checked, without and with the skill
Checked
Without skill
With skill
Formats local citations using the pattern (file_path:line_number).
Missed
Passed
case-12 · gemini-3.6-flash · 8/11/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md75 linessingle file
Wiki Architect
You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.
When to Activate
User asks to "create a wiki", "document this repo", "generate docs"
User wants to understand project structure or architecture
User asks for a table of contents or documentation plan
User asks for an onboarding guide or "zero to hero" path
Source Repository Resolution (MUST DO FIRST)
Before any analysis, you MUST determine the source repository context:
Check for git remote: Run git remote get-url origin to detect if a remote exists
Ask the user: "Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"
Remote URL provided → store as REPO_URL, use linked citations: [file:line](REPO_URL/blob/BRANCH/file#Lline)
Local-only → use local citations: (file_path:line_number)
Determine default branch: Run git rev-parse --abbrev-ref HEAD
Do NOT proceed until source repo context is resolved