Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, operationally precise skill body that gives concrete commands, exact clarification prompts, and a validated hand-off sequence. Weakest on actionability and workflow_clarity where behavioral policy and one placeholder command prevent a top score.
Suggestions
Replace the '--since <cursor>' placeholder with a concrete example value or a one-line note on what a cursor token looks like, so the bounded-read command is fully copy-paste ready.
Add a short numbered summary of the core live-session loop (acknowledge user -> bounded read -> answer in posture -> defer proactive nudges) so the mid-skill workflow is as explicitly sequenced as the hand-off section.
If any posture-specific guidance grows, move the per-posture detail into a referenced file to keep SKILL.md an overview and push progressive_disclosure toward 5.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean, directive prose that assumes competence and avoids explaining concepts Claude already knows; every section states operational rules (finals vs current_draft, foreground priority, evidence provenance) that earn their place for a genuinely complex live-meeting context. | 5 / 5 |
Actionability | Provides concrete, copy-paste-ready commands ('minutes transcript --status', 'minutes transcript --since 2m --include-current', 'minutes stop') and an exact posture menu, but a meaningful portion is behavioral policy and one argument ('--since <cursor>') is a placeholder rather than a literal value. | 4 / 5 |
Workflow Clarity | Sections form a clear sequence (select surface -> establish contract -> attach -> respect foreground -> end/hand off), and the hand-off section is an explicit numbered list with validation checkpoints (check status, report processing state, wait for finalized artifact before debrief); the mid-skill flow is section-based rather than strictly numbered, leaving minor gaps. | 4 / 5 |
Progressive Disclosure | Well-organized into clearly headed sections with no nested or buried references; all content is appropriately inline because it is needed at runtime during a live meeting, though at ~100 lines it exceeds the under-50-line simple-skill exception that would allow a 5 with sections alone. | 4 / 5 |
Total | 17 / 20 Passed |