talk-stage4-position
Generates 3-4 strategic talk angles with strength/weakness analysis, title options, CFP descriptions, and a peer feedback draft, then enforces a mandatory CHECKPOINT for user confirmation before scripting. Use when deciding how to frame a talk, preparing a CFP submission, or choosing between multiple narrative angles.
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that clearly articulates specific deliverables (talk angles, strength/weakness analysis, title options, CFP descriptions, peer feedback draft), includes a distinctive workflow element (mandatory CHECKPOINT), and provides explicit trigger guidance with natural user terms. It covers the full what/when spectrum and occupies a clear, distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generates 3-4 strategic talk angles, strength/weakness analysis, title options, CFP descriptions, peer feedback draft, and enforces a mandatory CHECKPOINT. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both what (generates strategic talk angles with analysis, titles, CFP descriptions, feedback draft) and when ('Use when deciding how to frame a talk, preparing a CFP submission, or choosing between multiple narrative angles'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'talk angles', 'CFP submission', 'frame a talk', 'narrative angles', 'title options'. These are terms a user preparing a conference talk would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on conference talk preparation and CFP submissions. The specific mention of talk angles, CFP descriptions, and the CHECKPOINT workflow makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 well-structured, highly actionable skill with a clear multi-step workflow and a critical CHECKPOINT gate that enforces user confirmation before proceeding. Its main weakness is verbosity — the extensive inline output templates inflate the token cost significantly and could be externalized. The anti-patterns and validation checklist are strong additions that prevent common mistakes.
Suggestions
Move the detailed output format templates (angles.md, titre.md, descriptions.md) into separate reference files and link to them from the SKILL.md to reduce inline verbosity and improve progressive disclosure.
Provide the referenced templates/feedback-draft.md bundle file, since the skill explicitly links to it but it's not present in the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but verbose for what it conveys. The extensive markdown format templates (angles.md, titre.md, descriptions.md) take up significant space and could be more compact. Some sections like 'Tips' and 'When to Use This Skill' add moderate value but could be tightened. However, it doesn't over-explain basic concepts. | 2 / 3 |
Actionability | The skill provides highly concrete, copy-paste-ready output templates with exact file naming conventions, specific markdown structures, word count targets, and a verbatim CHECKPOINT message to display. The angle generation rules, anti-patterns, and validation checklist give precise, actionable constraints rather than vague guidance. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced with explicit inputs, outputs, and a mandatory CHECKPOINT gate before proceeding. The CHECKPOINT serves as a critical validation/confirmation step with explicit instructions to halt and wait for user confirmation. The validation checklist provides a final verification loop. Anti-patterns section guards against common failure modes. | 3 / 3 |
Progressive Disclosure | The skill references external files (templates/feedback-draft.md, related stages) appropriately, but the inline format templates for angles.md, titre.md, and descriptions.md are quite lengthy and could be split into separate reference files. The body content is somewhat monolithic with all templates inline rather than referenced. However, no bundle files were provided to confirm the referenced template exists. | 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.