AutoGineer
Generated banner for Outreach Composer
Generated logo for Outreach Composer

Outreach Composer

AnthropicOfficialPublished by Anthropic

  • Skill
  • Content generator
  • Business and productivity
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Writes prospect outreach and follow-up sequences that sound like the owner wrote them, not like an AI did. Learns a voice profile from the owner's own sent mail, grounds every message in something specific about that prospect, builds the follow-up sequence behind it, queues every send for approval, and logs each touch to the CRM. Runs draft-only when no mail connector is available, so the copy can be pasted anywhere. Use this whenever the owner needs to reach out to prospects or customers — including phrasings like "write this cold email," "draft a follow-up," "reach out to these leads," "what do I say to them," "I need a sequence for this list," "nudge the people who didn't reply," or "write it but don't make it sound like a robot." Reach for it whenever outreach copy is the deliverable, even for a single message.
— the description by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Outreach Composer generates prospect outreach and follow-up sequences designed to mimic the owner's authentic writing style rather than generic AI output. By learning from the owner's sent emails and grounding each message in specific, verifiable details about the prospect, it creates high-fidelity communication. The skill manages the entire lifecycle, from drafting and self-checking against quality standards to presenting for approval, logging in the CRM, and queuing for delivery.

What it does

  • Learns the owner's unique voice profile from sent emails or provided examples.
  • Grounds messages in specific prospect details to avoid generic templates.
  • Generates multi-touch follow-up sequences tailored to specific scenarios.
  • Validates all drafts against a rigorous quality checklist to ensure human-like tone.
  • Presents sequences for approval before queuing or saving to CRM/marketing tools.
  • Logs all outreach activity to the CRM to prevent duplicate contact.

When to use it

  • When you need to send cold outreach or follow-up emails to prospects.
  • When you want to ensure your outreach sounds like you, not an AI.
  • When you need a structured follow-up sequence for a specific lead list.
  • When you need to re-engage quiet customers with a fresh, relevant angle.

Advantages

  • High voice fidelity prevents the 'robotic' tone common in AI-generated copy.
  • Strict approval gates ensure the owner maintains full control over sent communications.
  • Reduces manual effort by automating the drafting and logging process.
  • Prevents common outreach mistakes like generic flattery or 'just checking in' follow-ups.

Usage examples

“Write a cold email sequence for these 5 leads from the construction industry.”
The agent analyzes the owner's voice, identifies specific hooks for each lead, and drafts a 4-part sequence for each, presented in a visual card format for approval.
“Nudge the people who didn't reply to my last email.”
The agent reviews the CRM logs, identifies the non-responders, and drafts a follow-up message that adds a new, relevant piece of information to re-engage them.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/outreach-composer/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip outreach-composer.zip -d .agents/skills

Documentation by Anthropic

Outreach Composer

Write outreach the owner would actually send under their own name.

The single most repeated condition owners set is some version of "without sounding like a bot." Owners will not send copy that embarrasses them, so a message that reads as generated is worth nothing regardless of how well structured it is. Voice fidelity is the product here, not a finishing touch.

Step 1 — Learn the voice before writing anything

Read the shared voice profile first. If a profile already exists there, use it and skip to Step 2 — rebuilding it every time wastes the owner's patience and produces drift.

If there is no profile, build one from evidence:

  • Gmail or Microsoft 365 — pull 15 to 30 of the owner's own sent messages to customers and prospects. This is the best source by a wide margin. Confirm the mailbox is the owner's first (../../shared/tenant-scope.md); another tenant's sent mail would teach the wrong voice.

  • HubSpot — logged emails and notes

  • Their website and any published writing — weaker, but real

  • Pasted examples — ask for three emails they were happy with

Then extract the specific, imitable traits: sentence length, greeting and sign-off habits, contractions, whether they use exclamation marks, how direct the ask is, what they call their own product, regionalisms, and the things they never do. Save the profile so every later run inherits it.

Without any sample, say so and ask for three. Writing in a guessed voice produces exactly the generic copy the owner is trying to avoid.

Step 2 — Ground each message in something real

A personalized email is not one with the company name merged into a template. It is one that could only have been sent to that person.

For each prospect, find the specific hook. In order of strength:

  1. The buying signal from lead-finder — a permit filed, a location opened, a role posted

  2. A shared connection or customer

  3. Something specific about their business the owner can genuinely speak to

  4. A relevant result the owner produced for a similar customer

If no hook exists beyond category fit, write a shorter, plainly cold message and say it is cold. A fake-warm opener is worse than an honest cold one, because it reads as a mail merge and destroys credibility in the first line.

Apollo or Clay, when connected, can fill in the contact and company detail that makes a thin hook usable — role, tenure, company size, tech stack — the kind of specific that keeps a message from reading as generic. Enrichment data, not a hook on its own.

Step 3 — Write the sequence

Read reference/sequence_patterns.md for structure by scenario. Defaults:

  • Cold outreach — 4 messages over 3 weeks

  • Warm or referral — 3 messages over 2 weeks

  • Post-meeting follow-up — 2 messages over 10 days

  • Re-engagement of a quiet customer — 3 messages over 4 weeks

Each message in a sequence must add something new. A follow-up whose entire content is "just bumping this" trains people to ignore the sender. Give every touch a fresh reason to exist: a different angle, a relevant result, a genuinely useful piece of information, or a clean close-out.

Length rule: first message under 120 words. Owners in this segment sell to people who read on their phone between jobs.

Step 4 — Self-check against the slop test

Before showing anything, run every draft against reference/slop_test.md. It catches the specific patterns that make copy read as machine-written.

The fastest checks:

  • Would the owner say this sentence out loud? If not, rewrite it.

  • Could this message be sent to any other company with two words changed? If yes, it is not personalized.

  • Does it open with a compliment about the prospect's business? Delete it — everyone does this and everyone recognizes it.

  • Is there a phrase here the owner has never used in their life? Cut it.

This step is not optional and it is not a formality. It is the difference between copy that gets sent and copy that gets rewritten by hand, which is the outcome the skill exists to prevent.

Step 5 — Present for approval

Show the full sequence before anything queues. Follow reference/output_template.md.

Present message one in full, then the rest of the sequence with subject lines and the angle each takes. Owners want to read the first one closely and skim the shape of the rest.

Deliver per the owner's stored output preference — never default to a markdown file. Check the ## Business context block's Output preference (shared style guide rule, ../../shared/artifact-style.md):

  • Visual artifact (the default): an HTML page in the house style — one card per prospect or sequence, each message as a copy block so any single message can be copied and sent by hand.

  • docx / md / notion / canva preference: deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.

  • Best for skill: use the visual artifact — the copy blocks are the point.

Chat keeps the recap and the approval question in every case.

Then ask what to change. Expect edits — the first pass is a proposal, not a delivery. Fold every edit back into the voice profile, because a correction made once should not have to be made again.

Step 6 — Queue sends, with approval, one gate at a time

Sending email under the owner's name is the highest-consequence action in this skill.

  • Never send without an explicit yes for that specific batch

  • State exactly what will happen before asking: how many messages, to whom, on what schedule, from which account

  • Never send to a contact marked "inferred" without flagging it separately. Bounces at volume damage the owner's sending domain for months, and that damage reaches their real customer mail

  • Approval for message one is not approval for the sequence. Confirm the follow-ups separately, or set them to draft and let the owner release each

Mailchimp is a drafting destination, not a send route. When it is connected, an approved sequence can be saved into Mailchimp as campaign content for the owner to schedule there. Three things govern that:

  • It cannot send. Nothing this skill puts into Mailchimp goes out on its own. The owner presses send in Mailchimp.

  • Its planner refuses single campaigns. Mailchimp's campaign planner only produces multi-channel plans — email plus SMS plus social. A one-off email is written here, in the owner's voice, and saved as content. Do not route a single message through the planner and do not report a refusal as a failure.

  • Do not assume you can read the audience list. Treat the contact list as unavailable unless a call actually returns it. Build the recipient list from the CRM or the owner's own file, as today.

Without a mail connector, run draft-only. Produce the copy formatted to paste anywhere. This is a complete outcome, not a degraded one — plenty of owners prefer to send from their own client anyway.

Step 7 — Log it

Log every touch to HubSpot when connected: what was sent, when, to whom, and where it sits in the sequence. Without a CRM, keep the record in a file so the next run knows who has already been contacted.

Contacting someone twice with the same opener is a visible, avoidable mistake.

What not to do

  • Do not write before learning the voice. Everything downstream depends on it.

  • Do not open with flattery about their business. It is the single clearest tell.

  • Do not send a follow-up that says only "checking in." Every touch earns its place.

  • Do not merge a company name into a template and call it personalized.

  • Do not send anything without an explicit approval for that batch.

  • Do not claim results the owner has not actually produced. Invented case studies in outreach are a serious problem, not an exaggeration.

After the send

The sequence is approved, queued or drafted, and every touch is logged. The natural next step is "update the CRM" — crm-autopilot keeps the next-step queue current as replies come in. Also nearby: "leads are going cold" (speed-to-lead) to catch the responses fast, and "find me customers" (lead-finder) when this list runs dry. Offer at most three, and skip any offer the owner already declined this session.

Reference files

  • ../../shared/voice-profile.md — the owner's voice, shared by every skill that writes in their name

  • reference/sequence_patterns.md — structure and cadence by scenario

  • reference/slop_test.md — the checklist that catches machine-written copy

  • reference/output_template.md — how sequences are presented for approval

  • reference/gotchas.md — the failure modes that get owners to stop using this

Using a tool that isn't listed

The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer build-connector — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.


  Syntax-file, code seperations,code vault integeted with css definition.
Pre-recordec, pre-tested, elements to capture elements into Packeted-User-Relations to capture - [

pre-requisites, statements, recorded-cams
, cams-data
, data, input()

]

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Declares allowed tools

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/knowledge-work-plugins · small-business/skills/outreach-composer · commit e050c2e
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download outreach-composer.zip