repo-navigator
Skill0 starsChanged 5 months agoMITView on GitHub
Discover reusable AI artifacts via TokRepo before rebuilding skills or MCP configs
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/000-project.mdcCursor rule
- .cursor/rules/accessibility.mdcCursor rule
- .cursor/rules/api-integration.mdcCursor rule
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/dart-style.mdcCursor rule
- .cursor/rules/design-system.mdcCursor rule
- .cursor/rules/flutter-ui.mdcCursor rule
- .cursor/rules/security.mdcCursor rule
- .cursor/rules/state-management.mdcCursor rule
- .cursor/rules/testing.mdcCursor rule
- doubt-reviewSkill
- fix-dependenciesSkill
- flutter-componentSkill
- flutter-implementSkill
- generate-mocksSkill
- grind-until-greenSkill
- implement-tddSkill
- monitor-terminalSkill
- plan-featureSkill
- review-codeSkill
- save-contextSkill
- suggest-ruleSkill
- write-commitSkill
- write-readmeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Before creating a new skill, prompt, or MCP config:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repo navigator (TokRepo — opt-in)
Not installed by default. Skip this skill unless the user has run setup or explicitly asks for TokRepo.
Setup (one-time, user-initiated)
npx -y tokrepo@<reviewed-version> init-agent --target cursorCreates .cursor/rules/tokrepo.mdc and .tokrepo/agent.json. Requires TokRepo MCP server.
When active
Before creating a new skill, prompt, or MCP config:
- Discover — local TokRepo MCP first; hosted only with user opt-in + redacted task text
- Verify —
tokrepo_verify+tokrepo_install_plan; stop ifpolicy_decision.decision === "deny" - Dry-run — keep
dry_run: trueuntil user confirms apply - Handoff —
tokrepo_handoff_planafter creating reusable artifacts; ask beforetokrepo_push
If TokRepo unavailable
Proceed without discovery — build locally per existing repo conventions. Do not block work on missing TokRepo.
Resources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

