CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gbrain-advisor

Proactive "make the most of gbrain" coaching. Runs `gbrain advisor` on a cadence and pings the user with the top high-leverage actions for their brain: version drift, pending migrations, stalled jobs, low embed coverage, setup smells, and uninstalled brain skills. Read-only; always asks before fixing.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A lean, highly actionable body: exact commands, a numbered workflow with explicit validation and error-recovery routing, and a concrete output format. The only deductions are minor — the ask-first rule is restated in several sections, and the referenced convention files are not part of the bundle.

Suggestions

Consolidate the ask-before-fixing rule, which appears in Contract, findings step 5, Output Format, and Anti-Patterns, into one authoritative statement plus a single back-reference to save tokens.

Ensure the referenced convention files (`skills/conventions/brain-first.md`, `../conventions/agent-operator-protocol.md`) ship with or resolve from the skill's location, since no bundle files accompany SKILL.md.

DimensionReasoningScore

Conciseness

The body is efficient — exact commands (`gbrain advisor --json`, `gbrain advisor --apply <dispatch_id>`), exit-code semantics, and a compact JSON payload schema with no explanation of concepts Claude already knows. It is not a 5 because the ask-before-fixing rule is repeated in four places (Contract, findings step 5, Output Format, Anti-Patterns), which could be trimmed to one authoritative statement; it is well above a 3 since nearly every token earns its place.

4 / 5

Actionability

Guidance is fully executable: the exact run command, the severity exit-code gate ("0 clean, 1 warn, 2 critical"), the JSON finding structure including `fix.command_argv`/`fix.dispatch_id` semantics, a copy-paste-ready cron job prompt with a concrete schedule, and a rendered output-format example. This matches the 'copy-paste ready commands; specific examples cover the common cases' anchor, including the unreachable-DB edge case.

5 / 5

Workflow Clarity

The findings workflow is a clearly numbered 5-step sequence with explicit checkpoints: severity gate first, an ask-before-run decision point, a dispatch_id branch distinguishing auto-runnable vs manual fixes, and a dedicated "When it fails" section with error-recovery routing (e.g. the `GBRAIN_DB_ACCESS` marker routes to db-repair). Validation (exit-code gate) and feedback loops are explicit, matching the top anchor.

5 / 5

Progressive Disclosure

The body is well-sectioned (Contract, When to run, How to run, findings workflow, cron recipe, output format, failures, anti-patterns) with nothing inlined that belongs in a separate file, and its two references (`skills/conventions/brain-first.md`, `../conventions/agent-operator-protocol.md`) are clearly signaled and one level deep. It is not a 5 because those referenced files do not exist within this bundle (no references/, scripts/, or assets/ directories), so the links cannot be resolved from what ships with the skill.

4 / 5

Total

18

/

20

Passed

Description

75%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.

A strong, concrete description that clearly says what the skill does and enumerates its finding categories comprehensively, in a distinct niche with minimal conflict risk. Its main weakness is that explicit 'when to use' guidance is absent from the description text itself (it lives only in the separate `triggers` field), capping completeness at 3.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. "Use when the user asks how to get more out of gbrain, wants a brain checkup, or mentions `gbrain advisor`".

Fold one or two natural trigger phrases from the `triggers` list (e.g. "brain checkup", "is my brain set up right") into the description body so user phrasing matches without relying on the separate triggers field.

State the invocation modes explicitly in the description ("on demand or on a weekly cadence") rather than leaving the timing implied by "Proactive".

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Runs `gbrain advisor` on a cadence and pings the user with the top high-leverage actions" — and comprehensively enumerates the finding categories ("version drift, pending migrations, stalled jobs, low embed coverage, setup smells, and uninstalled brain skills") plus behavior guarantees ("Read-only; always asks before fixing"). This matches the 'multiple specific concrete actions; comprehensive coverage' anchor; it is not the 4 anchor because coverage of what the skill surfaces is complete rather than having minor gaps.

5 / 5

Completeness

The 'what' is clear (runs the advisor on a cadence, surfaces ranked actions, read-only, asks before fixing), but the description itself contains no 'Use when...' clause or equivalent explicit trigger guidance — the explicit triggers live in the separate `triggers` field. Per the judging guideline this caps completeness at 3; the 'when' is only weakly implied by "Proactive" and "on a cadence", so it does not reach the 4 anchor's explicit 'when'.

3 / 5

Trigger Term Quality

It includes good natural keywords for the niche: "make the most of gbrain", "gbrain advisor", "brain". It is not a 5 because natural variations users would say — e.g. "brain checkup", "is my brain set up right", "get more out of" — appear only in the separate `triggers` frontmatter field, not in the description text itself; it is above a 3 because the terms present are the ones a gbrain user would naturally use, not jargon.

4 / 5

Distinctiveness Conflict Risk

The description is anchored to a distinct niche tool ("gbrain advisor", "brain") with tool-specific vocabulary, so it is clearly distinguishable from other skills and unlikely to trigger the wrong one. This matches the 'clear niche with distinct triggers; minimal conflict risk' anchor; a 4 would require some overlap with closely related skills, which is not the case here.

5 / 5

Total

17

/

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

skills/gbrain-advisor/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.