Context-efficient codebase navigation and documentation using structured frontmatter headers. Use this when exploring an unfamiliar codebase, answering "where is X / how does Y work" questions, or when asked to add/maintain file-level documentation. Index a tree's headers in one pass instead of reading every file, and generate or validate frontmatter with the bundled scripts. Reach for it whenever token budget matters while navigating code, even if the user does not say "frontmatter".
71
100%
Does it follow best practices?
Impact
52%
4.33xAverage score across 7 eval scenarios
Passed
No known issues
{
"context": "The agent traces a short-link visit through a small documented TypeScript project (mounted at ./code). The criteria check whether it follows the request path and correctly locates the click increment in the store layer.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Traces server then shortener",
"description": "Traces the path through server.ts (the GET handler) then shortener.ts (resolve)",
"max_score": 8
},
{
"name": "Locates click increment in store",
"description": "Correctly locates the click increment in the store layer (incrementClicks in store.ts / store-redis.ts), called from Shortener.resolve",
"max_score": 8
}
]
}.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scripts