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 adds code-frontmatter headers to an undocumented TypeScript project (mounted at ./code). The criteria check coverage of substantive files, validity of the blocks (parse, purpose present, related paths resolve), and that purposes are specific rather than generic.",
"type": "weighted_checklist",
"checklist": [
{
"name": "All substantive files covered",
"description": "Every substantive source file (codec, store, store-redis, validate, config, shortener, server) gains a frontmatter block",
"max_score": 8
},
{
"name": "Blocks are valid",
"description": "Each frontmatter block is valid: it parses, has a purpose line, and its `related` paths resolve to real files — it would pass the skill's `validate` script with zero issues",
"max_score": 8
},
{
"name": "Purposes accurate and specific",
"description": "Purposes are accurate and specific to each file, not generic restatements of the filename",
"max_score": 6
}
]
}.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scripts