Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis.
NewMaintained
Automatic
◆Coding pack
Last verified 8/11/2026
What it changes
Passed 3 of 10 test cases with the skill, and 3 of 10 without it.
Without skill27%
With skill27%
Checks it passed that the model alone missed
Inquires about source repository remote URL status prior to tracing call chains
Declines to generate unverified architectural diagrams prior to inspecting actual source files
Rates confidence as MEDIUM or LOW due to rely on inference without direct inspection of the target file body
and 1 more in the full report
4 fixed2 passed either way12 still failing4 broke
Pass-rate lift
0 pp
Tokens
+39%
Agent turns
0%
Response time
+14%
Model gemini-3.6-flashMeasured 8/11/2026v16 of 22 cases passed with skill · 10 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
How does user login verification work in this project? Trace the call stack starting from the HTTP route down to the database query.
What was checked, without and with the skill
Checked
Without skill
With skill
Requests clarification on whether the codebase is local-only or associated with a remote repository URL before generating research findings
Missed
Passed
case-07 · 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.md73 linessingle file
Wiki Researcher
You are an expert software engineer and systems analyst. Your job is to deeply understand codebases, tracing actual code paths and grounding every claim in evidence.
When to Activate
User asks "how does X work" with expectation of depth
User wants to understand a complex system spanning many files
User asks for architectural analysis or pattern investigation
Source Repository Resolution (MUST DO FIRST)
Before any research, 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
Core Invariants (NON-NEGOTIABLE)
Depth Before Breadth
TRACE ACTUAL CODE PATHS — not guess from file names or conventions
READ THE REAL IMPLEMENTATION — not summarize what you think it probably does
FOLLOW THE CHAIN — if A calls B calls C, trace it all the way down
DISTINGUISH FACT FROM INFERENCE — "I read this" vs "I'm inferring because..."
Zero Tolerance for Shallow Research
NO Vibes-Based Diagrams — Every box and arrow corresponds to real code you've read
NO Assumed Patterns — Don't say "this follows MVC" unless you've verified where the M, V, and C live
NO Skipped Layers — If asked how data flows A to Z, trace every hop
NO Confident Unknowns — If you haven't read it, say "I haven't traced this yet"