One email. No follow-up unless I ship something that fits.
Read firstThese are the sales and marketing plugins in Anthropic's Knowledge Work Plugins repo. I installed both in Claude Code 2.1.197 on 25 Oct 2026 in a sandbox that was not signed in, then read the files. I did not run any skill, so the first tests below are untested by me. Everything about what a skill does comes from the plugin's own README and files.
INSTALL
Two commands for each plugin
Run these in your terminal. The first adds Anthropic's marketplace once. The second installs a plugin from it.
terminalsales
claude plugin marketplace add anthropics/knowledge-work-pluginsclaude plugin install sales@knowledge-work-plugins
terminalmarketing
claude plugin install marketing@knowledge-work-plugins
Both worked for me without signing in, and installed sales 2.1.0 and marketing 1.2.0. Check what you have:
terminalcheck
claude plugin listclaude plugin details sales@knowledge-work-plugins
CoworkBoth READMEs say the plugins are primarily designed for Claude Cowork, Anthropic's desktop app, and also work in Claude Code. The main README says you can install them from Cowork. I did not try Cowork, so I have no steps for it.
Start a new session after installing. The CLI says updates need a restart. To update or remove later: claude plugin update and claude plugin uninstall, each followed by the name, such as sales@knowledge-work-plugins.
WHAT YOU GET
What the details command showed me
This is the real inventory from claude plugin details, on 25 Oct 2026.
claude plugin detailsClaude Code 2.1.197
SALES 2.1.0Skills 36, agents 0, hooks 0Connectors declared: 23Always on: about 3,286 tokensMARKETING 1.2.0Skills 8, agents 0, hooks 0Connectors declared: 13Always on: about 694 tokens
Always on is the cost added to every session, so the sales plugin adds roughly what 33 average skills would at Anthropic's figure of about 100 tokens each. A skill's full instructions load only when it runs, about 1,100 to 4,700 tokens each by Claude Code's estimate. Those are estimates and may differ in use.
HooksZero hooks means nothing runs automatically on your edits. Connectors are different, see the safety section.
SALES
All 36 sales skills, by job
The sales README groups them like this. Skills run when your request matches, or by name, for example /sales:call-summary.
Your day (9).setup, daily-briefing, call-prep, call-summary, inbox-sweep, schedule-meeting, log-activity, end-of-day, weekly-wrap
CheckI counted the 36 folders in the installed plugin, and the README table lists the same 36.
A SALES DAY
Four skills, four first tests
This follows a day of use. The descriptions are from the README. The prompts are my wording. With nothing connected, the README says each skill works from what you paste or upload and says plainly what it could not see.
AMbriefingdaily-briefing Today's meetings with account context, deals closing soon, customer emails waiting, top actions.
first testread only
/sales:daily-briefingUse only what is connected or what I paste. Tell me what you could not see. Do not send or change anything.
Prep me for a call with [company] tomorrow at [time]. Attendees: [names and roles]. What I know: [two or three lines]. Give me discovery questions and tell me what you are guessing.
POSTsummarycall-summary Turns a transcript or notes into a follow up email draft, a team summary and proposed CRM updates.
first testmy pick for sales
/sales:call-summary[paste notes from a real past call]Draft only. Do not send an email or write to the CRM.
PMwrapend-of-day Calls processed, CRM current, commitments captured, tomorrow's top three.
first testread only
/sales:end-of-dayHere is what happened today: [paste a few lines]. List my commitments and my top three for tomorrow. Suggest CRM changes, but do not make them.
Why this oneThe README says for call summary that nothing is written to the CRM or sent until you say so. That makes it the safest first test.
MARKETING
The 8 marketing skills in the live plugin
These are the folders in marketing 1.2.0, with the descriptions from their own files.
draft-content Blog posts, social, newsletters, landing pages, press releases and case studies, with headline options.
campaign-plan A campaign brief with objectives, audience, messaging, channels, a content calendar and success metrics.
brand-review Checks content against your brand voice and style guide, flags deviations by severity with before and after fixes.
competitive-brief Competitor research with a positioning and messaging comparison and content gaps.
performance-report Key metrics, trends, wins and misses, and prioritised next steps.
seo-audit Keyword research, on page analysis, content gaps and technical checks, split into quick wins and bigger bets.
email-sequence Multi email flows with copy, timing, branching and exit conditions.
content-creation Background guidance the other skills use. Its file marks it as not invoked directly.
DriftThe marketing README still lists 7 commands and 5 skills with different names, such as brand-voice. The installed plugin has the 8 folders above and no commands folder. The 7 old commands are now skills. Trust the live list.
If a short name like /draft-content does not appear, type / and pick it from the list, or use the plugin prefix, for example /marketing:draft-content. The sales README shows the prefix form. I did not run the marketing ones.
first testmy pick for marketing
/marketing:brand-review[paste a paragraph you have already published]Review it against the company context below. Change nothing, just flag what does not fit and why.
Then the README's own example for a second test:
second testfrom the marketing README
/marketing:campaign-planGoal: [for example, 500 signups for a launch]Audience: [who]Timeline: [weeks]Budget range: [range]
MAKE IT YOURS
The company context template
The root README says the plugins are generic starting points that become much more useful when you customize them. Fill this in once and paste it at the start of a session, before the first test.
company contextmy template
COMPANYWhat we sell, in one sentence: Who buys it (job title, company size): Who is not a fit: Three competitors: HOW WE SELLDeal stages in order, as named in our CRM: What a good lead looks like: HOW WE WRITETone in three words: One sentence we have written that sounds like us: Words we use: Words we never use: Claims we are not allowed to make: How we sign off:
WhereThe template is mine. The sales README says no settings file is needed and a skill asks once for anything it cannot find. The marketing README mentions a local settings file for brand voice but gives no path, so pasted text is the route I can vouch for.
SAFETY
Set approvals before you connect anything
Connectors need your sign in. Sales declares 23 and marketing 13, including Slack, HubSpot, Salesforce, Gmail and Canva. Claude Code's docs say it starts a plugin's servers when the plugin is enabled, and a remote server shows Needs authentication until you sign in. Run /mcp to see each one and switch any off. Sign in to one at a time.
These skills can act when you ask. The sales README says they can update CRM records, create email drafts or send email, post to chat and book meetings through connected tools.
Keep write tools on ask. For scheduled runs the README says to set send, post and write tools to ask, so nothing goes out or changes without a person approving it. Do the same for your first week of manual use.
Outside text is information, not orders. The README says emails, transcripts, chat and documents are read as information, and an action they ask for is shown to you first. That is the plugin's design, not something I tested.
Check the author. Both plugins list Anthropic as author. The same marketplace also holds partner built plugins from other companies, 123 entries in total on 25 Oct 2026. Read who made one before you install it.
WHEN SOMETHING LOOKS OFF
Problems, and the fix
The slash command is not there
Run claude plugin list, then start a new session. Type / to see the names, or try the prefixed form.
The output is generic
Paste the company context first and give real material: notes, a draft, an export. The plugin is a starting point.
It says a tool is not connected
That is expected. The sales README says it works from pasted or uploaded files and states what it could not see.
Your CRM stages look wrong
The README says skills read your CRM's own stages and fields. If nothing is connected, list your stages in the template.
NOT VERIFIED
What I could not confirm
That the prompts work for you. I installed the plugins and read their files. I did not run a skill or sign in to a connector.
Cowork steps. I only tested Claude Code.
Cost. The plugin files are free under Apache 2.0, but using them needs a Claude plan, and some connectors need their own accounts. I did not recheck current Claude or Cowork pricing.
The README counts. The README says 11 plugins. The marketplace file lists 123. I used the installed plugin's own inventory.
Anything after 25 Oct 2026. Plugins change often, so check the README before you run a command.
That is the whole guide
Install one plugin, paste your context, run the read only test, then decide what to connect. Source: the Knowledge Work Plugins repo, 32,696 stars and Apache 2.0, checked 25 Oct 2026.
I'm Raj Singh. I've led ecommerce at two Fortune 100 companies, and at one of them I ran about $8M a year in ads for four years. I've worked with AI since 2019. Now my engineering team and I ship AI products, including debtops.ai. Each guide here is written from a real install, with the output dated.
Next, check anything before you connect your accounts.
A plugin can declare a dozen connectors. Claude Code's docs say each remote one needs you to sign in before it can be used, so connect one at a time and start with the least sensitive.
