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 determines the rate-limiting scope and locates its implementation in a documented analytics-api service (mounted at ./code). This is a pinpoint single-file question.",
"type": "weighted_checklist",
"checklist": [
{
"name": "States per-API-key scope",
"description": "States that rate limiting is per-API-key (a token bucket keyed by API key), not global",
"max_score": 8
},
{
"name": "Identifies implementation file",
"description": "Identifies middleware/rateLimit.ts as the implementation",
"max_score": 8
}
]
}.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scripts