CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

faceless-video

Make faceless videos end to end with the PopNow API: topic to hook-first script, AI voiceover, matching B-roll images or clips, captions and a 9:16 or 16:9 cut for TikTok, Reels, Shorts and YouTube. Quotes every step in USD before spending. Use when the user wants faceless content, a YouTube automation video, a short explainer or a series of shorts.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

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 strong, highly actionable skill body: the paid-generation workflow is gated by explicit quote-approval checkpoints with correct retry semantics, and every command is concrete and executable. The only weaknesses are minor — a slightly padded intro, a version-sensitive model table that could age poorly, and limited use of reference files to keep SKILL.md lean.

Suggestions

Trim the opening definitional sentence ("A faceless video tells a story with narration over visuals, without anyone on camera") — Claude already knows this; start with what to deliver.

Move the versioned "Recommended models" table into a references/ file (e.g. references/models.md) and keep only the instruction to confirm paths via `scripts/popnow.py models`, so time-sensitive version numbers don't age the main file.

DimensionReasoningScore

Conciseness

The body is dense and operational — numbered beats, timing budgets, exact CLI argument templates — but has minor trimmable fat: the opening definition "A faceless video tells a story with narration over visuals, without anyone on camera" explains a concept Claude already knows, and the versioned "Recommended models" table is time-sensitive information not placed in a deprecated/old-patterns section. This fits the score-4 anchor (efficient with minor instances of over-explanation) better than 5, where every token would earn its place.

4 / 5

Actionability

Every step is executable: full command templates for models/quote/create/status with exact flags ("--quote-id <quoteId>", "--approved-max-usd <approved-decimal-string>", "--idempotency-key <stable-key>"), a concrete worked search example, ffmpeg assembly specifics (concat demuxer, H.264, yuv420p), and caption constraints ("under about 42 characters"). Placeholders are appropriate since values are discovered at runtime via the schema check. This is copy-paste-ready guidance covering the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

Two interleaved workflows are clearly sequenced (8-step creative pipeline; models → quote → approve → create → status API loop) with explicit validation checkpoints for a paid batch operation: user approval of a cost table before any spend, re-quote on plan change/price rise/expiry, retry with the same idempotency key after timeout, "pending is not failure", and terminal-failure/auth/low-balance handling. The feedback loops (re-quote, retry-same-key, re-validate) match the score-5 anchor; score 4 would require a missing checkpoint, and none is missing.

5 / 5

Progressive Disclosure

Structure is good: clear headers, and the only bundle references (scripts/popnow.py and its client) are real, one level deep, and clearly signaled with runnable commands. But at ~103 body lines the skill exceeds the under-50-line simple-skill exception, and the time-sensitive "Recommended models" table plus the API workflow detail are natural candidates for a references/ file that the body only partially justifies keeping inline. Score 4 (good structure, minor organization gaps) rather than 5 (content appropriately split across files).

4 / 5

Total

18

/

20

Passed

Description

100%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.

An exemplary description: it states a comprehensive, concrete capability set in third person, prices in the cost-approval behavior that distinguishes it, and closes with an explicit 'Use when' clause full of natural trigger terms for the faceless-video niche. It reads like the rubric's own good examples.

DimensionReasoningScore

Specificity

The description enumerates the full concrete pipeline — "topic to hook-first script, AI voiceover, matching B-roll images or clips, captions and a 9:16 or 16:9 cut" plus "Quotes every step in USD before spending" — comprehensive coverage of the skill's capabilities with no vague filler. It matches the score-5 anchor (multiple specific concrete actions, comprehensive) rather than score 4, which allows minor coverage gaps; every core capability of the skill is named.

5 / 5

Completeness

It explicitly answers both questions: the "what" is the enumerated end-to-end pipeline, and the "when" is the explicit clause "Use when the user wants faceless content, a YouTube automation video, a short explainer or a series of shorts" with concrete trigger phrases. This mirrors the score-5 anchor example almost exactly; score 4 would require the 'when' to be less explicit or specific.

5 / 5

Trigger Term Quality

Natural user phrasings are well covered: "faceless videos", "faceless content", "a YouTube automation video", "a short explainer", "a series of shorts", plus platform names ("TikTok, Reels, Shorts and YouTube"). These are the terms users actually say in this niche, matching the comprehensive-synonyms anchor; no meaningful natural variant is missing (score 4 would require noticeable gaps).

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (faceless/voiceover video generation via the PopNow API) with distinct triggers — "faceless", "YouTube automation", named short-form platforms — that no generic video-editing or audio skill would claim. Minimal conflict risk, matching the score-5 anchor; score 4 would imply overlap with closely related skills, which the highly specific triggers here avoid.

5 / 5

Total

20

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

popnow-ai/popnow-skills

Path

skills/popnow-faceless-video/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.