Content
73%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 an unusually strong operational skill document: a clear sequenced lifecycle with explicit validation checkpoints, recovery loops, cost gating, and a strict output contract, all written leanly. Its one serious defect is progressive disclosure — all ten referenced markdown files are missing from the bundle while the eight provided reference files and twelve scripts are never mentioned, leaving both navigation and the bulk of the bundle content unreachable. Fixing the link structure would raise this substantially.
Suggestions
Ship the missing linked files (writing-outreach.md and the nine recipes/*.md) or rewrite the 'Specialized recipes' and Monitors sections to point at files that exist.
Link the existing bundle from SKILL.md — e.g. the monitors section should reference references/monitor-contract-reference.md and monitor-operations.md, and Clay conversion should reference scripts/clay-to-deepline.mjs and references/clay-action-mappings.md — so the provided material is discoverable.
Trim the opening platform pitch, which restates the description, and split the dense staleAfterSeconds reuse paragraph in section 6 into a short rule list.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, imperative, and free of concept explanations Claude already knows — commands, rules, and templates only (e.g. "Save files you link in the user's working directory, never a temp directory"). Minor trimmable spots keep it below anchor 5: the opening pitch line ("a GTM tool routing and automation platform for any ad-hoc or automated GTM task, with thousands of tools...") duplicates the description, and the `staleAfterSeconds` reuse paragraph in section 6 packs many rules into one long block. Well above anchor 3 — there is no real padding. | 4 / 5 |
Actionability | Concrete, runnable guidance throughout: exact command lines ("deepline run <name> --input '{...}' --dry-run", "deepline plays check <file>", "deepline runs export <run-id> --dataset <name> --out <file.csv>"), a complete executable Play example, and a copy-paste approval message template. Below anchor 5 because several key steps rely on placeholders and deferred detail ("<input you have -> result you need>", "filter, join and aggregate them with read-only SQL" via "<suggested SQL>", "follow the printed instructions") rather than concrete examples of the common cases. | 4 / 5 |
Workflow Clarity | A clear numbered lifecycle (1 choose what to run → 2 run it → 3 get results → 4 scope and spend → 5 deliver → 6 automate → 7 feedback) with explicit validation checkpoints and error-recovery loops for batch and paid operations: `--dry-run` and `deepline describe` before first calls, "`deepline plays check <file>` # required before running local source", pilot sampling ("run a small representative sample... Stop for a decision on wrong matches, low coverage or a changed cost"), delivery verification ("verify row count, identity and requested columns... read the file back with a strict reader"), and recovery paths ("After a timeout, reconnect with `deepline runs watch <run-id>`; do not launch the run again"). This matches the anchor-5 pattern of explicit validation with feedback loops. | 5 / 5 |
Progressive Disclosure | Every markdown link in the body is dangling: "[outreach copy](writing-outreach.md)" and the nine "recipes/*.md" links (account-orgchart, build-tam, clay-to-deepline, developer-signals, deepline-monitors, find-qualified-titles, portfolio-prospecting, small-business-prospecting) point to files that do not exist anywhere in the bundle. Meanwhile the provided bundle content — 8 files in references/ (monitor-contract-reference.md, clay-action-mappings.md, run-events.md, etc.) and 12 in scripts/ — is never linked from SKILL.md at all, so it is undiscoverable. Scored against the actual bundle per the rubric guideline, this is anchor 2: navigation is effectively broken and real bundle files are orphaned; not 3 because the problem is not unclear signaling but non-resolving links, and the body itself does have clear section structure keeping it above anchor 1. | 2 / 5 |
Total | 15 / 20 Passed |