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 locates the file and rule that rewrites client-supplied timestamps in a documented analytics-api service (mounted at ./code). This is a pinpoint single-file question.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Identifies responsible file",
"description": "Identifies services/enrichment.ts as responsible for the timestamp behaviour",
"max_score": 8
},
{
"name": "States the rule",
"description": "States the rule: the server assigns an authoritative timestamp that overrides the client-supplied one (the client time is kept only for drift)",
"max_score": 8
}
]
}.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scripts