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.
Install with Tessl CLI
npx tessl i github:supercent-io/skills-template --skill standup-meeting84
Quality
77%
Does it follow best practices?
Impact
99%
1.20xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/standup-meeting/SKILL.mdDiscovery
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 that clearly communicates its purpose and includes explicit 'Use when' guidance. The trigger terms are natural and specific to the agile standup domain. The main weakness is that the specific capabilities could be more concrete—listing specific outputs or techniques rather than general categories like 'standup format' and 'time management'.
Suggestions
Expand specificity by listing concrete actions like 'generate standup agendas, summarize updates, track action items, identify recurring blockers'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (daily standup meetings, agile teams) and mentions 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 | Good coverage of natural terms users would say: 'standup', 'standups', 'daily standup', 'blockers', 'agile teams', 'team synchronization'. These are terms users would naturally use when seeking help with standup meetings. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on daily standup meetings with distinct triggers like 'standup', 'blockers', and 'agile teams'. Unlikely to conflict with general meeting or project management skills due to specific agile/standup terminology. | 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.
The skill provides actionable, concrete templates for running standups in multiple formats, which is its primary strength. However, it suffers from structural issues - the 'Steps' are actually alternative approaches rather than a workflow, and there's unnecessary metadata and empty placeholder sections that waste tokens. The skill would benefit from clearer organization distinguishing between standup format options.
Suggestions
Rename 'Step 1/2/3' to 'Option 1/2/3' or 'Format A/B/C' since these are alternative approaches, not sequential steps
Remove the empty Examples section placeholders and the Metadata/Tags sections which don't help Claude execute the skill
Add a brief decision guide at the top for when to use each standup format (e.g., 'Use Walking the Board when sprint progress is the focus')
Add a validation checkpoint for blocker resolution follow-up (e.g., 'Check previous day's action items at start of standup')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes useful templates but has unnecessary sections like Metadata, empty Examples placeholders, and verbose formatting. The References and Tags sections add little value for Claude's execution. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready templates for multiple standup formats (3 Questions, Walking the Board, Async). The markdown templates are immediately usable with clear structure and examples. | 3 / 3 |
Workflow Clarity | Steps are labeled but the relationship between Step 1, 2, and 3 is unclear - they appear to be alternative formats rather than sequential steps. No validation checkpoints for ensuring standup effectiveness or blocker resolution follow-up. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The empty Examples section and external references could be better structured. No clear signaling of what's essential vs. advanced. | 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 | |
- 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.