CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

videodb-skills

Upload, stream, search, edit, transcribe, and generate AI video and audio using the VideoDB SDK.

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/videodb-skills/SKILL.md

The canonical home for this skill is videodb-skills in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured and setup is executable, but the skill's actual purpose — using the VideoDB SDK — is represented only by natural-language example prompts with no SDK code, API patterns, or task workflows. Validation exists only implicitly in setup, not in the task workflows themselves.

Suggestions

Add a minimal executable SDK snippet per major capability (connect, upload, search, edit/compile, stream) so the skill is copy-paste actionable rather than intent-only examples.

Sequence the core workflow (upload → optionally transcribe → edit → compile → get stream URL) with an explicit verification step, e.g. checking the returned playable link before reporting success.

Move marketing copy ("The only video skill your agent needs", "$20 free credits, no credit card") out of the body, and as capability detail grows, split per-capability guides into referenced files to keep SKILL.md an overview.

DimensionReasoningScore

Conciseness

Mostly lean — a terse capabilities table, one-line bullets, and short examples — but contains minor trimmable fluff such as "The only video skill your agent needs" and "($20 free credits, no credit card)".

4 / 5

Actionability

Setup is fully executable ("npx skills add video-db/skills", "pip install \"videodb[capture]\" python-dotenv"), but the core task content — how to use the VideoDB SDK to upload, search, edit, or transcribe — has no code or API detail; the Examples are natural-language user prompts rather than executable guidance.

3 / 5

Workflow Clarity

The 3-step setup sequence is clear and step 2 mentions it "verifies the connection", but the primary workflows (upload → search → edit → compile → stream) have no sequence or validation checkpoints at all.

3 / 5

Progressive Disclosure

A well-organized single file with clear sections (Purpose, When to Use, Setup, Capabilities, Examples, Repository) and a repo link, no nested references; scored 4 rather than 5 because at ~108 lines with no per-capability detail pointers, the Examples/capability detail are beginning to justify a split into referenced files.

4 / 5

Total

14

/

20

Passed

Description

71%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 is specific and verb-rich, clearly communicating what the skill does with a distinct VideoDB niche. Its main weakness is the absence of any 'Use when...' trigger clause, and its keyword coverage misses natural variations like 'subtitles' and 'captions'.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to upload, search, transcribe, subtitle, edit, or AI-generate video/audio, or mentions VideoDB."

Add natural synonym keywords users actually say — "subtitles", "captions", "clip", "transcription" — to improve trigger matching.

Mention input sources users name (YouTube links, local files, screen recording) to sharpen when-to-use disambiguation against generic media skills.

DimensionReasoningScore

Specificity

Six concrete, distinct actions ("Upload, stream, search, edit, transcribe, and generate AI video and audio") scoped to a named SDK, comprehensively covering the domain — matches the 'multiple specific concrete actions; comprehensive coverage' anchor.

5 / 5

Completeness

The 'what' is clear via six named actions, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like "upload", "search", "edit", "transcribe", and "stream" are present, but common user phrasings such as "subtitles", "captions", and "video editing" are missing despite being core capabilities listed in the body.

4 / 5

Distinctiveness Conflict Risk

"using the VideoDB SDK" establishes a clear niche, but generic verbs like "search", "edit", and "transcribe" leave minor overlap risk with general transcription or media-editing skills — 'mostly distinct; minor overlap risk'.

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/videodb-skills/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.