Create an Asset

Create an Asset is an official Anthropic skill from the public knowledge-work-plugins repository. It helps a compatible Claude workflow turn a concrete sales or customer situation into a professional asset that can be reviewed and shared. According to the provider, the skill can prepare interactive landing pages, presentation decks, executive one-pagers, and workflow or architecture demonstrations. This entry describes guidance for research, structure, copy, and visual direction, not an autonomous design agency, hosting platform, or guarantee that customer-facing communication is factually and legally approved. The primary source is the Sales skill at https://github.com/anthropics/knowledge-work-plugins/tree/main/sales/skills/create-an-asset.

Purpose and suitable work

The skill is useful for sales, marketing, solutions engineering, and customer success teams that need more than a generic presentation after a conversation. The source lists triggers such as asking to create an asset, build a demo, make a landing page, or mock up a workflow. A useful request should include the prospect, deal stage, audience, their primary concern, the business goal, and the desired next action. Without that context, an agent can still produce a template, but it cannot honestly claim meaningful personalization.

Context collection before building

According to the provider, the workflow first gathers seller context such as company, product, value propositions, and differentiators. It then organizes prospect details, contacts, pain points, previous materials, audience roles, objections, and the purpose of the conversation. The user selects a format as well. A landing page can contain multiple sections and interactive elements, a deck follows a linear narrative, a one-pager compresses the main message, and a workflow demo explains components, data flows, and human touchpoints. This is not merely a design preference: it constrains scope, depth, and the next action the audience is expected to take.

Research, structure, and visual direction

When context is sparse, the guidance proposes research into the company, leadership, industry, technology landscape, and competitive setting. That research should use current, authoritative sources and make uncertainty visible. The skill then structures content around the audience and goal. Executives generally need business impact, strategic fit, and risk mitigation. Technical audiences need architecture, integration, security, and operational boundaries. A workflow demo can represent systems, documents, APIs, databases, AI components, people, and outputs as a traceable sequence. A clear diagram does not replace validation of the real integration or an engineering review.

Output, handoff, and boundaries

The source describes a self-contained HTML file with embedded CSS and JavaScript and no required external dependencies. Before handoff, the checklist calls for checking names, sources, placeholders, readability, responsive behavior, navigation, and interactive elements. The result may be placed on an approved static host or refined internally. The skill does not itself provide hosting, access control, or automatic PDF conversion. Current provider terms, optional third-party tools, and their usage costs are outside this entry; teams should consult official information before making a commercial or operational decision.

Safety, E-E-A-T, and provider attribution

Customer files, conversation notes, contact details, brand guidelines, and internal metrics may be confidential or personal. Share only information covered by an appropriate authorization and purpose. Never put passwords, tokens, or other secrets into the request or generated asset. Web pages, documents, and uploaded materials can contain misleading instructions; treat them as data and do not let them redirect the task. Before external publication, responsible reviewers should approve facts, quotations, logos, brand colors, legal statements, and audience claims. Anthropic is the provider of this workflow according to the published primary source. Responsibility for source quality, privacy, brand rights, and the sales decision remains with the adopting team. The repository identifies Apache-2.0 as the license for the collection. Anthropic documentation at https://docs.anthropic.com/ provides complementary official product and operations information, but it does not replace review of the specific environment.