CtrlK
BlogDocsLog inGet started
Tessl Logo

voiceover

write the voice-over, demo script first, voiceover instead of PRD, voiceover-first development, align on the demo, script the demo, ship a feature demo-first. The whole demo-driven journey — approve the narration BEFORE any code, then build on a fresh worktree until the demo holds and open the PR with the proof on it. Use when a feature request arrives, or when the user runs /voiceover.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 tight, actionable, well-sequenced workflow with executable commands and explicit validation/feedback loops. The only sub-5 dimension is progressive disclosure, where splitting the script-format detail or fraimz-handoff into a reference file would push it to 5.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence (no explanation of worktrees, PRs, or scaffolding) with every section earning its place; only a couple of framing sentences are mildly narrative.

5 / 5

Actionability

Copy-paste-ready bash commands (git worktree add, pnpm fraimz scaffold, gh pr create, pnpm fraimz --flow --pr), concrete file paths, and an explicit script-format example cover the common cases.

5 / 5

Workflow Clarity

A clear four-phase numbered sequence with explicit validation checkpoints and a feedback loop: "no code until the script is approved", the runner failing on narration drift, and "repair and re-run until every frame passes".

5 / 5

Progressive Disclosure

Well-organized into phases with one-level-deep references to source-of-truth files and the fraimz skill; at ~70 lines it slightly exceeds the under-50-line simple-skill threshold, so it stays just below 5 rather than at it.

4 / 5

Total

19

/

20

Passed

Description

87%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 strong: it names concrete actions, includes an explicit "Use when" trigger, and carves out a distinct niche. Minor synonym/trigger-term breadth is the only gap keeping specificity and trigger quality below 5.

DimensionReasoningScore

Specificity

Lists several concrete actions ("approve the narration BEFORE any code", "build on a fresh worktree", "open the PR with the proof on it"), but the build/verify mechanics are slightly compressed compared to a fully comprehensive action list.

4 / 5

Completeness

Clearly states the whole demo-driven journey (what) and explicitly provides a "Use when a feature request arrives, or when the user runs /voiceover" trigger clause (when).

5 / 5

Trigger Term Quality

Natural phrases like "feature request arrives", "runs /voiceover", "script the demo", and "demo-first" give good keyword coverage, though coverage is more idiomatic than exhaustively synonym-rich.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (voiceover-first, narration-before-code workflow) with a distinctive /voiceover trigger and minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Devin-AXIS/iPolloWork
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.