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

The canonical home for this skill is gbrain-advisor in garrytan/gbrain

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 tight, highly executable instruction-only skill: exact commands, exit-code semantics, a JSON schema, an approval-gated fix workflow, error routing, and anti-patterns, all in an organized single file. It lands just short of top marks on conciseness (repeated ask-first contract) and progressive disclosure (cron recipe and output template inlined in a >50-line body).

DimensionReasoningScore

Conciseness

The body is dense and imperative with zero background-concept explanation ("Exit code is the severity gate: 0 clean, 1 warn, 2 critical"), but the ask-before-fix contract is repeated across four sections (Contract, findings steps 3/5, Output Format, Anti-Patterns). The repetition is deliberate safety emphasis yet still trimmable, matching the "efficient with minor instances that could be trimmed" anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Everything is copy-paste ready: the exact command (`gbrain advisor --json`), the apply path (`gbrain advisor --apply <dispatch_id>`), the JSON payload field list (severity, title, fix.command_argv, fix.dispatch_id), a literal cron job prompt, and a filled-in output template with real fix commands (`gbrain apply-migrations --yes`, `gbrain upgrade`). Specific examples cover the common cases.

5 / 5

Workflow Clarity

The findings procedure is a numbered 5-step sequence with an approval gate at every mutation point ("Never run a fix the user didn't approve"), the exit code serves as an explicit severity checkpoint, and "When it fails" adds error-recovery routing (e.g. GBRAIN_DB_ACCESS routes to the db-repair skill instead of reporting "no findings"). This is a read-only skill whose only mutation is user-gated, so validation checkpoints are present rather than implicit.

5 / 5

Progressive Disclosure

A single self-contained SKILL.md with no bundle directories (references/, scripts/, assets/ are absent), organized into clear ## sections, and two clearly signaled one-level-deep references to conventions files outside the bundle (skills/conventions/brain-first.md, ../conventions/agent-operator-protocol.md). At ~107 lines with the cron recipe and output template inlined it has good structure, but those sections could split into a reference file and the conventions paths cannot be verified within the bundle, matching the minor-organization-gaps anchor.

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 highly specific, distinctive description with good natural trigger terms, held back only by completeness. The description field itself lacks an explicit "Use when..." clause, leaving the trigger guidance to the separate when_to_use/triggers frontmatter fields, which caps the what-and-when pairing at the midpoint.

Suggestions

Append an explicit trigger clause to the description field itself, e.g. "Use when the user asks 'what should I do to get more out of gbrain', 'is my brain set up right', requests a weekly brain checkup, or mentions gbrain advisor."

Fold one or two natural user phrasings ("get more out of my brain", "brain checkup") into the description so the skill surfaces from the description text alone, not just the separate triggers list.

Consider replacing the slightly jargon-y "high-leverage actions" and "setup smells" with plainer terms users would actually say when asking for help.

DimensionReasoningScore

Specificity

Names the exact command ("Runs `gbrain advisor` on a cadence and pings the user"), two concrete actions, and comprehensively enumerates the six finding classes it reports ("version drift, pending migrations, stalled jobs, low embed coverage, setup smells, and uninstalled brain skills"), plus behavioral guarantees ("Read-only; always asks before fixing"). Coverage of the skill's capabilities is complete for its domain, matching the comprehensive-actions anchor rather than the minor-gaps anchor.

5 / 5

Completeness

The "what" is clear and concrete, but the "when" is only weakly implied ("Proactive", "on a cadence") with no explicit "Use when..." clause or trigger guidance in the description field, which caps completeness at 3 per the judging guidelines. It is not a 4 because the when is not explicit, and not a 2 because the what is specific rather than vague.

3 / 5

Trigger Term Quality

Includes natural phrases a user would say ("make the most of gbrain", "gbrain advisor", "brain", "setup") giving good keyword coverage. A few natural variations are missing from the description itself (e.g. "get more out of", "weekly brain checkup", "is my brain set up right"), which live only in the separate frontmatter triggers/when_to_use fields.

4 / 5

Distinctiveness Conflict Risk

"gbrain" and "gbrain advisor" name a specific tool and subcommand, creating a clear niche with distinct triggers and minimal conflict risk with any other skill. Nothing in the description is generic enough to collide with unrelated skills.

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

plugin-variants/gbrain-daily/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.