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 the POST /v1/events ingestion path through a larger documented analytics-api service (mounted at ./code), a broad trace spanning many files. The criteria check the entry path, validation location, and storage write.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Traces ingest entry path",
"description": "Traces routes/ingest.ts -> services/ingestion.ts as the entry path",
"max_score": 8
},
{
"name": "Locates validation",
"description": "Locates validation in services/ingestion.ts via lib/validate.ts",
"max_score": 8
},
{
"name": "Locates storage write",
"description": "Locates the write at EventStore.insert in the selected store implementation",
"max_score": 8
}
]
}.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scripts