Design or audit a repo-local markdown knowledge graph with wiki links, source-code backlinks, drift checks, and searchable sections.
SkillScore96Maintained
Automatic
◆Knowledge Management pack
Last verified 8/18/2026
What it changes
Passed 22 of 23 test cases with the skill, and 14 of 23 without it.
Without skill61%
With skill96%
Checks it passed that the model alone missed
Recommends resolving links bi-directionally where needed
Recommends interlinking concept pages using wiki link syntax
Recommends CI checks for test specifications lacking code mentions
and 6 more in the full report
8 fixed14 passed either way1 still failing0 broke
Pass-rate lift
+35 pp
Tokens
-12%
Agent turns
0%
Response time
-28%
Model gemini-3.6-flashMeasured 8/18/2026v122 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
We use a global catalog tool like ctx for recommending skills and MCPs across all repositories. Where should project-specific architecture decisions and business rules be stored?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends storing repo-specific facts in a repo-local knowledge graph
Missed
Passed
case-09 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md40 linessingle file
lat.md Knowledge Graph
Purpose
Turn durable project knowledge into linked markdown files that agents can
search, cite, and keep synchronized with code.
When to Use
One root instruction file is too large or hides domain decisions.
Agents repeatedly rediscover the same architecture or business rules.
Test intent needs explicit specs linked to test code.
A custom harness needs persistent memory outside conversation history.
Design Pattern
Create a repo-local knowledge directory such as lat.md/ or docs/knowledge/.
Split pages by durable concepts: architecture, domain rules, workflows,
interfaces, test specs, and operational constraints.
Link concepts with [[wiki links]].
Link knowledge pages to source symbols or files.
Add code backlinks such as comments or metadata where the code implements a
documented rule.
Add a check that fails on broken links, missing backlinks, stale indexes, or
test specs without code mentions.
ctx Fit
Use this alongside ctx's LLM-wiki when a project needs its own local memory
graph. ctx recommends skills/MCPs/agents from its catalog; the repo-local graph
stores project-specific facts that should not live in the global catalog.
Quality Bar
Page titles and section anchors are stable.
Links resolve both ways where needed.
Code backlinks are narrow and reviewable.
Checks run in CI before merge.
Sensitive facts stay out unless the repo already allows them.
The graph explains current behavior, not a speculative roadmap.