talk-stage5-script
Produces a complete 5-act pitch with speaker notes, a slide-by-slide specification, and a ready-to-paste Kimi prompt for AI slide generation. Requires validated angle and title from Stage 4. Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt.
66
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong description that clearly articulates specific outputs, prerequisites, and when to use the skill. Its main weakness is that trigger terms lean toward specialized vocabulary that may not match how users naturally phrase requests. The description is concise, uses third person voice, and carves out a distinct niche within what appears to be a multi-stage workflow.
Suggestions
Add more natural trigger terms users might say, such as 'presentation', 'deck', 'slides', 'keynote script', or 'talk preparation' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'complete 5-act pitch with speaker notes', 'slide-by-slide specification', and 'ready-to-paste Kimi prompt for AI slide generation'. Also specifies a prerequisite ('validated angle and title from Stage 4'). | 3 / 3 |
Completeness | Clearly answers both 'what' (produces a 5-act pitch with speaker notes, slide spec, and Kimi prompt) and 'when' (explicit 'Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt'). The trigger clause is explicit and well-defined. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'pitch', 'speaker notes', 'slide spec', 'presentation prompt', and 'talk angle', but these are somewhat specialized. Missing common variations users might say like 'presentation', 'deck', 'slides', 'keynote', 'talk preparation'. The term 'Kimi prompt' is very niche and may not be naturally used by most users. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: the combination of '5-act pitch', 'Kimi prompt', 'Stage 4' prerequisite, and the specific output format (script + slide spec + AI prompt) makes this very unlikely to conflict with other skills. It occupies a very specific step in a defined workflow. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill that provides complete, concrete output formats and a clear multi-step workflow with validation checkpoints. Its main weakness is moderate verbosity — some sections are redundant (e.g., 'When to Use' repeats the prerequisite, 'What This Skill Does' previews the workflow that follows in detail), and the large inline templates could benefit from being extracted to separate reference files. Overall, it's a well-crafted skill that would effectively guide Claude through producing all three deliverables.
Suggestions
Remove or merge the 'When to Use This Skill' and 'What This Skill Does' sections — the prerequisite line and the detailed workflow below already convey this information more concisely.
Consider extracting the pitch.md and slides.md format templates into separate reference files (e.g., templates/pitch-format.md) and linking to them, reducing the SKILL.md body length and improving progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes some unnecessary explanation (e.g., 'When to Use This Skill' and 'What This Skill Does' sections largely repeat information). The detailed format templates are justified given the complexity, but the 'Tips' section and some preamble could be tightened. | 2 / 3 |
Actionability | Highly actionable — provides exact file formats with complete markdown templates for all three deliverables, specific construction rules, anti-patterns to avoid, a concrete validation checklist, and step-by-step instructions for using the Kimi prompt. Everything is copy-paste ready or directly implementable. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: verify inputs → load template → build pitch → build slide spec → generate Kimi prompt → save files. Validation is explicit with a comprehensive checklist including placeholder verification. The prerequisite checkpoint from Stage 4 is clearly stated, and the Kimi usage steps include a verification step before proceeding. | 3 / 3 |
Progressive Disclosure | References to related stages and the Kimi template are well-signaled and one level deep. However, the inline format templates for pitch.md and slides.md are quite lengthy (~80 lines combined) and could arguably be split into separate reference files. The 'Related' section is clean, but the main body is heavy with inline content. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
60a4372
- 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.