Content
61%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.
The body is lean and centers on one concrete, executable command with a clear single-purpose workflow, but it duplicates its trigger conditions twice and lacks any validation step for what is a batch file-overwrite operation. The bundled sync script is also never referenced, leaving a small gap between the invoked command and the actual implementation.
Suggestions
State the trigger conditions once (either the opening sentence or the When-to-use section) and drop the duplicate to tighten the body.
Add a verification checkpoint before confirming to the sender, e.g., check the command's success output or `~/.last-pull` marker, since the sync batch-overwrites local files.
Reference the implementation explicitly (e.g., `scripts/agentteams-sync.sh`) or clarify how `agentteams-sync` resolves to it, so the command and the bundle file clearly correspond.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening sentence ("When your coordinator or another Worker notifies you that files have been updated...") and the "**When to use**" paragraph ("any time you are told that new files are available, configs have changed...") state the same trigger conditions twice, mirroring the frontmatter. This is more than minor padding, so it sits at "mostly efficient but could be tightened" rather than anchor 4. | 3 / 5 |
Actionability | The body gives a concrete, copy-paste-ready command (```bash\nagentteams-sync\n```) plus a follow-up action ("Always confirm to the sender after sync completes"), which is mostly executable guidance. Not 5 because the invoked command `agentteams-sync` does not match the bundled `scripts/agentteams-sync.sh`, and there is no guidance for the failure path. | 4 / 5 |
Workflow Clarity | The sequence (receive notification → run `agentteams-sync` → confirm to sender) is present and unambiguous, but the sync is a batch overwrite operation pulling many files, and the body includes no validation that the sync succeeded — "confirm to the sender" is a notification, not a checkpoint. Per the rubric's cap for batch operations without validation, workflow clarity cannot exceed 3. | 3 / 5 |
Progressive Disclosure | The body is appropriately minimal for a single-task skill (~10 lines, organized with a When-to-use callout), but the bundle's `scripts/agentteams-sync.sh` is never referenced and the command name does not obviously map to it, leaving a minor navigation gap. This matches "good structure; most content appropriately placed; minor organization gaps" rather than the clean top anchor. | 4 / 5 |
Total | 14 / 20 Passed |