agentleFS
alsy99alsy99/agent-enterprise-os/skills/sales-outbound/SKILL.md

sales-outbound

Skill0 starsChanged 2 months agoMITView on GitHub

First-touch email after research pack. Use when a new lead is qualified and the research pack includes the Unknown checklist. Draft only — never send without human approval.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. peter-tu-zynkr/zynkr-skill-builder★ 21same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If actor was also Gemini and you need family diversity, use verifier (Groq gpt-oss)

    line 22
  2. Very specific:

    Read the research pack / wiki page.

    line 28
  3. Distinctive:

    Write 3 evidence bullets (why them, why now, why us) — no invented proof.

    line 29
  4. Very specific:

    Run verifier: reject overclaims.

    line 32
  5. Very specific:

    Stop. Wait for human APPROVE_SEND.

    line 33
  6. Distinctive:

    No email send, no calendar book

    line 39
  7. Distinctive:

    No fake logos, metrics, or case studies

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

When to use

  • Lead is qualified (see sops/sales-qualify.md)
  • Research pack path exists from market-research
  • Research pack contains ## Unknown checklist and all five rows (Headcount / team size, Shipping status of cited features, Decision-maker path, Timeline ≤90 days, Willingness to talk / design-partner interest)

Models

  • Actor: worker (Gemini Flash-Lite)
  • Verifier: planner (Gemini Flash, different prompt — reject overclaims)
    • If actor was also Gemini and you need family diversity, use verifier (Groq gpt-oss)
  • Resolve: ./scripts/resolve-model.sh sales-outbound / ... verifier

Steps

  1. Confirm qualification via sops/sales-qualify.md.
  2. Read the research pack / wiki page. Stop if ## Unknown checklist or any of the five rows is missing — run market-research first; do not draft.
  3. Write 3 evidence bullets (why them, why now, why us) — no invented proof.
  4. Draft email (subject + body ≤150 words) into artifacts/outreach-drafts/<slug>.md.
  5. Set send_status: awaiting_approval in that file.
  6. Run verifier: reject overclaims; fail if status is not awaiting_approval.
  7. Stop. Wait for human APPROVE_SEND.

Tools allowed

  • Wiki / SOP read
  • Write under artifacts/outreach-drafts/
  • No email send, no calendar book

Definition of done

  • Research pack has full Unknown checklist (five rows) before drafting
  • Draft file exists with subject, body, evidence, send_status: awaiting_approval
  • Evidence cites research pack paths
  • No fake logos, metrics, or case studies
  • Verifier pass

Never do

  • Draft when the lead page lacks ## Unknown checklist or any of the five rows
  • Send email or InMail
  • Invent social proof
  • Quote pricing not in wiki/sales/pricing.md
  • Unsourced comparative claims (“ahead of most”, “best”, category leadership) — mark Unknown or cite a dated source
  • Language that implies the message was already sent (“I sent”, “already sent”, send_status: sent)

Escalation

  • Pricing/legal questions → human
  • Missing research pack → run market-research first
  • Missing ## Unknown checklist or incomplete five rows → run market-research first; do not draft

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.