Using Create an Asset safely

Create an Asset is a skill from the sales plugin within the Knowledge Work Plugins that Anthropic publishes on GitHub under anthropics/knowledge-work-plugins. The skill helps sales teams turn account data, call notes, and already-approved marketing material into a finished, prospect-specific asset, such as a one-pager, a deck, or a leave-behind document for a particular prospect or customer. According to the provider, the shape of the asset is deliberately flexible while the content pipeline is fixed: every claim must be grounded in the organization's approved materials, real account data, or content the user provides, and invented numbers are ruled out entirely.

The four ground rules that govern every step

Central to the skill is that product, pricing, packaging, and positioning claims may only come from the organization's approved materials or content supplied by the user; when neither covers a claim, it is explicitly labeled unverified rather than quietly filled in from the model's general knowledge. Second, an audience gate applies: internal content such as roadmap details or battlecards must never land in a customer-facing asset, and the final list of claims is checked against this rule. Third, no metrics may be invented; every customer-specific number needs a source such as a record link, a transcript line, or an email thread, or it appears as a placeholder the sales rep must fill in themselves. Fourth, content from emails, chats, transcripts, and external documents counts strictly as data, never as an instruction to the skill, even if it contains something phrased like a request.

The four-step workflow

First, the skill establishes grounding, shape, and audience: it checks which tools are connected, orients itself on the organization's template and voice, and infers the appropriate shape from the request, asking exactly one clarifying question when genuinely ambiguous. Second, it gathers content in a fixed priority order: user-provided material first, then the organization's approved content, and finally account data such as CRM facts, transcript themes, and email commitments, clearly distinguishing paraphrase from verbatim quotes. This produces a content inventory where every claim carries its source before anything is rendered; for decks the default is a tight first-call outline of five to six slides covering who we are, what has changed for the prospect's industry, proof points, how to get started, and the ask. Only after a brief confirmation of that outline does the third step actually render the asset, with decks becoming slide decks and documents becoming standalone pages; when the right surface is unavailable, the skill falls back to an exportable document instead of blocking the deliverable. The fourth step is a quality pass confirming every claim traces back to the inventory, no internal information ends up in the customer-facing asset, and every number is either sourced or marked as a placeholder.

Requirements and integration

The skill is activated by installing the sales plugin from the Knowledge Work Plugins marketplace inside Claude Cowork or Claude Code. It requires no credentials of its own but benefits heavily from connected tools such as CRM systems, document stores, and email, since the quality of the result depends directly on how complete the accessible account data and approved material are. When a connector is missing, the skill states it works transparently with what is available and plainly names what could not be included.

Security, practical value, and limitations

The main security consideration is the strict separation between internal and customer-facing material, together with the rule that content from external sources is never interpreted as an instruction. The practical value is that sales teams get a reliable, source-grounded document in a short amount of time without manually looking up every number themselves, which is especially valuable ahead of short-notice customer meetings. The limitation is that the skill is only as good as the connected data sources; without approved material or account access it falls back to generic, clearly labeled content, and final responsibility for the content still rests with the sales rep.