Content
63%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 content is highly actionable with concrete code, exact prompts, and well-sequenced validation/test loops, but it is verbose due to heavy triplication across providers and monolithic rather than progressively disclosed. Splitting provider wizards and reference material into bundle files would notably improve both conciseness and progressive disclosure.
Suggestions
Extract the repeated per-provider wizard scaffolding ("How This Skill Works", event-config, env-var alternative, detect-existing-config) into a shared section or reference file to remove triplication and recover token budget.
Move the Hook Event Templates and Custom Integration sections into separate reference files (e.g., HOOK_TEMPLATES.md, CUSTOM_INTEGRATIONS.md) and link to them one level deep from SKILL.md.
Resolve or remove the dangling "Related" references to src/notifications/*.ts, which do not exist in the skill bundle and cannot be navigated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is concrete and avoids explaining concepts Claude already knows, but it triplicates substantial boilerplate across the Telegram, Discord, and Slack wizards ("How This Skill Works", event config, env-var alternative, detect-existing-config), which could be factored out; this places it at "mostly efficient but could be tightened" rather than lean. | 3 / 5 |
Actionability | It provides copy-paste-ready bash using jq/curl, exact AskUserQuestion prompts with option text, and explicit validation patterns (token format, webhook URL prefixes); it sits just below 5 because several write-config scripts reference shell variables (BOT_TOKEN, WEBHOOK_URL) that are placeholders rather than set in-block. | 4 / 5 |
Workflow Clarity | Each wizard is a clearly sequenced Step 1..N flow with explicit validation checkpoints and a test-then-debug feedback loop (e.g., token pattern validation with retry, test notification with decoded HTTP errors); it misses 5 because the "disable unselected events" handling is hand-wavy and some custom-integration sub-flows branch without explicit checkpoints. | 4 / 5 |
Progressive Disclosure | The body is well-structured with a routing section and clear provider/feature headers, but it is a ~1200-line monolith where per-provider wizards, hook templates, and custom-integration flows are all inlined rather than split into reference files; the only "Related" references point to non-existent source paths (src/notifications/*.ts), so there are no real one-level-deep bundle references to navigate. | 3 / 5 |
Total | 14 / 20 Passed |