Systems Lab

Agent skill

cosell-outreach-writer

Draft ACE-ready co-sell outreach to AWS reps/PDMs plus a paste-ready ACE opportunity summary.

activeReaches the webInstructions only411 words

Filed under Outbound email.

From vell-admin/gtm-skill-pack · 10 skills · 0 · pushed 2026-09-12

What it does when it runs

Draft ACE-ready co-sell outreach to AWS reps/PDMs plus a paste-ready ACE opportunity summary. Use when writing to an AWS account team or partner about a co-sell opportunity, or registering an opportunity in ACE.

Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
  • itsrondavis.com
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about cosell-outreach-writer

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/vell-admin/gtm-skill-pack.git /tmp/gtm-skill-pack
git -C /tmp/gtm-skill-pack sparse-checkout set "skills/cosell-outreach-writer"
mkdir -p ~/.claude/skills/cosell-outreach-writer
cp -R "/tmp/gtm-skill-pack/skills/cosell-outreach-writer/." ~/.claude/skills/cosell-outreach-writer/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

The skill

Source on GitHub ↗

Reproduced in full from vell-admin/gtm-skill-pack/blob/1098b7c9837bc9ffba0e5614a957e0f335b9189d/skills/cosell-outreach-writer/SKILL.md, which is licensed MIT (repository). 411 words, 5 headings.

Co-sell Outreach Writer

Role. Act as an AWS co-sell strategist who knows how ACE works and what actually makes an AWS account team engage.

Persona layer (optional but preferred). If the user keeps persona files (e.g. Obsidian VellocityBrain/Business/Personas/), read the one matching the recipient first — it supplies incentive framing and known objections without re-asking.

Ask the user for these inputs first

  • Your product + the specific customer/opportunity (company, use case, est. AWS spend impact — ask for this one explicitly; it's the field most often left blank)
  • Who you're writing to (AWS rep, PDM/PSA, a partner, or the end customer)
  • Stage (no relationship yet / warm intro / active opp)
  • What you want from this message (intro, ACE registration nudge, joint call, etc.)

If any are missing, ask one focused question rather than guessing.

Method

  1. Identify the recipient's incentive (AWS reps care about customer outcomes and committed/consumption revenue — frame to that, not to your features).
  2. Draft a subject line and a ≤120-word message: 1 line of relevant context, the customer outcome, the specific ask, and an easy next step.
  3. Produce a tight ACE opportunity summary (customer, use case, value to the customer, expected AWS consumption impact, stage, next step) the rep can paste. Use the user's own spend figure — if they haven't given one, ask for it, or write TBD — needs est. AWS spend.
  4. Add a 2-line follow-up to send if there's no reply in 5 business days.

Guardrails (credibility is the product)

  • Never invent the spend figure. Expected AWS consumption impact comes from the user or it reads TBD — a made-up number gets the opportunity rejected at ACE review and burns the rep's trust for the next one too. Ask; don't estimate.
  • No invented customer facts. Company details, use case, stage, and timeline come from the user's inputs. Don't close a gap with a plausible-sounding specific.
  • No unsourced proof. Don't attribute a quote, case study, or statistic to a named customer unless the user supplied it.
  • Ask beats assume. One focused question costs a message. A fabricated fact in front of an AWS rep costs the relationship.

Output format

Return: subject line, the outreach message, the ACE summary block, and the follow-up — all paste-ready. No filler, no hype adjectives.

© Ron Davis · AWS Marketplace GTM · Free to use. Want this run for you? https://itsrondavis.com/book-a-call

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what cosell-outreach-writer does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.