Content
71%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 highly actionable body with complete JSON payloads, explicit gating conditions, and precise state-machine rules for every operation. Its main weaknesses are a monolithic 650-line structure with no reference files and duplicated requester-report material that inflates token cost.
Suggestions
Move the Project Status Reports template, Post-Action Notification details, and Pause/Resume/Complete sections into reference files (e.g., references/report-template.md, references/notifications.md) and link them from SKILL.md.
Deduplicate the requester-report delivery and artifact-publish steps that appear in both "Accepting Worker Results" and "Project Status Reports"; state the protocol once and cross-reference it.
Add error-recovery guidance for tool failures (e.g., retry behavior when projectflow returns an error) to complete the workflow feedback loop.
Trim the localized-placeholder report envelope to one compact example instead of the fully elaborated template.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most content is TeamHarness-specific protocol Claude cannot know, but it could be tightened: the requester-report delivery and artifact-publish steps are duplicated across "Accepting Worker Results" and "Project Status Reports", "Use this skill when maintaining durable project state" is stated twice near the top, and the localized-placeholder report envelope is padded. This matches 'mostly efficient but could be tightened' rather than the noticeably-verbose anchor below. | 3 / 5 |
Actionability | Fully executable throughout: complete copy-paste JSON payloads for every projectflow action, exact file paths ("shared/projects/{project-id}/meta.json"), a safe-ID regex, allowed loop decision enums, and precise submissionId fencing rules — matching the 'copy-paste ready; specific examples cover the common cases' anchor. | 5 / 5 |
Workflow Clarity | Clear numbered sequences with explicit checkpoints ("send that message only after the tool returns ok: true", "After teamharness-task-delegation checks the task and returns effective: true"), but error-recovery feedback loops are largely absent — e.g., no guidance on what to do when a tool call itself fails — so it falls short of the anchor above. | 4 / 5 |
Progressive Disclosure | Section headers are clear and well-organized, but the ~650-line body inlines everything — the full status-report template, post-action notification protocol, and pause/resume/complete lifecycle — with no bundle reference files to split content into. This matches 'some structure but content that should be separate is inline' rather than the minimal-structure anchor, since navigation within the file is good. | 3 / 5 |
Total | 15 / 20 Passed |