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

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/capture/SKILL.md
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.

The body is an exemplary single-command skill reference: complete command surface, concrete defaults, an exact receipt format, error-code remediation with recovery loops, and clear negative guidance (anti-patterns, when NOT to use) that routes bulk and specialized ingestion to the right tools. Only minor duplication between Contract/Defaults and intro/Anti-Patterns keeps it from full marks on token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and actionable with no concept explanations, but has minor repetition that could be trimmed: the positioning of `capture` over `gbrain put` appears in both the intro ("Don't reach for `gbrain put`") and Anti-Patterns, and the daemon's 24h content-hash dedup is stated identically in both Contract ("The daemon's 24h content-hash dedup catches re-captures") and Defaults. Fits anchor 4 ("Efficient; minor instances of over-explanation that could be trimmed") rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Fully executable guidance throughout: copy-paste-ready commands covering all input modes and flags (inline, --file, --stdin, --slug, --type, --quiet, --json), concrete defaults (slug format, `note` type, 80-char title cap, frontmatter stamps), an exact example output receipt, and specific exit-code remediation ("poll `gbrain write-request <request_id>`; never capture it a second time"). Matches anchor 5's copy-paste-ready coverage of common cases.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill whose one action (run `gbrain capture`) is unambiguous, satisfying the simple-skill exception, and it goes further with an explicit error-recovery loop: exit 10 → tell the user it's saved and poll rather than re-capture, refusal → report what was refused without sneaking past the scanner, MCP scope errors → name the source needing a grant. It is not a destructive or batch operation (bulk looping is explicitly an anti-pattern), so the validation cap does not apply.

5 / 5

Progressive Disclosure

Sections are well-organized (Contract, When to invoke, How to use, Defaults, Output Format, When it fails, Anti-Patterns, When NOT to use) and the cross-references (../conventions/agent-operator-protocol.md and sibling skill SKILL.md paths) are clearly signaled one level deep. It is not anchor 5: the skill is ~100 lines all inline with no content split, and the referenced paths point outside the skill directory (no bundle files exist here to verify), so structure falls to "good structure; most content appropriately placed" rather than a clearly split, easily navigable overview.

4 / 5

Total

18

/

20

Passed

Description

53%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 the skill's role clearly and positions it well against internal alternatives, but it under-delivers as a discovery description: it states one action, omits when to use it, and buries the natural trigger phrases in a separate frontmatter field instead of the description text. The internal jargon ("put_page", "commit-then-sync", "autopilot-wait") spends tokens on positioning rather than capability or trigger coverage.

Suggestions

Append an explicit trigger clause to the description, e.g. "Use when the user says 'capture this', 'save this thought', 'remember this', or pastes content asking to keep it" — this lifts completeness from 3 to 4-5.

Fold natural synonyms ("remember this", "capture this", "save to brain", "note") into the description text itself rather than relying solely on the separate `triggers` field, improving trigger_term_quality.

Trim the internal-verb positioning ("put_page vs commit-then-sync vs autopilot-wait") in favor of one or two more user-visible capabilities (e.g. "prints a receipt with the page slug; queryable immediately via gbrain query"), improving specificity.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — "Save any thought or content into the brain via one CLI command" — but the remainder ("replaces \"put_page vs commit-then-sync vs autopilot-wait\"") is internal-verb positioning, not additional capabilities. This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") and not anchor 4, which requires several specific listed actions.

3 / 5

Completeness

The "what" is clearly stated (save thoughts/content into the brain via one CLI command), but there is no "Use when..." clause or equivalent trigger guidance in the description field — the user-facing trigger phrases live only in the separate `triggers` frontmatter list. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, which also matches anchor 3 exactly.

3 / 5

Trigger Term Quality

The description contains some natural keywords ("save", "thought", "brain", "CLI command") but misses common variations users would say — "remember this", "capture this", "note", "ingest" — which appear only in the separate frontmatter triggers field, not the description text itself. Fits anchor 3 ("Some relevant keywords but missing common variations or synonyms"), not anchor 4's "a few natural terms missing" since several core synonyms are absent.

3 / 5

Distinctiveness Conflict Risk

The description explicitly differentiates itself ("The single human-facing entrypoint that replaces \"put_page vs commit-then-sync vs autopilot-wait\""), giving it a clear niche with distinct triggers within its ecosystem. It is not anchor 5 because "Save any thought or content" claims broad scope that overlaps sibling ingestion skills (idea-ingest, meeting-ingestion, media-ingest), a minor overlap risk matching anchor 4.

4 / 5

Total

13

/

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