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.

80

Quality

100%

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

100%

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, action-oriented overview: lean prose, executable commands at every phase, an explicit approval gate and validate/repair feedback loop, and well-signaled one-level-deep references to source-of-truth files. It neither over-explains generic knowledge nor buries detail in nested files.

DimensionReasoningScore

Conciseness

The body is lean and instruction-oriented with no padding or explanations of concepts Claude already knows; its only conceptual line ("The voice-over is the spec") is the skill's core thesis rather than generic background, so every token earns its place.

3 / 3

Actionability

It provides fully executable, copy-paste-ready commands — git worktree add, pnpm fraimz scaffold, git push, gh pr create, pnpm fraimz --flow --pr — plus a concrete script-format example, matching the copy-paste-ready anchor.

3 / 3

Workflow Clarity

A clear four-phase sequence with numbered steps and explicit validation gates — the "no code until the script is approved" contract, the drift-check failure, and the Phase 3 "repair, and re-run until every frame passes" feedback loop — matches the anchor for clear sequence with explicit validation and error-recovery loops.

3 / 3

Progressive Disclosure

No bundle files are present (references/, scripts/, assets/ are absent), so this is scored on the body, which is well-organized into phases, a script-format spec, and a one-level-deep "Source of truth" section pointing to specific source files and the fraimz skill — clear overview with well-signaled shallow references.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise yet complete: concrete actions, natural trigger terms, an explicit Use-when clause, and a distinctive niche. It uses imperative rather than first/second person, so no voice penalty applies. No improvements needed.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "approve the narration BEFORE any code", "build on a fresh worktree until the demo holds", and "open the PR with the proof on it" — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

It answers both what ("the whole demo-driven journey... approve... build... open the PR") and when ("Use when a feature request arrives, or when the user runs /voiceover"), with an explicit Use-when trigger clause.

3 / 3

Trigger Term Quality

It offers broad natural-language coverage a user would actually say — "write the voice-over", "demo script first", "align on the demo", "script the demo", "ship a feature demo-first", plus the explicit "/voiceover" — with no jargon-only gaps.

3 / 3

Distinctiveness Conflict Risk

The voiceover-first/demo-driven niche is unusual and clearly bounded with distinct triggers (/voiceover, feature request), making conflict with other skills unlikely.

3 / 3

Total

12

/

12

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
different-ai/openwork
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.