CtrlK
BlogDocsLog inGet started
Tessl Logo

idea-ingest

Ingest links, articles, tweets, and ideas into the brain. Fetch content, save to brain with analysis, credit the author (people page only when they pass the notability gate), and cross-link. Use when the user shares a link or says "read this", "save this", "think about this".

71

Quality

89%

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

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 well-structured, highly actionable skill body: a six-phase workflow with real validation checkpoints, concrete commands and templates, and proper delegation of filing rules to external files. Its weaknesses are minor — redundant restatements of the notability gate and fetch-fail rules, and slightly loose placement of the back-link convention.

Suggestions

Consolidate the fetch-fail guidance into one section (either "Edge Cases" or "When it fails") and cross-reference from the other to remove duplication.

Fold the back-link format paragraph into the Contract section (or the referenced conventions file) so the Returns block is not followed by a stray rule.

State the notability gate once in Phase 3 and reference it from the Contract and Anti-Patterns instead of restating the full condition three times.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence with no concept over-explanation, but the notability-gate rule and the inline author-credit format are each stated three times (Contract, Phase 3, Anti-Patterns), and the fetch-fail case is described in both "Edge Cases" and "When it fails". This is efficient with minor trimmable repetition (anchor 4) rather than noticeably verbose (anchor 3).

4 / 5

Actionability

Concrete commands ("gbrain files upload-raw <file> --page <slug>", "gbrain sync", "gbrain write-request <request_id>"), an exact markdown page template, a precise back-link format, and a typed return contract (page_path, author_path, cross_links, status) give copy-paste-ready guidance. For an instruction-only skill this fully matches the anchor-5 executable-guidance standard.

5 / 5

Workflow Clarity

Six clearly sequenced phases (fetch, upload raw, identify author, save, analyze, sync) with explicit validation checkpoints (pre-ingest duplicate-URL search, notability gate, write_pending polling) and a dedicated error-recovery section. The destructive/batch cap does not apply because verification steps are present; this matches the anchor-5 feedback-loop example.

5 / 5

Progressive Disclosure

Sections are well-organized (Contract, Phases, Output Format, Edge Cases, When it fails, Anti-Patterns) with one-level, well-signaled external references ("skills/_brain-filing-rules.md", "skills/conventions/quality.md", the agent operator protocol). Minor organization gaps remain: the fetch-fail rule is duplicated across two sections, and the back-link format paragraph sits loosely after the Returns block. This fits anchor 4 (good structure, minor gaps) rather than anchor 5's easy-navigation standard.

4 / 5

Total

18

/

20

Passed

Description

88%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 and when with concrete trigger phrases and a complete, third-person action pipeline. Its only weaknesses are a few missing natural trigger synonyms and mild overlap risk from generic phrases like "save this".

Suggestions

Add one or two more natural trigger synonyms to the description (e.g., "bookmark this" or "check this out") to broaden keyword coverage.

Tie the generic phrases more tightly to the brain domain in the 'when' clause (e.g., "save this to the brain") to reduce overlap with other capture/reading skills.

DimensionReasoningScore

Specificity

"Fetch content, save to brain with analysis, credit the author (people page only when they pass the notability gate), and cross-link" lists multiple concrete actions covering the full ingest pipeline, in third-person voice. This matches the comprehensive-coverage anchor; anchor 4 would require a gap in the pipeline, and none is evident.

5 / 5

Completeness

The description clearly states what it does ("Ingest links, articles, tweets, and ideas into the brain. Fetch content, save to brain with analysis, credit the author... and cross-link") and when to use it with concrete trigger phrases ("Use when the user shares a link or says 'read this', 'save this', 'think about this'"). This matches anchor 5 exactly; anchor 4 would require a less explicit 'when' clause.

5 / 5

Trigger Term Quality

Natural user phrases like "read this", "save this", "think about this", and "shares a link" are present, but common variants such as "bookmark this", "check this out", or "add this to brain" are missing from the description (the last appears only in the frontmatter triggers list, not the description text). Good coverage with a few natural terms missing fits anchor 4, not the synonym-level comprehensiveness of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The brain-specific vocabulary ("into the brain", notability gate) carves a clear niche, but generic trigger phrases like "read this" and "save this" carry minor overlap risk with other capture/reading skills. It sits between anchor 4 (mostly distinct, minor overlap) and anchor 5 (clear niche with minimal conflict), and the generic phrases keep it from a clean anchor-5 fit.

4 / 5

Total

18

/

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 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository
garrytan/gbrain
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.