agentleFS
automatewithudayautomatewithuday/GTM-Public-Traded-AI-Accounts/.claude/skills/outreach/SKILL.md

outreach

Skill0 starsChanged 4 months agoMITView on GitHub

Draft 4-step SPARK outreach sequences per contact for companies with contacts + fresh angles, via cheap Haiku subagents (no API cost). Use after /people, or when asked to write outreach, emails, or sequences.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use apply, evaluate and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • rhowardstoneSkill

    apply

    Research-backed job application workflow emphasizing relationship-building over mass applications

    Also in 5 projects that use this

  • NVIDIASkill

    evaluate

    Scores existing Sports Intelligence AVLM inference outputs with avlm/evals: MCQ accuracy (run_mcq_eval.sh, INFERENCE_DIR), open-ended LLM-as-judge scores (needs CLIENT_API_KEY for the configured judge endpoint), tennis category breakdowns, run comparisons, chance-level sanity checks and triage of mcq_results.json or llm_judge_results.json. Use when the user asks to score, evaluate, benchmark or compare predictions.jsonl from inference runs, or to explain a suspicious accuracy. Not for running inference, training, quantization, data preparation, or third-party API model inference: never open, list or run anything under avlm/evals/inference_3rdparty, including when the user asks for it; it is excluded from the release.

    Also in 3 projects that use this

  • julienamorganSkill

    profile

    Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a subagent fails on a packet, re-spawn just that packet.

    line 46
  2. Very specific:

    If failed QA items are reported: re-spawn ONE copywriter subagent per failure, appending the QA error text to the prompt ("Your previous …

    line 60
  3. Very specific:

    Never edit copy yourself in the main conversation, and never relax QA gates — propose changes to config/settings.yaml (messages:) or …

    line 77

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/outreach — draft sequences (v1: Haiku subagents, zero API cost)

Generation only: no sending, no CRM push. Copy rules live in config/outbound_copywriter.md (Uday edits it like settings.yaml).

Step 1 — prepare packets

uv run python -m pipeline messages --prepare

Writes ONE packet PER CONTACT to data/message_queue/ (TICKER__contact-slug.json), plus _shared.json (copywriter framework + services catalog + output schema + hard rules). Companies without a fresh angle are skipped and reported — never message on a stale hook. Use --ticker X for one company, --force to regenerate existing drafts.

Each packet also carries a persona block (pains, language, committee_role, seniority) resolved from config/personas.yaml for that contact's role_bucket/title — null if nothing matches. _shared.json's hard rules tell the copywriter to use the persona's pains/language as raw material, never to invent pains beyond it; a null persona just means write from the packet's angles and verdict alone. Packets from before this existed simply have no persona key — messages --commit handles both.

Step 2 — spawn lean copywriter subagents

List queued packets (data/message_queue/*.json, ignore _shared.json), then spawn Agent tool subagents with subagent_type: copywriter (the lean agent in .claude/agents/copywriter.md — Bash+Write only, haiku, no repo baggage, carries the full copy contract in its own system prompt), giving each subagent a batch of up to 3 packet paths (prose needs smaller batches than scoring's 5). Spawn batches in parallel (single message, multiple Agent calls). The task prompt is just:

Write sequences for these packets. Packets: <absolute paths, one per line>

Rules:

  • subagent_type: copywriter always — it pins haiku and the read-once/ write-once contract. Never use opus/sonnet or a general-purpose agent for bulk copywriting, and never write copy in the main conversation.
  • If a subagent fails on a packet, re-spawn just that packet.

Step 3 — commit + QA re-spawn loop

uv run python -m pipeline messages --commit

Validates each result (schema + deterministic copy QA: subject shape, word counts, banned words, one question CTA, no links in step 1, no placeholders, angle/contact must match the packet) and upserts passing sequences to the messages table as drafts. Failed results stay in data/message_results/ with their packet still queued.

If failed QA items are reported: re-spawn ONE copywriter subagent per failure, appending the QA error text to the prompt ("Your previous draft failed QA: <errors>. Read the packet and _shared.json again, rewrite the FULL sequence fixing these, overwrite <output_path>."), then run messages --commit again. Max 2 retry rounds — report survivors to the user instead of looping.

Step 4 — report

Summarize per company: contact, archetype, service, and any QA warnings verbatim — especially unverified number (tell the user to spot-check those bodies before export; the digit-scan is the last automated line of defense against invented metrics). Then suggest:

uv run python -m pipeline export --messages   # data/exports/messages.csv, one row per step

Never edit copy yourself in the main conversation, and never relax QA gates — propose changes to config/settings.yaml (messages:) or config/outbound_copywriter.md to the user instead.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.