capture

Save any thought or content into the brain via one CLI command. The single human-facing entrypoint that replaces "put_page vs commit-then-sync vs autopilot-wait" with one command that just works.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/capture/SKILL.md

Quality

Content

85%

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

The content is highly actionable and clearly organized for a simple single-task skill, with executable examples and a well-documented contract. The only weakness is minor verbosity from an inline version number and duplicated trigger phrasing.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with no explainer filler, but it embeds an inline version number ("v0.38 write-through plumbing") and repeats trigger phrases already present in the frontmatter, so it could be tightened further.	2 / 3
Actionability	It provides fully executable gbrain capture commands covering every flag (inline, --file, --stdin, --slug, --type, --quiet, --json) plus a concrete receipt/output block that is copy-paste ready.	3 / 3
Workflow Clarity	This is a simple single-action skill whose action is unambiguous; the Contract section documents input, output, side effects, idempotency, and trust, and there is no destructive/batch operation requiring a validation checkpoint.	3 / 3
Progressive Disclosure	No bundle files exist, the body is organized into clearly labeled sections, and the only references are one-level pointers to sibling skills in 'When NOT to use', so navigation is easy with no nested reference chains.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 conveys a clear, distinct purpose and niche but stops short of listing multiple concrete actions or an explicit when-to-use clause. Trigger-term coverage in the description field is moderate, with the richer phrasing isolated in the triggers list.

Suggestions

Append an explicit 'Use when the user wants to save a thought, note, or snippet into the brain' clause so the description answers both what and when.

Surface a couple of concrete sub-actions (inline arg, --file, --stdin) in the description to lift specificity from a single action to multiple concrete actions.

Fold one or two natural trigger phrases (e.g. 'remember this', 'drop this in the inbox') directly into the description so trigger-term quality does not depend on the separate triggers field.

Dimension	Reasoning	Score
Specificity	Names a concrete action ("Save any thought or content into the brain via one CLI command") and contrasts it with the primitives it replaces, but it describes a single action rather than listing multiple specific concrete actions.	2 / 3
Completeness	It clearly states what the skill does but lacks an explicit "Use when…" trigger clause, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	"thought", "content", and "brain" are moderately natural terms, but the description field omits common user variations ("save this", "remember this") which only appear in the separate triggers field.	2 / 3
Distinctiveness Conflict Risk	Positioning as "the single human-facing entrypoint" with explicit contrast against put_page/commit-then-sync/autopilot-wait gives it a clear niche unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 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/capture/SKILL.md
Commit: 3fafb69

Reviewed: about 21 hours 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.