talk-stage3-concepts
Builds a numbered, categorized concept catalogue from the talk summary and timeline, scoring each concept HIGH / MEDIUM / LOW for talk potential with optional repo enrichment. Use when you need a structured inventory of concepts before choosing a talk angle, or when assessing which ideas have the strongest presentation potential.
75
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/skills/talk-pipeline/stage-3-concepts/SKILL.mdQuality
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 well-crafted description that clearly defines a specific capability (building scored concept catalogues for talk preparation) and explicitly states when to use it. The main weakness is that trigger terms lean toward domain-specific jargon rather than natural user language, which could reduce discoverability when users phrase requests more casually. The description also uses second person ('you need') in the 'Use when' clause, though this is a minor issue since the main action uses third person.
Suggestions
Add more natural trigger terms users might say, such as 'brainstorm talk topics', 'rank ideas for a presentation', or 'which concept should I present on'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: builds a numbered/categorized concept catalogue, scores concepts HIGH/MEDIUM/LOW for talk potential, and includes optional repo enrichment. These are concrete, well-defined actions. | 3 / 3 |
Completeness | Clearly answers both what ('Builds a numbered, categorized concept catalogue...scoring each concept HIGH/MEDIUM/LOW') and when ('Use when you need a structured inventory of concepts before choosing a talk angle, or when assessing which ideas have the strongest presentation potential'). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'concept catalogue', 'talk potential', 'presentation potential', 'talk angle', and 'structured inventory', but these are somewhat domain-specific. Users might more naturally say things like 'brainstorm topics', 'rank ideas', or 'pick a talk topic' which are missing. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: concept cataloguing specifically for talk/presentation preparation, with scoring and categorization. This is unlikely to conflict with other skills due to its very specific domain and workflow position (after summary/timeline, before choosing a talk angle). | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%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 skill that clearly defines the output format, scoring criteria, and categories for concept cataloguing. Its main weakness is the gap between describing what should happen and providing concrete, executable guidance on how to perform the extraction and scoring — the process steps read more like a description than actionable instructions. The validation checklist is a good inclusion but would be stronger if integrated as checkpoints within the workflow.
Suggestions
Add concrete, step-by-step instructions for how to actually extract and score concepts from the summary (e.g., specific patterns to look for, decision trees for scoring, worked example of scoring one concept)
Integrate validation checkpoints into the workflow steps rather than only having a post-hoc checklist — e.g., after extraction, verify count >= 15 before proceeding to scoring; after scoring, verify <= 30% HIGH before writing output
Include a brief worked example showing 3-4 concepts being extracted from a sample summary snippet, with reasoning for their category assignment and score
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary explanation (e.g., 'What This Skill Does' largely repeats what's already clear from the workflow and output sections). The scoring criteria descriptions and category table are useful reference material, but some sections like 'Tips' restate what's already implied. Overall mostly efficient with some tightening possible. | 2 / 3 |
Actionability | The skill provides clear output format templates with concrete markdown structure, scoring criteria, and category definitions. However, it lacks executable commands or concrete code for the actual extraction/scoring process — it describes what to do conceptually ('loads summary', 'extracts concepts', 'scores') without specifying how. The output format is copy-paste ready, but the process steps are abstract. | 2 / 3 |
Workflow Clarity | The 'What This Skill Does' section lists 7 steps in sequence, and there's a validation checklist at the end. However, the workflow lacks explicit validation checkpoints between steps — for instance, there's no guidance on what to do if fewer than 15 concepts are found, or how to verify scoring calibration before writing output. The checklist is post-hoc rather than integrated into the workflow. | 2 / 3 |
Progressive Disclosure | The skill is well-organized with clear sections (When to Use, Input, Output, Scoring Criteria, Output Format, Anti-patterns, Validation, Tips). Related skills are linked with one-level-deep references and clear descriptions of their relationship. The enriched output variant is cleanly separated. Content is appropriately scoped for a single file. | 3 / 3 |
Total | 9 / 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.