Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →borghei/code-tour
Build ordered, annotated tours of an unfamiliar codebase and keep the anchors from rotting.
Passed 14 of 19 test cases with the skill, and 5 of 19 without it.
and 12 more in the full report
10 fixed6 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
After inspecting a drifted tour and confirming that all 'why' notes remain correct despite minor function body refactoring, we want to update the stored line numbers and content fingerprints in the tour file. Which flag should be passed to the validation script?
| Checked | Without skill | With skill |
|---|---|---|
| Passes `--update` to tour_validate.py | Missed | Passed |
| Re-freezes line numbers and symbol fingerprints in the tour definition file | Missed | Passed |
The instructions your model reads when the skill loads.
A guided path through a codebase, ordered so each stop makes the next one legible, and annotated with why the code is the way it is rather than what it does. The what is already on screen; the why is what takes a new engineer three weeks to reconstruct and what the person who knows it will lose in six months. Tours rot faster than any other documentation because they point at line numbers, so anchoring and validation are half this skill.
Before building the tour, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
test cases passed, vs 5 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.