CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

functional-area-resolver

Compress an agent's routing file (RESOLVER.md or AGENTS.md) by converting granular skill-per-row tables into functional-area dispatchers. Each area lists sub-skills in a "(dispatcher for: ...)" clause. The LLM reads one area entry and routes to the correct sub-skill. Proven via held-out A/B eval: dispatcher pattern outperforms naive pipe-table compression.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugin-variants/gbrain-coding/skills/functional-area-resolver/SKILL.md

The canonical home for this skill is functional-area-resolver in garrytan/gbrain

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplar of actionable, well-gated workflow writing: concrete commands, numeric pass/fail thresholds, and revert-and-retry loops around a mutating operation. Its weaknesses are token efficiency and file structure — a large evidence-and-citations section that serves persuasion rather than execution is inlined in an already long single file.

Suggestions

Move the A/B Eval Results tables, methodology caveats, and prior-work citations into a one-level-deep reference file (e.g., references/eval-results.md, alongside the existing evals README), leaving a 3-5 line summary with the headline numbers (98-100% lenient accuracy at 48% size) and a link in SKILL.md.

Trim the "Why It Works" and "What the data shows" prose to the operative conclusions — the two-layer dispatch principle and 'the (dispatcher for: ...) clause is load-bearing' — since the numbered data analysis restates what the tables show.

Cut the changelog entry's rename history and the Contract section's restatement of body content ('this section exists for the conformance test'), keeping only what an executing agent needs at runtime.

DimensionReasoningScore

Conciseness

The instructional core (Steps 1-7, Anti-Patterns, Maintenance) is tight and earns its tokens, but roughly 90 lines of A/B eval tables, "What the data shows" analysis, methodology caveats, and a literature review (AnyTool, RAG-MCP) are justification for the pattern rather than instructions for executing it, and the eval detail duplicates content the referenced evals README already carries.

3 / 5

Actionability

Guidance is fully executable: exact byte thresholds ("under 12KB"), a copy-paste entry template, `gbrain routing-eval --json`, and a complete two-command harness invocation with env var, --variants-dir setup, and the cost-approval --yes flow; the common cases (single fat file, two fat files, gate failures) are each covered.

5 / 5

Workflow Clarity

Seven explicitly sequenced steps with preconditions that refuse to proceed (size gate, clean-tree gate), two mandatory verification gates with numeric thresholds (95%), explicit revert-and-tune feedback loops, enumerated failure causes, and a final user-approval checkpoint before committing — the strongest anchor's checklist-and-recovery pattern.

5 / 5

Progressive Disclosure

Section structure and headers are clear, and external pointers (evals README, agent-operator-protocol.md) are properly linked, but no bundle files exist and heavy reference-grade material — the full A/B eval tables, methodology caveats, and citations survey — is inlined in SKILL.md where the rubric expects it split into a one-level-deep reference file.

3 / 5

Total

16

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, third-person, and tightly scoped to a distinct niche with concrete named artifacts. Its one material weakness is that the description field itself never states when to invoke the skill, deferring trigger guidance to separate frontmatter fields.

Suggestions

Append a 'Use when...' clause to the description field with concrete trigger phrases (e.g., 'Use when the user says "compress agents.md", "resolver too big", or asks to shrink a routing table') so completeness answers both what and when.

Replace the 'Proven via held-out A/B eval' meta-commentary with the compression preconditions (file over 12KB) to make the capability boundary explicit rather than citing evidence.

Fold one or two natural user phrasings ('too big', 'shrink routing table') into the description text itself so trigger matching does not depend solely on the separate triggers list.

DimensionReasoningScore

Specificity

Concrete actions are named with specific artifacts — "Compress an agent's routing file (RESOLVER.md or AGENTS.md) by converting granular skill-per-row tables into functional-area dispatchers" and "Each area lists sub-skills in a '(dispatcher for: ...)' clause" — but coverage stops at the compression transform itself, omitting verification gates and multi-file handling that the body implements.

4 / 5

Completeness

The "what" is explicit and concrete, but the description text contains no "Use when..." clause or equivalent trigger guidance — the "Proven via held-out A/B eval" sentence is evidence commentary, not usage timing — so completeness caps at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage for the domain — "compress", "routing file", "RESOLVER.md", "AGENTS.md", "dispatcher", "skill-per-row tables" — with both file-name synonyms present, though common user phrasings like "too big", "shrink", or "routing table" appear only in the separate when_to_use/triggers fields, not the description.

4 / 5

Distinctiveness Conflict Risk

A clear niche — compressing routing files (RESOLVER.md/AGENTS.md) into functional-area dispatchers — with named file artifacts that no plausible sibling skill would claim; conflict risk is minimal.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

plugin-variants/gbrain-coding/skills/functional-area-resolver/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.