CtrlK
BlogDocsLog inGet started
Tessl Logo

brain-taxonomist

Filing gate for ALL brain writes. Consulted before creating any new brain page to determine the correct path. Reads the ACTIVE schema pack via `gbrain schema show --json` — no hardcoded directory table. Also runs periodic taxonomy drift detection via `gbrain schema review-orphans`.

61

Quality

72%

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 ./skills/brain-taxonomist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with a clear, validated decision workflow, but it is a long monolithic document with notable internal repetition and no bundle files to offload detail, capping conciseness and progressive disclosure.

Suggestions

Collapse the repeated 'no hardcoded directory table' rationale into a single Hard Rules entry and reference it elsewhere rather than restating it four times.

Move the book sub-category enumeration and drift-detection command details into a reference bundle file (e.g. references/drift-detection.md) and link to it one level deep to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The ~175-line body is mostly domain-specific and useful, but restates the 'no hardcoded directory table' point across Contract, Critical, Anti-Patterns, and Hard Rules and includes light over-justification, so it could be tightened — anchor 2.

2 / 3

Actionability

Provides concrete executable commands ('gbrain schema show --json | jq ...', 'gbrain schema review-orphans --json', 'gbrain doctor --json | jq ...'), a numbered decision protocol, output templates, and a validation checklist — copy-paste ready, anchor 3.

3 / 3

Workflow Clarity

The 5-step Decision Protocol has an explicit validation checklist (Step 5) and an error-recovery branch (no match -> signal EIIRP Phase 3, not closest-fit), plus a drift-detection feedback loop — anchor 3.

3 / 3

Progressive Disclosure

No bundle files exist and the ~175-line body is a monolithic SKILL.md; sections are well-organized but content that could be split (book sub-categories, drift details) is inline with no one-level-deep reference files — anchor 2.

2 / 3

Total

10

/

12

Passed

Description

67%

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 concrete and distinctive, naming specific CLI actions and a clear niche, but its natural-language triggers are segregated into the triggers array so the description text alone is weaker on trigger coverage and explicit 'when' guidance.

Suggestions

Fold one or two natural user phrasings (e.g. 'Use when deciding where a new brain page goes') into the description itself so trigger coverage does not depend solely on the triggers array.

Add an explicit 'Use when...' clause to the description to satisfy the completeness trigger requirement without relying on the separate triggers field.

DimensionReasoningScore

Specificity

Quotes 'Filing gate for ALL brain writes', 'determine the correct path', 'Reads the ACTIVE schema pack via gbrain schema show --json', and 'runs periodic taxonomy drift detection via gbrain schema review-orphans' — multiple concrete, tool-backed actions matching anchor 3.

3 / 3

Completeness

The 'what' is explicit (filing gate, drift detection) and 'when' is only implied via 'Consulted before creating any new brain page'; the explicit 'Use when...' trigger clause sits in the triggers array, so per the guideline completeness caps at 2.

2 / 3

Trigger Term Quality

The description carries some relevant keywords ('brain page', 'filing') but the natural user phrasings live in the separate triggers array rather than the description text itself, leaving common variations missing — anchor 2.

2 / 3

Distinctiveness Conflict Risk

Highly specific niche ('brain writes', 'ACTIVE schema pack', gbrain tooling) makes it clearly distinguishable and unlikely to fire for the wrong skill — anchor 3.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
garrytan/gbrain
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.