CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

The canonical home for this skill is capture in garrytan/gbrain

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is highly actionable with copy-paste-ready commands, explicit defaults, output formats, and concrete failure recovery, and the single-action workflow is unambiguous. The main weakness is redundancy — repeated dedup and anti-put guidance, duplicated trigger lists, and inline version-specific details that could be tightened.

Suggestions

State the 24h content-hash dedup once (Contract or Defaults, not both) and merge the intro's "don't reach for gbrain put or commit-then-sync" into the Anti-Patterns section to remove the repetition.

Drop the "When to invoke" section or reduce it to a pointer, since it restates the frontmatter triggers verbatim.

Move version-sensitive specifics ("v0.38 write-through plumbing") out of the main flow or into a changelog/deprecated note so the guidance ages better.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the 24h dedup sentence appears verbatim in both Contract and Defaults, "don't reach for gbrain put" is stated in both the intro and Anti-Patterns, "When to invoke" duplicates the frontmatter triggers, and version-sensitive details ("v0.38 write-through plumbing", date-stamped receipt example) are not isolated — more than minor trimming is needed.

3 / 5

Actionability

Commands are copy-paste ready and cover every input mode (inline, --file, --stdin) and flag (--slug, --type, --source, --quiet, --json), the exact receipt output format is shown, and failure handling gives per-exit-code recovery actions (poll gbrain write-request, never re-capture).

5 / 5

Workflow Clarity

This is a simple single-action skill with an unambiguous invocation (run gbrain capture with the content), and the "When it fails" section supplies explicit error-recovery guidance; it is not a destructive or batch operation, so no validation cap applies.

5 / 5

Progressive Disclosure

Sections are well-organized with clearly signaled one-level references to sibling skills and an operator protocol, but the referenced paths (../conventions/agent-operator-protocol.md, skills/*/SKILL.md) do not exist in this bundle, and at ~100 lines the body sits above the under-50-line simple-skill exception.

4 / 5

Total

17

/

20

Passed

Description

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

The description communicates a clear core action but reads more like internal positioning than a trigger-optimized skill description. It lacks an explicit "Use when..." clause, natural trigger synonyms, and differentiation from sibling ingestion skills.

Suggestions

Append an explicit trigger clause to the description, e.g. "Use when the user says 'capture this', 'save this thought', 'remember this', or wants to store any content in the brain."

Include natural trigger synonyms ("remember this", "capture this", "save to brain") in the description text itself rather than only in the separate triggers/when_to_use frontmatter fields.

Trim internal jargon ("put_page vs commit-then-sync vs autopilot-wait") from the description and reserve it for the body, replacing it with a brief distinction from sibling ingestion skills.

DimensionReasoningScore

Specificity

"Save any thought or content into the brain via one CLI command" names the domain and one concrete action, but the rest ("single human-facing entrypoint that replaces...") is positioning rather than capability, so coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (save content into the brain via one CLI command), but the description contains no "Use when..." clause or equivalent trigger guidance — the when_to_use frontmatter field is separate from the description — which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

"Save", "thought", "content", and "brain" are natural terms, but common variations users would actually say ("remember this", "capture this", "take a note") are missing from the description itself.

3 / 5

Distinctiveness Conflict Risk

The brain-capture niche is somewhat specific, but "any thought or content" is broad and the description does not disambiguate from closely related ingestion skills (media-ingest, idea-ingest, meeting-ingestion), leaving overlap risk.

3 / 5

Total

12

/

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/skills/capture/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.