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 navigates a larger documented analytics-api service (mounted at ./code) to find where to add a DynamoDB backend. This is a broad question frontmatter should answer from headers without reading the whole tree.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Names interface file",
"description": "Names store/store.ts as defining the EventStore interface to implement",
"max_score": 8
},
{
"name": "Names template implementation",
"description": "Identifies a store-* implementation (e.g. store-postgres.ts) as the template to copy",
"max_score": 8
},
{
"name": "Names wiring file",
"description": "Identifies server.ts as where the backend is selected/wired at startup",
"max_score": 8
}
]
}.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scripts