CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

72%

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-variants/gbrain-daily/skills/media-ingest/SKILL.md

The canonical home for this skill is media-ingest in garrytan/gbrain

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a well-structured, highly actionable five-phase workflow with concrete gbrain commands, a complete page template, real validation checkpoints, and detailed failure-mode coverage. Its weaknesses are redundant error guidance repeated across three sections, an options-menu Phase 1 without concrete transcription commands, and external references that cannot be verified in the bundle.

Suggestions

Consolidate the duplicated error guidance: merge "When it fails" into "Error Handling" (or vice versa) since transcription-failure, retry-once, and auth-abort policy are stated nearly verbatim in both, and fold the duplicate-detection bullet into Known Pitfalls #2 or keep only one copy.

Embed the duplicate-source check as an explicit pre-step inside Phase 3 (e.g., "Phase 3.0: search the brain for the source URL or file hash; if found, ask the user") so validation is an inline gating step rather than scattered across sections.

Add a final verification step after `gbrain sync` (e.g., confirm the entity back-links resolve) to close the workflow with an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts and uses tight tables and bullets, but error guidance is duplicated: the retry-once/auth-abort policy appears in both "Error Handling" ("On transient API failures (network, timeout), retry once. On auth failures, abort immediately") and "When it fails" ("A transient API failure ... retry once. On an auth failure, abort"), and duplicate detection appears in both "Error Handling" ("search the brain for the source URL or file hash") and "Known Pitfalls" #2. This fits the 3 anchor ("Mostly efficient but includes some unnecessary explanation or could be tightened"). Not a 4 because the duplication spans three overlapping sections and is more than a minor trim.

3 / 5

Actionability

Concrete executable elements abound: `gbrain files upload-raw <file> --page <slug>`, `gbrain sync`, a full copy-paste page template, a numbered 4-step entity propagation procedure, and a report format ("Ingested {title}: {N} entities detected, {N} pages updated."), matching the 4 anchor ("Mostly executable guidance; concrete code or commands with minor gaps"). Not a 5 because Phase 1 fetching is an options menu ("Fetch transcript (Whisper, transcription service, or captions)", "Transcribe with available STT service") rather than concrete commands.

4 / 5

Workflow Clarity

The five phases are clearly sequenced and real checkpoints exist — duplicate detection before page creation, "A media item is NOT fully ingested until entity propagation is complete", and the OCR quality threshold ("If OCR quality is <80% readable, flag to user") — with error-recovery guidance (retry once on transient failures, abort on auth). This fits the 4 anchor ("Clear sequence with most checkpoints present; minor validation gaps"). Not a 5 because the validation checks live in separate sections rather than inline gating steps in the phase sequence, and there is no post-sync verification that back-links were actually created.

4 / 5

Progressive Disclosure

The single-file body is well organized into labeled sections with clearly signaled, one-level-deep references ("**Filing rule:** Read `skills/_brain-filing-rules.md`", "**Convention:** See `skills/conventions/quality.md`", the linked agent-operator protocol), matching the 4 anchor ("Good structure; most content is appropriately placed; references mostly clear; minor organization gaps"). Not a 5 because no bundle files exist to verify the referenced paths against, and the four overlapping sections (Error Handling, Known Pitfalls, When it fails, Anti-Patterns) could be consolidated for better navigation.

4 / 5

Total

15

/

20

Passed

Description

66%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 clearly communicates a multi-format media ingestion capability with concrete entity-extraction and backlink actions in a distinct brain-ingest niche. Its main weakness is the missing explicit "Use when..." trigger guidance inside the description field itself, which caps completeness, alongside a few absent natural trigger terms like "podcast" and file extensions.

Suggestions

Add an explicit "Use when..." clause with concrete user trigger phrases (e.g., "Use when the user asks to ingest, watch, or summarize a video, podcast, PDF, book, screenshot, or repo into the brain") directly inside the description field rather than relying on the separate when_to_use frontmatter key.

Include natural synonyms and variations users actually say in the description — "podcast", "episode", "transcribe", "link/URL", and file extensions like .pdf and .mp3 — to strengthen trigger term coverage.

Name one or two concrete processing actions (e.g., "transcribes audio, extracts text via OCR") in the description so the action list is comprehensive rather than umbrella-level.

DimensionReasoningScore

Specificity

"Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation" lists several specific actions across six named formats, matching the 4 anchor ("Lists several specific actions; minor gaps in coverage"). Not a 5 because the primary verb "ingest" is an umbrella action and concrete processing steps (transcription, OCR, summarization) are only implied by format names.

4 / 5

Completeness

The description has a clear "what" ("Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain" with entity extraction and backlink propagation) but no "Use when..." clause or equivalent trigger guidance within the description field itself, so per the guideline cap it fits the 3 anchor ("Has a clear 'what' but 'when' is missing or only weakly implied"). The separate frontmatter when_to_use/triggers fields are not part of the evaluated description. Not a 2 because the "what" is concrete and multi-action, not vague.

3 / 5

Trigger Term Quality

Natural terms like "video", "PDF", "book", "screenshot", "GitHub repo", and "YouTube" give good keyword coverage, fitting the 4 anchor ("Good keyword coverage; a few natural terms missing"). Not a 5 because common user phrasings such as "podcast", "link", "transcribe", and file extensions (.pdf, .mp3) are absent from the description.

4 / 5

Distinctiveness Conflict Risk

"Ingest ... into the brain", "entity extraction and backlink propagation", and "Covers video-ingest, youtube-ingest, and book-ingest subtypes" carve out a clear niche and explicitly subsume sibling subtypes, matching the 4 anchor ("Mostly distinct; minor overlap risk with closely related skills"). Not a 5 because the broad multi-format scope (notably GitHub repo ingestion) creates minor overlap risk with other ingest or repo-analysis skills.

4 / 5

Total

15

/

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-variants/gbrain-daily/skills/media-ingest/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.