write-outreach-outreach-qa

write-outreach-outreach-qa is a skill for Claude Code, Codex from gooseworks-ai/goose-skills. It costs 55 tokens per session (602 once invoked), scanned A, original, MIT.

A quality-checking workflow for a completed cold-outreach pack and its send file. It checks prospect facts, evidence, product claims, message length, requests, tone, and rules for different countries.

In plain words
What is it for?
Use it to verify opening lines against dated source links, confirm approved claims and product facts, exclude suppressed or duplicate contacts, and check required compliance wording. Run the main outreach workflow to create the pack first.
Why use it?
It removes the risk of sending messages with invented details, unsupported proof, missing opt-out information, or the wrong treatment of restricted contacts. It gives the marketer a final set of issues to fix before sending.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to verify opening lines against dated source links, confirm approved claims and product facts, exclude suppressed or duplicate contacts, and check required compliance wording. Run the main outreach workflow to create the pack first.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gooseworks-ai/goose-skills/write-outreach-outreach-qa
About the project

Goose Skills is a library of workflows and data APIs that lets coding agents handle growth and go-to-market work such as advertising, social media, content, SEO, lead generation, and customer research. It is intended for teams using Claude Code, Cursor, Codex, and similar agents. The catalogue entries are its reusable skills.

gooseworks-ai/goose-skills · 1,265 stars · on GitHub · gooseworks.ai

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add gooseworks-ai/goose-skills --skill write-outreach-outreach-qa
Clone the repo
git clone --depth 1 https://github.com/gooseworks-ai/goose-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-outreach-outreach-qa

README.md
[![agentmods](https://agentmods.dev/badge/skills/gooseworks-ai/goose-skills/write-outreach-outreach-qa/github.svg)](https://agentmods.dev/skills/gooseworks-ai/goose-skills/write-outreach-outreach-qa)
Your own site
<a href="https://agentmods.dev/skills/gooseworks-ai/goose-skills/write-outreach-outreach-qa"><img src="https://agentmods.dev/badge/skills/gooseworks-ai/goose-skills/write-outreach-outreach-qa/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-outreach-outreach-qa

Your own site · 80×15
<a href="https://agentmods.dev/skills/gooseworks-ai/goose-skills/write-outreach-outreach-qa"><img src="https://agentmods.dev/badge/skills/gooseworks-ai/goose-skills/write-outreach-outreach-qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 602 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.00602
Opus 5.5 $0.00022 $0.00241
Sonnet 5.5 $0.00011 $0.00120
Haiku 4.5 $0.00006 $0.00060

Measured 4d ago against content hash e862f7fe1e6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-outreach-outreach-qa scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

marketing-agent/skills/write-outreach-outreach-qa/SKILL.md · 35 lines

What it actually says

outreach-qa

Run on the whole pack and the send file. Fix every failure, then run again. Nothing about the check goes into the pack itself.

Facts and proof

  • Every first line rests on its row's signal or hook URL and date (signal_1_date / hook_date); the fact still says that (a sample of 5 rows re-checked by link, or every row when under 10).
  • No invented compliment, mutual connection, number, customer, result, peer story, "brands like X", "most teams we talk to". Every proof line went through claims-gate; cuts are listed with the proof that would restore them.
  • Prices and product facts match the brand's site or brain, with the date read.

Compliance

  • Each email has the sender's name and company, a postal address placeholder the marketer fills once, and the opt-out line.
  • Row rules applied: no email body for UK-soletrader (letter instead), non-published CASL / AU-NZ, Germany/Austria rows; unchecked and catch-all addresses sit in email_to_check, never email; EU and unknown-country first emails carry the source-and-object line; the one-line country summary is in the pack.
  • Suppressed, cooled-down and duplicate rows are out of the send file, with counts.

Craft

  • Touch 1 50–90 words (fail over 120); follow-ups shorter; subjects under 50 characters (fail over 60); connection notes ≤200 characters (≤300 only if the marketer said paid).
  • At most 6 touches per person; one ask per message; no calendar link to a stranger in touch 1; no attachment; at most one link.
  • No banned words or openers (email-craft.md § Hard rules); nothing about us in the first sentence.
  • Follow-ups each add something new; LinkedIn text differs from the email.
  • Swap test: swap two rows' first lines — if they still fit, they're generic; rewrite.

The pack

  • The brand copy holds no person's name, company or first line.
  • write-report §3 passes; its first move is who to send to first and why (with no list, that there is no one yet). Outside tools the marketer runs (an email finder, a checker, a sending tool) may be named as examples, never endorsed.
  • The send file imports: header row, one subject and body column per touch, no merged cells, UTF-8.
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 35 lines · 55 tokens per session scan A e862f7fe1e6c

Subscribe to this mod's changes

write-outreach-outreach-qa is a skill published in the GitHub repository gooseworks-ai/goose-skills (1,265 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 602 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-21.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens