gbrain-upgrade

Keep gbrain current. When a `gbrain` invocation prints an `UPGRADE_AVAILABLE <old> <new>` marker (or `gbrain self-upgrade --check-only` reports an update), apply it per the configured self_upgrade.mode: notify (prompt the operator with a 4-option question + snooze) or auto (apply silently). The action is always the hardcoded `gbrain self-upgrade` — never a command read from the marker.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

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.

Highly actionable content: concrete commands, verbatim prompts, exact output formats, and validation checkpoints with error-recovery paths for a mutating self-upgrade. It is lean overall with only minor trimmable asides and one version-pinned external reference that is not bundled.

Suggestions

Trim or relocate the always-on-daemon/autopilot parenthetical under 'mode = auto' and de-duplicate the Contract section against the flow below it to tighten conciseness.

Replace the version-pinned `skills/migrations/v0.46.3.0.md` path with a stable location (e.g., a `references/` migration index or a glob like 'latest v* migration playbook') so the reference does not rot when new versions ship.

Consider adding a brief post-upgrade verification step (e.g., re-run `gbrain self-upgrade --check-only` or a version print) to close the loop after an applied upgrade.

Dimension	Reasoning	Score
Conciseness	The body is dense and imperative with no padding of known concepts, but the always-on-daemon/autopilot parenthetical and the Contract section restate details covered by the flow, and the version-pinned `skills/migrations/v0.46.3.0.md` reference is mildly time-sensitive without being in a deprecated/old-patterns section.	4 / 5
Actionability	Every step is copy-paste ready: `gbrain config get self_upgrade.mode`, `gbrain self-upgrade --check-only --json`, `gbrain config set self_upgrade.mode auto\|off`, a verbatim 4-option operator prompt, and exact one-line report formats for each outcome.	5 / 5
Workflow Clarity	The mode-branched sequence (read mode, then off/auto/notify paths) has explicit validation checkpoints — `--check-only --json` must report `update_available: true` before prompting, the version is regex-validated, failed versions are never retried, and doctor `self_upgrade_health` failures are surfaced — giving a genuine validate/recover feedback loop for a mutating operation.	5 / 5
Progressive Disclosure	A single-file skill with well-organized sections and one clearly signaled one-level reference ('open `skills/migrations/v0.46.3.0.md` and follow that playbook'); the minor gap is that the referenced playbook is not part of the bundle and its version-pinned filename is likely to rot across releases.	4 / 5
	Total	18 / 20 Passed

Description

92%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 description that explicitly answers both what the skill does and when to run it, with concrete mode-dependent actions and a distinctive gbrain-specific trigger surface. The only mild gap is that a few natural user phrasings live in the triggers field rather than the description itself.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete, mode-specific actions — 'apply it per the configured self_upgrade.mode: notify (prompt the operator with a 4-option question + snooze) or auto (apply silently)' and 'always the hardcoded `gbrain self-upgrade` — never a command read from the marker' — comprehensively covering the skill's scope.	5 / 5
Completeness	Both parts are explicit: the what ('apply it per the configured self_upgrade.mode...') and the when ('When a `gbrain` invocation prints an `UPGRADE_AVAILABLE <old> <new>` marker (or `gbrain self-upgrade --check-only` reports an update)') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases like 'Keep gbrain current', 'reports an update', and 'UPGRADE_AVAILABLE' give good keyword coverage, but common phrasings such as 'out of date' or 'up to date' appear only in the separate triggers field, not the description text itself.	4 / 5
Distinctiveness Conflict Risk	The description is entirely scoped to `gbrain` and its unique `UPGRADE_AVAILABLE` marker string, forming a clear niche with essentially no overlap risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: garrytan/gbrain
Path: skills/gbrain-upgrade/SKILL.md
Commit: e78f1c3

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.