Content
88%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 high-quality operational skill: every step is backed by an executable command, the workflow is well-sequenced with verification and a failure-diagnosis branch, and the troubleshooting section anticipates real failure modes with concrete fixes. The main improvement opportunity is structural — moving the channel-specific resolution matrix and pair-code details into a one-level-deep reference file would trim the main body further.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and nearly every token carries repo-specific knowledge Claude could not know (CLI flags, DB schemas, adapter policies); it does not explain general concepts. A few spots could still be tightened — e.g. the unknown_sender_policy two-level model explanation in Troubleshooting and the provider-selection paragraph in step 5 run slightly long. Not a 5 because a handful of sentences restate what the surrounding commands already show; not a 3 because there is no padding or taught material. | 4 / 5 |
Actionability | Fully executable throughout: complete copy-paste commands with exact flags (`pnpm exec tsx scripts/q.ts data/v2.db "SELECT ..."`, `npx tsx scripts/init-first-agent.ts --channel ... --platform-id ...`, `ncl groups list --json`), explicit variable conventions (CHANNEL lowercase, PLATFORM_ID=${CHANNEL}:${USER_HANDLE}), and exact per-step user prompts. Placeholders are all defined earlier in the flow. | 5 / 5 |
Workflow Clarity | Six numbered steps in a coherent sequence with prerequisites up front, an explicit validation step (step 6 asks the user to confirm receipt), and a diagnosis branch with concrete DB/log checks if the welcome DM does not arrive. Troubleshooting maps each failure mode to a fix, and idempotency is stated up front. The skill is non-destructive and idempotent, so the missing-validation cap does not apply. | 5 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/), so the skill is a self-contained single file with clear section headers (Prerequisites, steps 1–6, Troubleshooting) — well-organized and easy to navigate. It falls short of 5 only because at ~145 lines some channel-specific detail (the per-channel cold-DM resolution matrix and the pair-code path) would sit more appropriately in a one-level-deep reference file; it is not a 3 because what is inline is clearly sectioned and nothing is buried. | 4 / 5 |
Total | 18 / 20 Passed |