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.

75

Quality

92%

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 lean, actionable, and well-sequenced with explicit approval and validation checkpoints plus executable commands throughout. Progressive disclosure is handled cleanly for a self-contained skill via clear sections and one-level references.

DimensionReasoningScore

Conciseness

Lean and efficient; it assumes Claude knows what a worktree, PR, and scaffold are, with no padded concept explanation — every token earns its place. Not a 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands ('git worktree add ...', 'pnpm fraimz scaffold <flow-id>', 'gh pr create --base dev --fill', 'pnpm fraimz --flow <flow-id> --pr') with concrete file paths. Not a 2 because the guidance is concrete and complete rather than pseudocode.

3 / 3

Workflow Clarity

A clear four-phase numbered sequence with an explicit gate ('no code until the script is approved') and a validate–repair–rerun feedback loop ('drive the demo against the real app, repair, and re-run until every frame passes'). Not a 2 because validation checkpoints and the error-recovery loop are explicit.

3 / 3

Progressive Disclosure

Self-contained SKILL.md with well-organized sections and one-level-deep, clearly signaled references (the 'fraimz' skill and the 'Source of truth' file list); no nested or deep reference chains. Not a 2 because navigation is clear and content is appropriately split.

3 / 3

Total

12

/

12

Passed

Description

85%

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 complete with an explicit 'Use when' trigger and concrete, distinguishable actions. Trigger-term quality is slightly held back by process jargon and uneven keyword coverage, but the niche is clear and unlikely to conflict.

Suggestions

Trade some process jargon ('voiceover-first development', 'demo-driven journey') for the plain terms a user would actually say, such as 'feature request', 'demo', 'voice-over script', and 'approve before building'.

Add a couple of common natural variations (e.g. 'write the demo script', 'spec the feature as a demo') so trigger coverage is broader.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'approve the narration BEFORE any code', 'build on a fresh worktree', 'open the PR with the proof on it', 'script the demo' — rather than vague language. It is not below 3 because the actions are specific and varied; not above because the scale tops at 3.

3 / 3

Completeness

Explicitly answers both what ('approve the narration... build on a fresh worktree... open the PR with the proof') and when ('Use when a feature request arrives, or when the user runs /voiceover'). The explicit 'Use when...' clause clears the completeness cap; it is not below 3 because both halves are present.

3 / 3

Trigger Term Quality

Natural terms like 'feature request', '/voiceover', 'demo script first', and 'PRD' appear, but the description leans on process jargon ('voiceover-first development', 'demo-driven journey') and misses common user variations. Not a 3 because coverage is uneven; not a 1 because several genuinely natural trigger phrases are present.

2 / 3

Distinctiveness Conflict Risk

Third-person voice with a clear niche — demo-first feature building tied to a specific narration/worktree/PR flow — unlikely to trigger for the wrong skill. Not a 2 because the trigger and scope are distinctive, not overlapping with generic skills.

3 / 3

Total

11

/

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