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.
86
85%
Does it follow best practices?
Impact
Pending
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 deliverables and includes an explicit 'Use when' clause with clear trigger conditions. The main weakness is in trigger term coverage—it relies on somewhat specialized terminology ('5-act pitch', 'Kimi prompt') that users may not naturally use, and it misses common synonyms like 'presentation', 'deck', or 'slides'.
Suggestions
Add common user-facing trigger terms like 'presentation', 'deck', 'slides', 'talk script' to improve discoverability when users use everyday language.
Consider briefly clarifying what 'Kimi prompt' means (e.g., 'Kimi AI slide-generation tool') for broader recognition.
| 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' ('Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt'). The explicit 'Use when...' clause is present with clear trigger conditions. | 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 its specific niche: 5-act pitch structure, Stage 4 dependency, Kimi prompt generation. The combination of these elements makes it very unlikely to conflict with other skills. The pipeline stage reference ('Stage 4') further narrows its scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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, well-structured skill that provides highly actionable output specifications for three deliverables. The format templates are detailed and copy-paste ready, the workflow is clear with explicit validation steps, and references to related stages and templates are well-organized. Minor verbosity in introductory sections and some redundancy between 'What This Skill Does' and the actual workflow prevent a perfect conciseness score.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long but most content serves a purpose — the detailed format templates are necessary for reproducibility. However, some sections like 'What This Skill Does' largely duplicate the workflow that follows, and tips like 'Speaker notes are the heart of this stage' are somewhat unnecessary filler. The 'When to Use This Skill' section repeats the prerequisite already stated. | 2 / 3 |
Actionability | The skill provides extremely concrete, copy-paste-ready format templates for all three output files (pitch.md, slides.md, kimi-prompt.md), specific construction rules ('1 idea per slide', 'max 10 words'), anti-patterns to avoid, and step-by-step instructions for using the Kimi prompt. Every deliverable has a precise specification. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: verify inputs → load template → build pitch → build slide spec → generate Kimi prompt → save 3 files. Validation is explicit with a comprehensive checklist including checking for remaining placeholders, timing coherence, and completeness of all deliverables. The prerequisite checkpoint is clearly stated. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections. The Kimi template is appropriately referenced as an external file rather than inlined. Related stages are linked with clear descriptions of their relationship. The format templates are necessarily inline since they define the core output specification. | 3 / 3 |
Total | 11 / 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
4ef3dec
- 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.