[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-smb-onboard":3,"mdc-qmokt0-key":37,"related-repo-anthropic-smb-onboard":401,"related-org-anthropic-smb-onboard":520},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"smb-onboard","onboard SMB owners to tool integrations","Claude as the trainer. Walks an SMB owner through connecting their first two tools, runs one recipe to prove immediate value, interviews them about their business (industry, size, top three headaches), stores that context persistently so every other skill benefits, and sets a weekly check-in cadence. Use when the owner is getting started or says any of: \"set me up,\" \"setup,\" \"help me get set up,\" \"get started,\" \"help me get started,\" \"get me started,\" \"what can you do,\" \"I'm new to this,\" or is in their first session.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"anthropic","Anthropic","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fanthropic.png","anthropics",[13,17,20,23],{"name":14,"slug":15,"type":16},"Operations","operations","tag",{"name":18,"slug":19,"type":16},"Productivity","productivity",{"name":21,"slug":22,"type":16},"Integrations","integrations",{"name":24,"slug":25,"type":16},"Coaching","coaching",22885,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","2026-05-14T06:02:51.824437",null,2736,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"Open source repository of plugins primarily intended for knowledge workers to use in Claude Cowork","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Ftree\u002FHEAD\u002Fsmall-business\u002Fskills\u002Fsmb-onboard","---\nname: smb-onboard\ndescription: >\n  Claude as the trainer. Walks an SMB owner through connecting their first two\n  tools, runs one recipe to prove immediate value, interviews them about their\n  business (industry, size, top three headaches), stores that context\n  persistently so every other skill benefits, and sets a weekly check-in\n  cadence. Use when the owner is getting started or says any of: \"set me up,\"\n  \"setup,\" \"help me get set up,\" \"get started,\" \"help me get started,\" \"get me\n  started,\" \"what can you do,\" \"I'm new to this,\" or is in their first session.\n---\n\n# SMB Onboard\n\n## Quick start\n\nFour moves: connect two tools → run one recipe → capture business context → set a weekly rhythm. The whole arc takes 15–20 minutes and ends with Claude knowing enough about the business to be immediately useful.\n\n```\nUser: \"get me started\"\n→ Assess what's already connected; pick the best 2 tools to connect first\n→ Guide connection of each tool (one at a time)\n→ Run one recipe against live data to prove value\n→ Ask 5 business questions one at a time; store answers to persistent memory\n→ \"Each Monday, say 'weekly check-in' — I'll pull your numbers and flag anything urgent.\"\n```\n\n## Tone for connectors\n\nWhenever a connector comes up — recommending one, naming what to try next, or clarifying mid-flow — describe **what Claude will be able to do once it's connected**, not what the platform itself is or sells. Owners already know what HubSpot, QuickBooks, Gmail, and Calendar do; they don't need a product pitch from us.\n\n- Speak about capabilities we unlock (\"draft follow-ups after every meeting\", \"pull your cash position anytime\"), never feature lists.\n- One short sentence per connector, max — unless the owner explicitly asks for more (\"what does HubSpot actually do?\"), in which case answer that directly.\n- This rule applies to every step below.\n\n## Workflow\n\n1. **Welcome and assess.** Greet the owner briefly. Check which connectors are already active. If a `## Business context` block already exists in the owner's CLAUDE.md or memory, read it first — then skip to the return-session path: show the existing profile, ask what's changed, update only the fields that changed. Do not re-interview from scratch.\n\n2. **Pick two functions, then check what the owner uses.** Ask: *\"What are your biggest day-to-day headaches — money, customers, scheduling, or getting organized?\"* Map the answer to the connector priority list in [reference\u002Fonboard-checklist.md](reference\u002Fonboard-checklist.md).\n\n   Name the two **functions** we want (e.g. \"a place to track customers and deals\" and \"your inbox\") — not the platform features. One short sentence each, max. Then ask whether the owner uses a supported tool for each.\n\n   For each function, branch:\n   - **Owner uses a supported connector** (e.g. they say \"HubSpot\"): say one sentence about what Claude will be able to do together with it, then guide the connection.\n   - **Owner uses an unsupported tool or nothing yet**: list 2–3 concrete things Claude will be able to do *with* the supported alternative, and 1–2 things that won't work without it. Then let the owner decide whether to switch or add it. Do not push.\n\n   Connect one tool at a time — never ask the owner to configure two simultaneously. See [reference\u002Fgotchas.md](reference\u002Fgotchas.md) for the failure pattern this replaces.\n\n3. **Run one recipe to prove value.** Once the first tool connects — or if connectors are already active when the session starts — immediately run the matched recipe for the owner's primary headache (see connector-to-recipe table in [reference\u002Fonboard-checklist.md](reference\u002Fonboard-checklist.md)). Narrate what Claude is doing and why — this is the \"aha\" moment. Do not skip it to get to the interview faster. For a worked example of the full arc, see [reference\u002Fexamples\u002Fhappy-path.md](reference\u002Fexamples\u002Fhappy-path.md).\n\n4. **Interview the owner.** Ask the five questions from [reference\u002Fonboard-checklist.md](reference\u002Fonboard-checklist.md), one at a time, conversationally. Wait for the full answer before moving to the next. If the owner seems pressed for time, compress to three: industry, headaches, tools — but never fewer.\n\n5. **Store context.** Show the owner the full profile before writing. Wait for explicit approval. Write the block to the Cowork session memory directory under the heading `## Business context` using the exact format in [reference\u002Fonboard-checklist.md](reference\u002Fonboard-checklist.md). If a memory file already exists, update only the `## Business context` section — do not touch other content. Confirm: *\"Saved. Every skill from here will know your business.\"*\n\n6. **Set the weekly cadence.** Propose: *\"Each Monday, just say 'weekly check-in' and I'll pull a snapshot of your numbers, flag anything urgent, and remind you what's due.\"* If they prefer a different phrase or day, store it in the profile. If tools are connected, name one skill the owner can try right now. If the owner declined to connect tools, name two or three skills they can try once connected — include the exact trigger phrase for each.\n\n## Approval gates\n\n- **Show context before writing.** Display the full owner profile draft before storing it. Wait for explicit approval.\n- **Never overwrite existing context silently.** If a `## Business context` block already exists, show current vs. proposed before writing any changes.\n- **Never connect a tool on the owner's behalf.** Guide; do not act. Connector auth is always owner-initiated.\n\n## Reference\n\n- [reference\u002Fonboard-checklist.md](reference\u002Fonboard-checklist.md) — interview questions, connector priority matrix, recipe selection, context storage format\n- [reference\u002Fgotchas.md](reference\u002Fgotchas.md) — Good \u002F Bad patterns for pacing, tool selection, and context storage\n- [reference\u002Fexamples\u002Fhappy-path.md](reference\u002Fexamples\u002Fhappy-path.md) — worked example: retail shop owner, first session end-to-end\n",{"data":38,"body":39},{"name":4,"description":6},{"type":40,"children":41},"root",[42,50,57,63,76,82,95,115,121,319,325,365,371],{"type":43,"tag":44,"props":45,"children":46},"element","h1",{"id":4},[47],{"type":48,"value":49},"text","SMB Onboard",{"type":43,"tag":51,"props":52,"children":54},"h2",{"id":53},"quick-start",[55],{"type":48,"value":56},"Quick start",{"type":43,"tag":58,"props":59,"children":60},"p",{},[61],{"type":48,"value":62},"Four moves: connect two tools → run one recipe → capture business context → set a weekly rhythm. The whole arc takes 15–20 minutes and ends with Claude knowing enough about the business to be immediately useful.",{"type":43,"tag":64,"props":65,"children":69},"pre",{"className":66,"code":68,"language":48},[67],"language-text","User: \"get me started\"\n→ Assess what's already connected; pick the best 2 tools to connect first\n→ Guide connection of each tool (one at a time)\n→ Run one recipe against live data to prove value\n→ Ask 5 business questions one at a time; store answers to persistent memory\n→ \"Each Monday, say 'weekly check-in' — I'll pull your numbers and flag anything urgent.\"\n",[70],{"type":43,"tag":71,"props":72,"children":74},"code",{"__ignoreMap":73},"",[75],{"type":48,"value":68},{"type":43,"tag":51,"props":77,"children":79},{"id":78},"tone-for-connectors",[80],{"type":48,"value":81},"Tone for connectors",{"type":43,"tag":58,"props":83,"children":84},{},[85,87,93],{"type":48,"value":86},"Whenever a connector comes up — recommending one, naming what to try next, or clarifying mid-flow — describe ",{"type":43,"tag":88,"props":89,"children":90},"strong",{},[91],{"type":48,"value":92},"what Claude will be able to do once it's connected",{"type":48,"value":94},", not what the platform itself is or sells. Owners already know what HubSpot, QuickBooks, Gmail, and Calendar do; they don't need a product pitch from us.",{"type":43,"tag":96,"props":97,"children":98},"ul",{},[99,105,110],{"type":43,"tag":100,"props":101,"children":102},"li",{},[103],{"type":48,"value":104},"Speak about capabilities we unlock (\"draft follow-ups after every meeting\", \"pull your cash position anytime\"), never feature lists.",{"type":43,"tag":100,"props":106,"children":107},{},[108],{"type":48,"value":109},"One short sentence per connector, max — unless the owner explicitly asks for more (\"what does HubSpot actually do?\"), in which case answer that directly.",{"type":43,"tag":100,"props":111,"children":112},{},[113],{"type":48,"value":114},"This rule applies to every step below.",{"type":43,"tag":51,"props":116,"children":118},{"id":117},"workflow",[119],{"type":48,"value":120},"Workflow",{"type":43,"tag":122,"props":123,"children":124},"ol",{},[125,143,229,251,267,302],{"type":43,"tag":100,"props":126,"children":127},{},[128,133,135,141],{"type":43,"tag":88,"props":129,"children":130},{},[131],{"type":48,"value":132},"Welcome and assess.",{"type":48,"value":134}," Greet the owner briefly. Check which connectors are already active. If a ",{"type":43,"tag":71,"props":136,"children":138},{"className":137},[],[139],{"type":48,"value":140},"## Business context",{"type":48,"value":142}," block already exists in the owner's CLAUDE.md or memory, read it first — then skip to the return-session path: show the existing profile, ask what's changed, update only the fields that changed. Do not re-interview from scratch.",{"type":43,"tag":100,"props":144,"children":145},{},[146,151,153,159,161,167,169,173,175,180,182,185,187,217,220,222,227],{"type":43,"tag":88,"props":147,"children":148},{},[149],{"type":48,"value":150},"Pick two functions, then check what the owner uses.",{"type":48,"value":152}," Ask: ",{"type":43,"tag":154,"props":155,"children":156},"em",{},[157],{"type":48,"value":158},"\"What are your biggest day-to-day headaches — money, customers, scheduling, or getting organized?\"",{"type":48,"value":160}," Map the answer to the connector priority list in ",{"type":43,"tag":162,"props":163,"children":165},"a",{"href":164},"reference\u002Fonboard-checklist.md",[166],{"type":48,"value":164},{"type":48,"value":168},".",{"type":43,"tag":170,"props":171,"children":172},"br",{},[],{"type":48,"value":174},"Name the two ",{"type":43,"tag":88,"props":176,"children":177},{},[178],{"type":48,"value":179},"functions",{"type":48,"value":181}," we want (e.g. \"a place to track customers and deals\" and \"your inbox\") — not the platform features. One short sentence each, max. Then ask whether the owner uses a supported tool for each.",{"type":43,"tag":170,"props":183,"children":184},{},[],{"type":48,"value":186},"For each function, branch:",{"type":43,"tag":96,"props":188,"children":189},{},[190,200],{"type":43,"tag":100,"props":191,"children":192},{},[193,198],{"type":43,"tag":88,"props":194,"children":195},{},[196],{"type":48,"value":197},"Owner uses a supported connector",{"type":48,"value":199}," (e.g. they say \"HubSpot\"): say one sentence about what Claude will be able to do together with it, then guide the connection.",{"type":43,"tag":100,"props":201,"children":202},{},[203,208,210,215],{"type":43,"tag":88,"props":204,"children":205},{},[206],{"type":48,"value":207},"Owner uses an unsupported tool or nothing yet",{"type":48,"value":209},": list 2–3 concrete things Claude will be able to do ",{"type":43,"tag":154,"props":211,"children":212},{},[213],{"type":48,"value":214},"with",{"type":48,"value":216}," the supported alternative, and 1–2 things that won't work without it. Then let the owner decide whether to switch or add it. Do not push.",{"type":43,"tag":170,"props":218,"children":219},{},[],{"type":48,"value":221},"Connect one tool at a time — never ask the owner to configure two simultaneously. See ",{"type":43,"tag":162,"props":223,"children":225},{"href":224},"reference\u002Fgotchas.md",[226],{"type":48,"value":224},{"type":48,"value":228}," for the failure pattern this replaces.",{"type":43,"tag":100,"props":230,"children":231},{},[232,237,239,243,245,250],{"type":43,"tag":88,"props":233,"children":234},{},[235],{"type":48,"value":236},"Run one recipe to prove value.",{"type":48,"value":238}," Once the first tool connects — or if connectors are already active when the session starts — immediately run the matched recipe for the owner's primary headache (see connector-to-recipe table in ",{"type":43,"tag":162,"props":240,"children":241},{"href":164},[242],{"type":48,"value":164},{"type":48,"value":244},"). Narrate what Claude is doing and why — this is the \"aha\" moment. Do not skip it to get to the interview faster. For a worked example of the full arc, see ",{"type":43,"tag":162,"props":246,"children":248},{"href":247},"reference\u002Fexamples\u002Fhappy-path.md",[249],{"type":48,"value":247},{"type":48,"value":168},{"type":43,"tag":100,"props":252,"children":253},{},[254,259,261,265],{"type":43,"tag":88,"props":255,"children":256},{},[257],{"type":48,"value":258},"Interview the owner.",{"type":48,"value":260}," Ask the five questions from ",{"type":43,"tag":162,"props":262,"children":263},{"href":164},[264],{"type":48,"value":164},{"type":48,"value":266},", one at a time, conversationally. Wait for the full answer before moving to the next. If the owner seems pressed for time, compress to three: industry, headaches, tools — but never fewer.",{"type":43,"tag":100,"props":268,"children":269},{},[270,275,277,282,284,288,290,295,297],{"type":43,"tag":88,"props":271,"children":272},{},[273],{"type":48,"value":274},"Store context.",{"type":48,"value":276}," Show the owner the full profile before writing. Wait for explicit approval. Write the block to the Cowork session memory directory under the heading ",{"type":43,"tag":71,"props":278,"children":280},{"className":279},[],[281],{"type":48,"value":140},{"type":48,"value":283}," using the exact format in ",{"type":43,"tag":162,"props":285,"children":286},{"href":164},[287],{"type":48,"value":164},{"type":48,"value":289},". If a memory file already exists, update only the ",{"type":43,"tag":71,"props":291,"children":293},{"className":292},[],[294],{"type":48,"value":140},{"type":48,"value":296}," section — do not touch other content. Confirm: ",{"type":43,"tag":154,"props":298,"children":299},{},[300],{"type":48,"value":301},"\"Saved. Every skill from here will know your business.\"",{"type":43,"tag":100,"props":303,"children":304},{},[305,310,312,317],{"type":43,"tag":88,"props":306,"children":307},{},[308],{"type":48,"value":309},"Set the weekly cadence.",{"type":48,"value":311}," Propose: ",{"type":43,"tag":154,"props":313,"children":314},{},[315],{"type":48,"value":316},"\"Each Monday, just say 'weekly check-in' and I'll pull a snapshot of your numbers, flag anything urgent, and remind you what's due.\"",{"type":48,"value":318}," If they prefer a different phrase or day, store it in the profile. If tools are connected, name one skill the owner can try right now. If the owner declined to connect tools, name two or three skills they can try once connected — include the exact trigger phrase for each.",{"type":43,"tag":51,"props":320,"children":322},{"id":321},"approval-gates",[323],{"type":48,"value":324},"Approval gates",{"type":43,"tag":96,"props":326,"children":327},{},[328,338,355],{"type":43,"tag":100,"props":329,"children":330},{},[331,336],{"type":43,"tag":88,"props":332,"children":333},{},[334],{"type":48,"value":335},"Show context before writing.",{"type":48,"value":337}," Display the full owner profile draft before storing it. Wait for explicit approval.",{"type":43,"tag":100,"props":339,"children":340},{},[341,346,348,353],{"type":43,"tag":88,"props":342,"children":343},{},[344],{"type":48,"value":345},"Never overwrite existing context silently.",{"type":48,"value":347}," If a ",{"type":43,"tag":71,"props":349,"children":351},{"className":350},[],[352],{"type":48,"value":140},{"type":48,"value":354}," block already exists, show current vs. proposed before writing any changes.",{"type":43,"tag":100,"props":356,"children":357},{},[358,363],{"type":43,"tag":88,"props":359,"children":360},{},[361],{"type":48,"value":362},"Never connect a tool on the owner's behalf.",{"type":48,"value":364}," Guide; do not act. Connector auth is always owner-initiated.",{"type":43,"tag":51,"props":366,"children":368},{"id":367},"reference",[369],{"type":48,"value":370},"Reference",{"type":43,"tag":96,"props":372,"children":373},{},[374,383,392],{"type":43,"tag":100,"props":375,"children":376},{},[377,381],{"type":43,"tag":162,"props":378,"children":379},{"href":164},[380],{"type":48,"value":164},{"type":48,"value":382}," — interview questions, connector priority matrix, recipe selection, context storage format",{"type":43,"tag":100,"props":384,"children":385},{},[386,390],{"type":43,"tag":162,"props":387,"children":388},{"href":224},[389],{"type":48,"value":224},{"type":48,"value":391}," — Good \u002F Bad patterns for pacing, tool selection, and context storage",{"type":43,"tag":100,"props":393,"children":394},{},[395,399],{"type":43,"tag":162,"props":396,"children":397},{"href":247},[398],{"type":48,"value":247},{"type":48,"value":400}," — worked example: retail shop owner, first session end-to-end",{"items":402,"total":519},[403,419,435,451,469,488,504],{"slug":404,"name":404,"fn":405,"description":406,"org":407,"tags":408,"stars":26,"repoUrl":27,"updatedAt":418},"accessibility-review","run WCAG accessibility audits","Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with \"audit accessibility\", \"check a11y\", \"is this accessible?\", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[409,412,415],{"name":410,"slug":411,"type":16},"Accessibility","accessibility",{"name":413,"slug":414,"type":16},"Design","design",{"name":416,"slug":417,"type":16},"WCAG","wcag","2026-04-06T17:58:05.682394",{"slug":420,"name":420,"fn":421,"description":422,"org":423,"tags":424,"stars":26,"repoUrl":27,"updatedAt":434},"account-research","research accounts for sales intel","Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with \"research [company]\", \"look up [person]\", \"intel on [prospect]\", \"who is [name] at [company]\", or \"tell me about [company]\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[425,428,431],{"name":426,"slug":427,"type":16},"CRM","crm",{"name":429,"slug":430,"type":16},"Research","research",{"name":432,"slug":433,"type":16},"Sales","sales","2026-04-06T17:56:41.410418",{"slug":436,"name":436,"fn":437,"description":438,"org":439,"tags":440,"stars":26,"repoUrl":27,"updatedAt":450},"analyze","answer data questions and run analyses","Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[441,444,447],{"name":442,"slug":443,"type":16},"Analytics","analytics",{"name":445,"slug":446,"type":16},"Data Analysis","data-analysis",{"name":448,"slug":449,"type":16},"SQL","sql","2026-04-06T17:57:21.593647",{"slug":452,"name":452,"fn":453,"description":454,"org":455,"tags":456,"stars":26,"repoUrl":27,"updatedAt":468},"architecture","create and evaluate architecture decision records","Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[457,460,462,465],{"name":458,"slug":459,"type":16},"ADR","adr",{"name":461,"slug":452,"type":16},"Architecture",{"name":463,"slug":464,"type":16},"Documentation","documentation",{"name":466,"slug":467,"type":16},"Engineering","engineering","2026-04-06T17:57:49.26444",{"slug":470,"name":470,"fn":471,"description":472,"org":473,"tags":474,"stars":26,"repoUrl":27,"updatedAt":487},"audit-support","support SOX 404 control testing","Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[475,478,481,484],{"name":476,"slug":477,"type":16},"Audit","audit",{"name":479,"slug":480,"type":16},"Finance","finance",{"name":482,"slug":483,"type":16},"Regulatory Compliance","regulatory-compliance",{"name":485,"slug":486,"type":16},"SOX","sox","2026-04-06T17:57:36.714815",{"slug":489,"name":489,"fn":490,"description":491,"org":492,"tags":493,"stars":26,"repoUrl":27,"updatedAt":503},"brand-review","review content against brand voice","Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before\u002Fafter fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[494,497,500],{"name":495,"slug":496,"type":16},"Branding","branding",{"name":498,"slug":499,"type":16},"Marketing","marketing",{"name":501,"slug":502,"type":16},"Writing","writing","2026-04-06T17:58:19.548331",{"slug":505,"name":505,"fn":506,"description":507,"org":508,"tags":509,"stars":26,"repoUrl":27,"updatedAt":518},"brand-voice-enforcement","enforce brand voice in content","This skill applies brand guidelines to content creation. It should be used when the user asks to \"write an email\", \"draft a proposal\", \"create a pitch deck\", \"write a LinkedIn post\", \"draft a presentation\", \"write a Slack message\", \"draft sales content\", or any content creation request where brand voice should be applied. Also triggers on \"on-brand\", \"brand voice\", \"enforce voice\", \"apply brand guidelines\", \"brand-aligned content\", \"write in our voice\", \"use our brand tone\", \"make this sound like us\", \"rewrite this in our tone\", or \"this doesn't sound on-brand\". Not for generating guidelines from scratch (use guideline-generation) or discovering brand materials (use discover-brand).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[510,511,514,517],{"name":495,"slug":496,"type":16},{"name":512,"slug":513,"type":16},"Communications","communications",{"name":515,"slug":516,"type":16},"Content Creation","content-creation",{"name":501,"slug":502,"type":16},"2026-04-06T18:00:23.528956",200,{"items":521,"total":698},[522,541,553,565,584,595,616,636,646,661,669,682],{"slug":523,"name":523,"fn":524,"description":525,"org":526,"tags":527,"stars":538,"repoUrl":539,"updatedAt":540},"algorithmic-art","create algorithmic art with p5.js","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[528,531,532,535],{"name":529,"slug":530,"type":16},"Creative","creative",{"name":413,"slug":414,"type":16},{"name":533,"slug":534,"type":16},"Generative Art","generative-art",{"name":536,"slug":537,"type":16},"JavaScript","javascript",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-04-06T17:56:15.455818",{"slug":542,"name":542,"fn":543,"description":544,"org":545,"tags":546,"stars":538,"repoUrl":539,"updatedAt":552},"brand-guidelines","apply Anthropic brand colors and typography","Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[547,548,549],{"name":495,"slug":496,"type":16},{"name":413,"slug":414,"type":16},{"name":550,"slug":551,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":554,"name":554,"fn":555,"description":556,"org":557,"tags":558,"stars":538,"repoUrl":539,"updatedAt":564},"canvas-design","create posters and visual art as PNG or PDF","Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[559,560,561],{"name":529,"slug":530,"type":16},{"name":413,"slug":414,"type":16},{"name":562,"slug":563,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":566,"name":566,"fn":567,"description":568,"org":569,"tags":570,"stars":538,"repoUrl":539,"updatedAt":583},"claude-api","build apps with the Claude API","Reference for the Claude API \u002F Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.\nTRIGGER — read BEFORE opening the target file; don't skip because it \"looks like a one-liner\" — whenever: the prompt names Claude\u002FAnthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing\u002Fmodel choice\u002Flimits\u002Fcaching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent\u002FMCP\u002Ftool-definition\u002Fmulti-agent\u002FRAG\u002FLLM-judge\u002Fcomputer-use; generate\u002Fsummarize\u002Fextract\u002Fclassify\u002Frewrite\u002Fconverse over NL; debugging refusals\u002Fcutoffs\u002Fstreaming\u002Ftool-calls\u002Ftokens).\nSKIP only when another provider is being worked on (overrides all triggers): OpenAI\u002FGPT\u002FGemini\u002FLlama\u002FMistral\u002FCohere\u002FOllama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[571,574,575,578,580],{"name":572,"slug":573,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":576,"slug":577,"type":16},"Anthropic SDK","anthropic-sdk",{"name":579,"slug":566,"type":16},"Claude API",{"name":581,"slug":582,"type":16},"LLM","llm","2026-07-28T05:36:08.213335",{"slug":585,"name":585,"fn":586,"description":587,"org":588,"tags":589,"stars":538,"repoUrl":539,"updatedAt":594},"doc-coauthoring","co-author documentation and technical specs","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[590,591],{"name":463,"slug":464,"type":16},{"name":592,"slug":593,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":596,"name":596,"fn":597,"description":598,"org":599,"tags":600,"stars":538,"repoUrl":539,"updatedAt":615},"docx","create and edit Word documents","Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[601,604,606,609,612],{"name":602,"slug":603,"type":16},"Documents","documents",{"name":605,"slug":596,"type":16},"DOCX",{"name":607,"slug":608,"type":16},"Office","office",{"name":610,"slug":611,"type":16},"Templates","templates",{"name":613,"slug":614,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":617,"name":617,"fn":618,"description":619,"org":620,"tags":621,"stars":538,"repoUrl":539,"updatedAt":635},"frontend-design","design production-grade frontend interfaces","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[622,623,626,629,632],{"name":413,"slug":414,"type":16},{"name":624,"slug":625,"type":16},"Frontend","frontend",{"name":627,"slug":628,"type":16},"React","react",{"name":630,"slug":631,"type":16},"Tailwind CSS","tailwind-css",{"name":633,"slug":634,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":637,"name":637,"fn":638,"description":639,"org":640,"tags":641,"stars":538,"repoUrl":539,"updatedAt":645},"internal-comms","write internal company communications","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[642,643,644],{"name":512,"slug":513,"type":16},{"name":610,"slug":611,"type":16},{"name":501,"slug":502,"type":16},"2026-04-06T17:56:20.695522",{"slug":647,"name":647,"fn":648,"description":649,"org":650,"tags":651,"stars":538,"repoUrl":539,"updatedAt":660},"mcp-builder","build MCP servers","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node\u002FTypeScript (MCP SDK).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[652,653,656,657],{"name":572,"slug":573,"type":16},{"name":654,"slug":655,"type":16},"API Development","api-development",{"name":581,"slug":582,"type":16},{"name":658,"slug":659,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":563,"name":563,"fn":662,"description":663,"org":664,"tags":665,"stars":538,"repoUrl":539,"updatedAt":668},"read edit and manipulate PDF files","Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text\u002Ftables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting\u002Fdecrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[666,667],{"name":602,"slug":603,"type":16},{"name":562,"slug":563,"type":16},"2026-04-06T17:56:02.483316",{"slug":670,"name":670,"fn":671,"description":672,"org":673,"tags":674,"stars":538,"repoUrl":539,"updatedAt":681},"pptx","create and edit PowerPoint presentations","Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[675,678],{"name":676,"slug":677,"type":16},"PowerPoint","powerpoint",{"name":679,"slug":680,"type":16},"Presentations","presentations","2026-07-18T05:16:24.1471",{"slug":683,"name":683,"fn":684,"description":685,"org":686,"tags":687,"stars":538,"repoUrl":539,"updatedAt":697},"skill-creator","create and optimize agent skills","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[688,689,690,693,696],{"name":572,"slug":573,"type":16},{"name":463,"slug":464,"type":16},{"name":691,"slug":692,"type":16},"Evals","evals",{"name":694,"slug":695,"type":16},"Performance","performance",{"name":592,"slug":593,"type":16},"2026-04-19T06:45:40.804",490]