Claude Skills for Marketing and Sales: Call Recaps Before Emails

Build your first Claude skill around a task your team repeats every week, like call recaps, because a colleague can check what it writes.

HubSpot’s guide calls Claude skills “reusable instruction sets for tasks such as campaign planning, sales call recaps, persona research, content outlining.” It adds proposal drafting and performance reporting to that list. Reuse is also the flaw: a vague instruction gets reused as readily as a good one, so one weak line ends up in every output the skill writes until someone catches it.

So build a sales call recap skill first, and test it on past calls before anyone relies on it. Build email-drafting skills last, because the Gmail rules that affect delivery sit in your sending setup, not in the draft. If nothing on your team happens weekly, skip skills for now and keep a shared prompt doc.

How we evaluated

Criteria: how often the task comes back, who reads the output first, and which outside rules the output has to meet. Sources: HubSpot’s guide to Claude skills, Gmail’s email sender guidelines, and two Google Search Central pages (the helpful-content guidance and the SEO Starter Guide). Each is linked where it’s used.

What a Claude skill is: a reusable set of instructions you write once

HubSpot puts the difference this way: “A prompt usually guides a single interaction, while a skill preserves a process that Claude can apply across similar requests.” It says good skills “turn recurring work into reusable processes with defined instructions, inputs, and outputs” (source). That gives three core parts:

1. Instructions: the steps and rules, in the order a new hire would need them.
2. Inputs: what you hand over on each run, such as a transcript, a CSV export or a brief.
3. Outputs: the shape of the result, such as headings, length and fields.

HubSpot’s fuller list also includes the skill’s purpose, reference material such as templates and brand guidance, and review requirements, meaning the parts of the output that need checking before they go out.

A prompt retyped from memory has no fixed version. When the result goes wrong, there’s no single instruction to fix.

Six recurring marketing and sales tasks that suit skills: build recap and report skills first

The six tasks are the examples HubSpot gives. The build order is our recommendation. It ranks each task by who reads the output first, so a mistake reaches a teammate before it reaches a customer.

Build order	Task (HubSpot example)	Who reads the output first	Rule to write into the skill
1	Sales call recaps	Your sales reps	Summarize only what the transcript or notes contain
2	Performance reporting	Your team and manager	Make the data export a required input
3	Persona research	Your marketing team	Label each claim with where it came from
4	Campaign planning	Your team, then customers once it runs	A person signs off before anything is scheduled
5	Content outlining	Writers, then searchers	Name the reader (see the content section)
6	Proposal drafting	A prospect	A rep checks every price and promise before sending

Email drafting isn’t one of HubSpot’s six examples. If you build an email skill, it goes after all of these.

How to set up a skill: write instructions, inputs and outputs before the first run

Take the recap skill and write it as three blocks.

• Instructions: “Summarize this call for the account owner. List decisions, objections, and next steps with owners and dates. Add nothing the transcript does not say.”
• Inputs: the call transcript, the account name, the deal stage.
• Outputs: three headings matching the instructions: Decisions, Objections, Next steps (suggested). Write next steps as a checklist. Length cap: under 200 words (suggested).

Then run it on a few past calls you already have notes for. Wherever the skill’s recap differs from the rep’s, change the instruction, not just that one output. HubSpot’s guide keeps “strategy, factual validation, and business decisions” under human control. Name one owner who approves edits, so the instructions don’t drift as more people touch them.

Email-drafting skills: Gmail’s rules sit in your sending platform, not in the skill

Gmail’s email sender guidelines cover mail sent to personal Gmail accounts, meaning addresses ending in @gmail.com or @googlemail.com. Three of its rules matter for any email skill:

1. Alignment. Under its requirements for senders of more than 5,000 messages a day, Gmail says: “For direct email, the domain in the sender’s From: header must be aligned with either the SPF domain or the DKIM domain. This is required to pass DMARC alignment.” Ask whoever set up your sending domain which SPF and DKIM domains it uses.
2. Format. “Format messages according to the Internet Message Format standard, RFC 5322.”
3. Spam rate. “Keep spam rates reported in Postmaster Tools below 0.30%.” That works out to fewer than 3 spam reports per 1,000 messages that Postmaster Tools counts.

The first two are settings where the mail is sent from, not wording in the copy, so leave them out of the skill. Write the skill to output a subject line, preview text and body copy only, ready to paste into your platform’s editor. For the sending setup itself, see MarketingRating’s email-platform guides.

The spam rate comes from how recipients react to your sends, so a person has to watch it. Name the person who checks the Postmaster Tools rate after each send, and write that name into the skill’s instructions as the approver.

Rules to build into content and SEO skills: name the reader and drop any ranking goal

Google’s helpful-content guidance says SEO “can be a helpful activity when it is applied to people-first content, rather than search engine-first content.” Its SEO Starter Guide adds: “There are no secrets here that’ll automatically rank your site first in Google (sorry!).”

Two rules follow for an outlining skill:

1. Make the reader a required input. Write the skill to ask who the piece is for, and what question that person is asking, before it outlines anything.
2. Leave ranking out of the instructions and the output. No “rank #1 for X” goal, and no promised position in the brief the skill hands to a writer. Google’s own guide says it has no secret that ranks a site first, so a brief that promises a position is promising something the writer can’t control.

Checklist to run before a team relies on a skill

Seven checks, in order. The first two draw on HubSpot’s guide, and the last four apply the Gmail and Google rules above.

1. The task comes back regularly and matches one of HubSpot’s examples or something close.
2. The instructions, inputs and outputs are each written down, as HubSpot recommends.
3. The skill has run on past examples, and every gap against a person’s version was fixed in the instructions.
4. Email skills output copy only. Someone has also confirmed in the sending platform that, for direct email, the From: domain is aligned with the SPF or DKIM domain (Gmail).
5. For email skills, RFC 5322 formatting is left to the platform, and a named person watches the Postmaster Tools spam rate against the 0.30% line (Gmail).
6. Content skills require a named reader and question as inputs (Google).
7. Content skills carry no ranking target or promise (Google’s SEO Starter Guide), and the skill’s owner and next review date are written at the top of its instructions.

Before you budget: confirm plan, seat price and data access

Do these four things before you commit time:

• Confirm your Claude plan includes skills. Write down the current per-seat price and the date you checked it, so the cost sits next to the time saved.
• List the data each skill needs, such as call transcripts, CRM exports or analytics. Decide whether it gets connected to Claude or who pastes it in on each run.
• Find out who can open Postmaster Tools for your sending domain before anyone builds an email skill.
• Count the hours. Writing a skill and running it on past examples takes someone’s time. Compare that with how often the task comes back.

FAQ

Can one skill handle both recaps and proposals? Split them. A recap goes to your team, but a proposal goes to a prospect and needs a rep’s check, so the two need different rules.

When should a skill be re-checked? Re-check it whenever its inputs change, such as a new call-recording tool or a new report export. Re-check email skills when Gmail’s sender guidelines page changes. The page keeps a table of updates to its requirements, with the date each was added.

Does a skill replace our style guide? No. HubSpot lists brand guidance as reference material a skill can use, so attach the style guide to the skill instead of copying its rules into the instructions. When the guide changes, update the attached copy.