The real customer-support plugin, and what could (and couldn't) be verified
Anthropic's knowledge-work-plugins repository is real, public, Apache-2.0 licensed, and (at time of writing) has 16.2k stars. Its README describes customer-support as one of 11 plugins in the marketplace, with this exact one-line description: "Triage tickets, draft responses, package escalations, research customer context, and turn resolved issues into knowledge base articles."
Connectors (verbatim from the plugin table)
Slack, Intercom, HubSpot, Guru, Jira, Notion, Microsoft 365.
The workflow model plugins share
The README describes every plugin, including customer-support, as following the same structure:
| Path | Role |
|---|---|
.claude-plugin/plugin.json | Manifest |
.mcp.json | Tool connections -- wires Claude to external tools (CRMs, project trackers, data warehouses, design tools) via MCP servers |
commands/ | Slash commands you invoke explicitly (e.g. the README's own examples /sales:call-prep, /data:write-query -- a customer-support-specific command would follow the same /customer-support:<name> shape) |
skills/ | Domain knowledge Claude draws on automatically when relevant |
Honest limitation
The customer-support plugin's own subdirectory tree (github.com/anthropics/knowledge-work-plugins/tree/main/customer-support) was fetched during this site's research, but GitHub's directory listing for a subfolder renders via client-side JavaScript that a plain HTML/text fetch cannot execute -- so the actual filenames of customer-support's own skills or commands (e.g. what a hypothetical skills/ticket-triage/SKILL.md might be called) could not be confirmed and are deliberately not invented or guessed anywhere on this site.
Source: github.com/anthropics/knowledge-work-plugins, fetched live 2026-07-02.