BC write-outreach
Cold outreach a person sends to business buyers: email and LinkedIn sequences, a first line per prospect, reply and objection answers, and a read of replies. Use when the marketer says "write a cold email sequence", "what do I send to this list", "write LinkedIn messages for these leads", "how do I reply to this prospect" or "handle this objection", "reply to this demo request", "win back or reconnect with accounts that churned or went quiet", or "why is nobody replying to my outreach". Drafts only; the marketer sends from their own tool. Not for finding the people — use research-audience; not for emails to subscribers or users, or consumer win-back — use email-lifecycle.
Cold outreach a person sends to business buyers: email and LinkedIn sequences, a first line per prospect, reply and objection answers, and a read of replies.
As a process C 61/100 · Has gaps — References files that are not bundled: ../write-report/SKILL.md, ../marketing-guide/SKILL.md, ../claims-gate/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../write-report/SKILL.md - warning
missing-refreference to a missing file: ../marketing-guide/SKILL.md - warning
missing-refreference to a missing file: ../claims-gate/SKILL.md - warning
missing-refreference to a missing file: ../voice-card/SKILL.md - warning
missing-refreference to a missing file: ../run-memory/SKILL.md - warning
missing-refreference to a missing file: ../write-outreach-reply-reader/SKILL.md - warning
missing-refreference to a missing file: ../write-outreach-draft-sequence/SKILL.md - warning
missing-refreference to a missing file: ../write-outreach-outreach-qa/SKILL.md - warning
missing-refreference to a missing file: ../save-to-brain/SKILL.md - warning
missing-refreference to a missing file: <link> - warning
missing-refreference to a missing file: ../outcomes-ledger/SKILL.md - warning
missing-refreference to a missing file: ../save-learning/SKILL.md
Process rating: all ten parameters 61/100
- 0Tools and files. 12 referenced file(s) missing: ../write-report/SKILL.md, ../marketing-guide/SKILL.md, ../claims-gate/SKILL.md
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 36 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4040 tokens
- 100Steps. 29 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (11 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 680: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (9 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.