CtrlK
BlogDocsLog inGet started
Tessl Logo

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

65

Quality

78%

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 ./skills/media-ingest/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong operational skill body: exact commands, a copy-paste page template, sequenced phases with genuine validation gates, and skill-specific pitfalls (caption-garbled proper nouns, duplicate re-ingest, diarization limits) that Claude could not infer on its own. The only real costs are redundancy around the filing rule and the absence of a final verification pass over the created back-links.

DimensionReasoningScore

Conciseness

Dense, tabular, assumes Claude's competence — no space is spent explaining what a PDF or transcript is, and every section carries skill-specific knowledge (gbrain commands, filing conventions, OCR thresholds). Not anchor 5 because the file-by-subject rule is stated four times (top 'Filing rule' note, Contract bullet, Phase 3, Anti-Patterns) and the Contract section partially restates the Phases.

4 / 5

Actionability

Fully executable guidance: exact commands ('gbrain files upload-raw <file> --page <slug>', 'gbrain sync'), a copy-paste-ready page template, an explicit user-report format, and concrete procedures (search brain for source URL/hash before Phase 3, retry once on transient failures, abort on auth failures). The open-ended steps (STT choice, 'delegate to enrich skill') are environment flexibility, not vagueness.

5 / 5

Workflow Clarity

Five clearly sequenced phases with real validation checkpoints for a mutating/batch operation: pre-create duplicate search, the OCR <80% quality gate with user flagging, retry policy, and the completion criterion 'A media item is NOT fully ingested until entity propagation is complete.' Not anchor 5: there is no post-creation verification step confirming back-links and timeline entries actually landed.

4 / 5

Progressive Disclosure

Well-organized sections (Input, Contract, Phases, Output Format, Error Handling, Known Pitfalls, Anti-Patterns) with external references ('skills/_brain-filing-rules.md', 'skills/conventions/quality.md') one level deep and clearly signaled via blockquotes. No bundle directories (references/, scripts/, assets/) exist, so nothing is withheld or nested; minor gap is that the pitfalls/anti-patterns content could be trimmed per the conciseness point rather than reorganized.

4 / 5

Total

17

/

20

Passed

Description

75%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 solid, specific description that names concrete actions, formats, and the destination system in third-person voice, backed by a rich natural-language trigger list in the frontmatter. Its main weakness is structural: the 'when to use' guidance lives in a separate triggers field rather than the description text, and declared subtype coverage creates minor conflict risk with sibling ingest skills.

Suggestions

Embed a one-line 'Use when ...' clause in the description itself (e.g. 'Use when the user shares a video, podcast, PDF, book, screenshot, or repo to save into the brain') so the description is self-contained for trigger matching.

Clarify whether video-ingest/youtube-ingest/book-ingest are separate skills or aliases; if separate skills exist, remove the 'Covers ... subtypes' claim to avoid routing conflicts.

Add one or two more action verbs (transcribe, summarize, upload raw source) to move specificity from several-actions to comprehensive coverage.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain', 'entity extraction and backlink propagation' — with comprehensive format coverage, but deeper actions (transcribe, summarize, upload raw source) go unstated. Matches anchor 4 ('several specific actions; minor gaps'), not 3 (more than 1-2 actions present) nor 5 (not a complete action inventory).

4 / 5

Completeness

The 'what' is clear and concrete ('Ingest ... content into the brain. Multi-format handling with entity extraction and backlink propagation.'), and explicit trigger guidance exists in the same frontmatter via the 'triggers' list, so the missing-'Use when' cap at 3 does not apply. Falls short of anchor 5 because the 'when' is not embedded in the description text itself with concrete trigger phrases — it lives in a separate field.

4 / 5

Trigger Term Quality

Natural keywords 'video, audio, PDF, book, screenshot, GitHub repo' plus very natural frontmatter trigger phrases ('watch this video', 'save this podcast', 'what's in this screenshot', 'check out this repo') give good coverage with synonyms. Not anchor 5: no file extensions (.pdf, .mp3) and a few common variations (e.g. 'transcribe', 'media') are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (media ingestion into the brain) with distinct trigger phrases, but 'Covers video-ingest, youtube-ingest, and book-ingest subtypes' declares overlap with what may be separate skills. Matches anchor 4 ('mostly distinct; minor overlap risk with closely related skills'), not 5 (subtype declaration introduces some conflict surface) and not 3 (the brain-ingest framing is far more specific than generic document handling).

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

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.