standup-meeting
Conduct effective daily standup meetings for agile teams. Use when facilitating standups, tracking blockers, or improving team synchronization. Handles standup format, time management, and blocker resolution.
84
77%
Does it follow best practices?
Impact
99%
1.20xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/standup-meeting/SKILL.mdQuality
Discovery
89%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-structured skill description with explicit 'Use when' guidance and good trigger term coverage for agile standup scenarios. The main weakness is that the specific capabilities could be more concrete - listing actual outputs or techniques rather than general categories like 'standup format' and 'time management'.
Suggestions
Add more concrete actions to specificity, e.g., 'Generate standup agendas, summarize updates, track action items, escalate blockers' instead of general categories like 'handles standup format'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (daily standup meetings, agile teams) and some actions (facilitating standups, tracking blockers, improving team synchronization), but lacks comprehensive concrete actions like specific facilitation techniques or output formats. | 2 / 3 |
Completeness | Clearly answers both what ('Conduct effective daily standup meetings', 'Handles standup format, time management, and blocker resolution') and when ('Use when facilitating standups, tracking blockers, or improving team synchronization') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'standup', 'standups', 'blockers', 'agile teams', 'team synchronization', 'daily standup meetings'. Good coverage of terms someone needing this skill would use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on daily standups and agile ceremonies. The combination of 'standup', 'blockers', and 'agile teams' creates distinct triggers unlikely to conflict with general meeting or project management skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable standup templates that Claude can immediately use, which is its main strength. However, it suffers from structural issues: the 'Step 1, 2, 3' labeling misrepresents alternative formats as sequential steps, there's redundant content across similar templates, and the metadata/empty examples sections waste tokens without adding value.
Suggestions
Rename 'Step 1, 2, 3' to 'Format Option 1, 2, 3' or use headers like '## 3 Questions Format', '## Walking the Board Format' to clarify these are alternatives, not sequential steps
Remove the empty Examples section and the Metadata section (version, tags, supported platforms) as these don't help Claude facilitate standups
Add an explicit facilitation workflow: 1) Start on time, 2) Each person answers 3 questions, 3) Capture blockers, 4) Assign action items, 5) End within 15 min
Consolidate the three full templates into one primary template with brief notes on variations, reducing redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes useful templates but has some redundancy (multiple similar formats shown in full) and unnecessary metadata sections (version, tags, supported platforms) that don't add value for Claude. The empty example placeholders at the end waste tokens. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready templates for multiple standup formats (3 Questions, Walking the Board, Async). The markdown templates are complete and immediately usable with clear structure and realistic examples. | 3 / 3 |
Workflow Clarity | Steps are labeled but the 'Step 1, 2, 3' framing is misleading—these are alternative formats, not sequential steps. The actual workflow of running a standup (prepare, facilitate, capture action items, follow up) is implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The References section links to external resources but there's no indication of related internal files. The empty Examples section at the end suggests incomplete structure. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.