SKILLEMALL.ai
GitHub ↗ RU Sign in

BD write-outreach-reply-reader

Step of the write-outreach playbook: sorts outreach replies by type, matches each to its prospect row, sets that person's status and keeps useful exact words. Run write-outreach instead; not for direct use.

athina-ai/goose-skills Agent Skills author: athina-ai 2 files body ≈ 536 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Step of the write-outreach playbook: sorts outreach replies by type, matches each to its prospect row, sets that person's status and keeps useful exact words.

As a process D 36/100 · Unfinished process — References files that are not bundled: ../write-outreach/references/replies-and-objections.md

ProcedureSales and CRMtype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
D
36/100
Unfinished process
References files that are not bundled: ../write-outreach/references/replies-and-objections.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: write-outreach-reply-reader (gooseworks-ai/goose-skills)

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../write-outreach/references/replies-and-objections.md

Process rating: all ten parameters 36/100

Will not run. References files that are not bundled: ../write-outreach/references/replies-and-objections.md
  • 0Tools and files. 1 referenced file(s) missing: ../write-outreach/references/replies-and-objections.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 536 tokens

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Structure: 1 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 206: enough signal without eating the budget
  • +3Step-by-step instructions: 5 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.