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 small documented TypeScript project (mounted at ./code) to find where to add a Postgres storage backend. The criteria check whether it identifies the interface file, the implementation to model on, and the wiring file — ideally from frontmatter headers without reading every file body.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Names interface file",
"description": "Names store.ts as the file defining the interface to implement (LinkStore)",
"max_score": 8
},
{
"name": "Names implementation to model on",
"description": "Identifies store-redis.ts as the existing implementation to model the new backend on",
"max_score": 8
},
{
"name": "Names wiring file",
"description": "Identifies server.ts as where the store is constructed/wired up at startup",
"max_score": 8
}
]
}.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scripts