[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-crm-maintenance":3,"mdc--jqnyqz-key":40,"related-org-anthropic-crm-maintenance":408,"related-repo-anthropic-crm-maintenance":597},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":29,"repoUrl":30,"updatedAt":31,"license":32,"forks":33,"topics":34,"repo":35,"sourceUrl":38,"mdContent":39},"crm-maintenance","maintain HubSpot CRM records","Keeps HubSpot current without the owner opening it: creates and updates contacts and deals from email and calendar context, logs notes and calls, and flags stale records. The \"stop doing data entry\" skill. Use when the user asks to update the CRM, log a call, clean up HubSpot, or add context to a deal.\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,26],{"name":14,"slug":15,"type":16},"Operations","operations","tag",{"name":18,"slug":19,"type":16},"Automation","automation",{"name":21,"slug":22,"type":16},"CRM","crm",{"name":24,"slug":25,"type":16},"Sales","sales",{"name":27,"slug":28,"type":16},"HubSpot","hubspot",22885,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","2026-05-14T06:03:16.18061",null,2736,[],{"repoUrl":30,"stars":29,"forks":33,"topics":36,"description":37},[],"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\u002Fcrm-maintenance","---\nname: crm-maintenance\ndescription: >\n  Keeps HubSpot current without the owner opening it: creates and updates\n  contacts and deals from email and calendar context, logs notes and calls,\n  and flags stale records. The \"stop doing data entry\" skill. Use when the\n  user asks to update the CRM, log a call, clean up HubSpot, or add context\n  to a deal.\n---\n\n# CRM Maintenance\n\n## Quick start\n\nPull context from the referenced email or calendar event, resolve the right HubSpot contact and deal, log the activity, and surface what changed. For a deal cleanup, audit the deal against recent email\u002Fcalendar activity and propose updates — never apply them without approval.\n\n```\nUser: \"log this call to the Acme deal\"\n→ Read the most recent completed calendar event\n→ Confirm attendees map to the Acme deal's contacts\n→ Write a call activity on the Acme deal\n→ Report: \"Logged call to Acme Q2 Expansion. [deal link]\"\n```\n\n## Workflow\n\n1. **Identify intent.** Decide which of three paths applies from the user's message and context:\n   - **Email path** — \"update my CRM\", \"add this to the deal\", or any reference to an email thread\n   - **Call path** — \"log this call\", \"log the meeting\", or any reference to a calendar event\n   - **Cleanup path** — \"clean up HubSpot\", \"is this deal up to date\", or any request to audit a specific deal\n   If the intent is ambiguous (e.g. \"update HubSpot\" with no referenced email\u002Fmeeting\u002Fdeal), ask which path before proceeding.\n\n2. **Gather context.**\n   - Email path: read the thread (subject, participants, last 1–3 messages). Identify the primary external contact.\n   - Call path: read the calendar event (title, attendees, time, description). If no event was specified, use the most recent completed meeting in the last 24 hours and confirm with the user before proceeding.\n   - Cleanup path: pull the deal (stage, amount, close date, next-step, associated contacts, activities in last 60 days), plus the last 14 days of email threads and calendar events involving the deal's contacts.\n\n3. **Resolve the HubSpot contact and deal.** For email\u002Fcall paths:\n   - Search HubSpot contacts by email address. If a contact is missing, create it from email signature or calendar invite data — announce creation in chat before writing.\n   - Find the right deal in this order: (a) explicit match if the user named one, (b) the contact's sole open deal, (c) fuzzy match across the contact's open deals against the email subject or meeting title — confirm before writing, (d) ask the user if no match. **Never auto-create a deal.**\n   - For field names, activity types, and association rules, read [reference\u002Fhubspot-fields.md](reference\u002Fhubspot-fields.md) before writing anything to HubSpot.\n   - If deduplication or deal-resolution feels ambiguous, check [reference\u002Fgotchas.md](reference\u002Fgotchas.md) before proceeding — it covers the most common failure modes.\n\n4. **Execute the action.**\n   - Email path: write an email activity with the thread subject as the title and a concise summary (not the full thread) as the body. Timestamp to the latest message. For a worked example, see [reference\u002Fexamples\u002Flog-email-happy-path.md](reference\u002Fexamples\u002Flog-email-happy-path.md).\n   - Call path: write a call activity with the event title, duration, and any notes available. Timestamp to the event start. For a worked example including a missing-contact scenario, see [reference\u002Fexamples\u002Flog-call-happy-path.md](reference\u002Fexamples\u002Flog-call-happy-path.md).\n   - Cleanup path: walk each field per [reference\u002Fcleanup-checklist.md](reference\u002Fcleanup-checklist.md) and assemble a proposed-changes list. Show current → proposed side-by-side. Write only what the user approves. For a full worked example, see [reference\u002Fexamples\u002Fcleanup-deal.md](reference\u002Fexamples\u002Fcleanup-deal.md).\n\n5. **Approval gate — every externally visible write.** For contact creation and activity logging, announce before writing and surface the result after. For cleanup edits, do not write anything until the user approves the specific changes.\n\n6. **Report what happened.** Tell the user what was written and what's pending. Include a HubSpot link to the affected deal when possible. Keep it short.\n\n## Approval gates\n\n- **Never delete records.** Not contacts, not deals, not activities. If the user asks, say the skill cannot and direct them to HubSpot.\n- **Never change deal stage or close a deal without explicit user approval.** Even if evidence is strong. Flag and defer.\n- **Never create a new deal unprompted.** Ask if the right deal can't be resolved.\n- **Announce contact creation before writing.** One line — lets the user catch typos or duplicates.\n- **Side-by-side diffs for cleanup.** Show current value and proposed value; wait for approval per item.\n\n## Reference\n\n- [reference\u002Fhubspot-fields.md](reference\u002Fhubspot-fields.md) — activity types, field names, association rules used in this skill\n- [reference\u002Fcleanup-checklist.md](reference\u002Fcleanup-checklist.md) — the fields checked during a deal cleanup and the evidence needed to flag each\n- [reference\u002Fgotchas.md](reference\u002Fgotchas.md) — Good \u002F Bad patterns for contact resolution, activity summaries, and cleanup proposals\n- [reference\u002Fexamples\u002Flog-email-happy-path.md](reference\u002Fexamples\u002Flog-email-happy-path.md) — worked example: email to existing deal\n- [reference\u002Fexamples\u002Flog-call-happy-path.md](reference\u002Fexamples\u002Flog-call-happy-path.md) — worked example: meeting to existing deal, missing contact\n- [reference\u002Fexamples\u002Fcleanup-deal.md](reference\u002Fexamples\u002Fcleanup-deal.md) — worked example: stale deal audit\n",{"data":41,"body":42},{"name":4,"description":6},{"type":43,"children":44},"root",[45,53,60,66,79,85,286,292,345,351],{"type":46,"tag":47,"props":48,"children":49},"element","h1",{"id":4},[50],{"type":51,"value":52},"text","CRM Maintenance",{"type":46,"tag":54,"props":55,"children":57},"h2",{"id":56},"quick-start",[58],{"type":51,"value":59},"Quick start",{"type":46,"tag":61,"props":62,"children":63},"p",{},[64],{"type":51,"value":65},"Pull context from the referenced email or calendar event, resolve the right HubSpot contact and deal, log the activity, and surface what changed. For a deal cleanup, audit the deal against recent email\u002Fcalendar activity and propose updates — never apply them without approval.",{"type":46,"tag":67,"props":68,"children":72},"pre",{"className":69,"code":71,"language":51},[70],"language-text","User: \"log this call to the Acme deal\"\n→ Read the most recent completed calendar event\n→ Confirm attendees map to the Acme deal's contacts\n→ Write a call activity on the Acme deal\n→ Report: \"Logged call to Acme Q2 Expansion. [deal link]\"\n",[73],{"type":46,"tag":74,"props":75,"children":77},"code",{"__ignoreMap":76},"",[78],{"type":51,"value":71},{"type":46,"tag":54,"props":80,"children":82},{"id":81},"workflow",[83],{"type":51,"value":84},"Workflow",{"type":46,"tag":86,"props":87,"children":88},"ol",{},[89,135,161,214,266,276],{"type":46,"tag":90,"props":91,"children":92},"li",{},[93,99,101],{"type":46,"tag":94,"props":95,"children":96},"strong",{},[97],{"type":51,"value":98},"Identify intent.",{"type":51,"value":100}," Decide which of three paths applies from the user's message and context:",{"type":46,"tag":102,"props":103,"children":104},"ul",{},[105,115,125],{"type":46,"tag":90,"props":106,"children":107},{},[108,113],{"type":46,"tag":94,"props":109,"children":110},{},[111],{"type":51,"value":112},"Email path",{"type":51,"value":114}," — \"update my CRM\", \"add this to the deal\", or any reference to an email thread",{"type":46,"tag":90,"props":116,"children":117},{},[118,123],{"type":46,"tag":94,"props":119,"children":120},{},[121],{"type":51,"value":122},"Call path",{"type":51,"value":124}," — \"log this call\", \"log the meeting\", or any reference to a calendar event",{"type":46,"tag":90,"props":126,"children":127},{},[128,133],{"type":46,"tag":94,"props":129,"children":130},{},[131],{"type":51,"value":132},"Cleanup path",{"type":51,"value":134}," — \"clean up HubSpot\", \"is this deal up to date\", or any request to audit a specific deal\nIf the intent is ambiguous (e.g. \"update HubSpot\" with no referenced email\u002Fmeeting\u002Fdeal), ask which path before proceeding.",{"type":46,"tag":90,"props":136,"children":137},{},[138,143],{"type":46,"tag":94,"props":139,"children":140},{},[141],{"type":51,"value":142},"Gather context.",{"type":46,"tag":102,"props":144,"children":145},{},[146,151,156],{"type":46,"tag":90,"props":147,"children":148},{},[149],{"type":51,"value":150},"Email path: read the thread (subject, participants, last 1–3 messages). Identify the primary external contact.",{"type":46,"tag":90,"props":152,"children":153},{},[154],{"type":51,"value":155},"Call path: read the calendar event (title, attendees, time, description). If no event was specified, use the most recent completed meeting in the last 24 hours and confirm with the user before proceeding.",{"type":46,"tag":90,"props":157,"children":158},{},[159],{"type":51,"value":160},"Cleanup path: pull the deal (stage, amount, close date, next-step, associated contacts, activities in last 60 days), plus the last 14 days of email threads and calendar events involving the deal's contacts.",{"type":46,"tag":90,"props":162,"children":163},{},[164,169,171],{"type":46,"tag":94,"props":165,"children":166},{},[167],{"type":51,"value":168},"Resolve the HubSpot contact and deal.",{"type":51,"value":170}," For email\u002Fcall paths:",{"type":46,"tag":102,"props":172,"children":173},{},[174,179,189,202],{"type":46,"tag":90,"props":175,"children":176},{},[177],{"type":51,"value":178},"Search HubSpot contacts by email address. If a contact is missing, create it from email signature or calendar invite data — announce creation in chat before writing.",{"type":46,"tag":90,"props":180,"children":181},{},[182,184],{"type":51,"value":183},"Find the right deal in this order: (a) explicit match if the user named one, (b) the contact's sole open deal, (c) fuzzy match across the contact's open deals against the email subject or meeting title — confirm before writing, (d) ask the user if no match. ",{"type":46,"tag":94,"props":185,"children":186},{},[187],{"type":51,"value":188},"Never auto-create a deal.",{"type":46,"tag":90,"props":190,"children":191},{},[192,194,200],{"type":51,"value":193},"For field names, activity types, and association rules, read ",{"type":46,"tag":195,"props":196,"children":198},"a",{"href":197},"reference\u002Fhubspot-fields.md",[199],{"type":51,"value":197},{"type":51,"value":201}," before writing anything to HubSpot.",{"type":46,"tag":90,"props":203,"children":204},{},[205,207,212],{"type":51,"value":206},"If deduplication or deal-resolution feels ambiguous, check ",{"type":46,"tag":195,"props":208,"children":210},{"href":209},"reference\u002Fgotchas.md",[211],{"type":51,"value":209},{"type":51,"value":213}," before proceeding — it covers the most common failure modes.",{"type":46,"tag":90,"props":215,"children":216},{},[217,222],{"type":46,"tag":94,"props":218,"children":219},{},[220],{"type":51,"value":221},"Execute the action.",{"type":46,"tag":102,"props":223,"children":224},{},[225,237,248],{"type":46,"tag":90,"props":226,"children":227},{},[228,230,235],{"type":51,"value":229},"Email path: write an email activity with the thread subject as the title and a concise summary (not the full thread) as the body. Timestamp to the latest message. For a worked example, see ",{"type":46,"tag":195,"props":231,"children":233},{"href":232},"reference\u002Fexamples\u002Flog-email-happy-path.md",[234],{"type":51,"value":232},{"type":51,"value":236},".",{"type":46,"tag":90,"props":238,"children":239},{},[240,242,247],{"type":51,"value":241},"Call path: write a call activity with the event title, duration, and any notes available. Timestamp to the event start. For a worked example including a missing-contact scenario, see ",{"type":46,"tag":195,"props":243,"children":245},{"href":244},"reference\u002Fexamples\u002Flog-call-happy-path.md",[246],{"type":51,"value":244},{"type":51,"value":236},{"type":46,"tag":90,"props":249,"children":250},{},[251,253,258,260,265],{"type":51,"value":252},"Cleanup path: walk each field per ",{"type":46,"tag":195,"props":254,"children":256},{"href":255},"reference\u002Fcleanup-checklist.md",[257],{"type":51,"value":255},{"type":51,"value":259}," and assemble a proposed-changes list. Show current → proposed side-by-side. Write only what the user approves. For a full worked example, see ",{"type":46,"tag":195,"props":261,"children":263},{"href":262},"reference\u002Fexamples\u002Fcleanup-deal.md",[264],{"type":51,"value":262},{"type":51,"value":236},{"type":46,"tag":90,"props":267,"children":268},{},[269,274],{"type":46,"tag":94,"props":270,"children":271},{},[272],{"type":51,"value":273},"Approval gate — every externally visible write.",{"type":51,"value":275}," For contact creation and activity logging, announce before writing and surface the result after. For cleanup edits, do not write anything until the user approves the specific changes.",{"type":46,"tag":90,"props":277,"children":278},{},[279,284],{"type":46,"tag":94,"props":280,"children":281},{},[282],{"type":51,"value":283},"Report what happened.",{"type":51,"value":285}," Tell the user what was written and what's pending. Include a HubSpot link to the affected deal when possible. Keep it short.",{"type":46,"tag":54,"props":287,"children":289},{"id":288},"approval-gates",[290],{"type":51,"value":291},"Approval gates",{"type":46,"tag":102,"props":293,"children":294},{},[295,305,315,325,335],{"type":46,"tag":90,"props":296,"children":297},{},[298,303],{"type":46,"tag":94,"props":299,"children":300},{},[301],{"type":51,"value":302},"Never delete records.",{"type":51,"value":304}," Not contacts, not deals, not activities. If the user asks, say the skill cannot and direct them to HubSpot.",{"type":46,"tag":90,"props":306,"children":307},{},[308,313],{"type":46,"tag":94,"props":309,"children":310},{},[311],{"type":51,"value":312},"Never change deal stage or close a deal without explicit user approval.",{"type":51,"value":314}," Even if evidence is strong. Flag and defer.",{"type":46,"tag":90,"props":316,"children":317},{},[318,323],{"type":46,"tag":94,"props":319,"children":320},{},[321],{"type":51,"value":322},"Never create a new deal unprompted.",{"type":51,"value":324}," Ask if the right deal can't be resolved.",{"type":46,"tag":90,"props":326,"children":327},{},[328,333],{"type":46,"tag":94,"props":329,"children":330},{},[331],{"type":51,"value":332},"Announce contact creation before writing.",{"type":51,"value":334}," One line — lets the user catch typos or duplicates.",{"type":46,"tag":90,"props":336,"children":337},{},[338,343],{"type":46,"tag":94,"props":339,"children":340},{},[341],{"type":51,"value":342},"Side-by-side diffs for cleanup.",{"type":51,"value":344}," Show current value and proposed value; wait for approval per item.",{"type":46,"tag":54,"props":346,"children":348},{"id":347},"reference",[349],{"type":51,"value":350},"Reference",{"type":46,"tag":102,"props":352,"children":353},{},[354,363,372,381,390,399],{"type":46,"tag":90,"props":355,"children":356},{},[357,361],{"type":46,"tag":195,"props":358,"children":359},{"href":197},[360],{"type":51,"value":197},{"type":51,"value":362}," — activity types, field names, association rules used in this skill",{"type":46,"tag":90,"props":364,"children":365},{},[366,370],{"type":46,"tag":195,"props":367,"children":368},{"href":255},[369],{"type":51,"value":255},{"type":51,"value":371}," — the fields checked during a deal cleanup and the evidence needed to flag each",{"type":46,"tag":90,"props":373,"children":374},{},[375,379],{"type":46,"tag":195,"props":376,"children":377},{"href":209},[378],{"type":51,"value":209},{"type":51,"value":380}," — Good \u002F Bad patterns for contact resolution, activity summaries, and cleanup proposals",{"type":46,"tag":90,"props":382,"children":383},{},[384,388],{"type":46,"tag":195,"props":385,"children":386},{"href":232},[387],{"type":51,"value":232},{"type":51,"value":389}," — worked example: email to existing deal",{"type":46,"tag":90,"props":391,"children":392},{},[393,397],{"type":46,"tag":195,"props":394,"children":395},{"href":244},[396],{"type":51,"value":244},{"type":51,"value":398}," — worked example: meeting to existing deal, missing contact",{"type":46,"tag":90,"props":400,"children":401},{},[402,406],{"type":46,"tag":195,"props":403,"children":404},{"href":262},[405],{"type":51,"value":262},{"type":51,"value":407}," — worked example: stale deal audit",{"items":409,"total":596},[410,431,445,457,476,489,510,530,544,559,567,580],{"slug":411,"name":411,"fn":412,"description":413,"org":414,"tags":415,"stars":428,"repoUrl":429,"updatedAt":430},"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},[416,419,422,425],{"name":417,"slug":418,"type":16},"Creative","creative",{"name":420,"slug":421,"type":16},"Design","design",{"name":423,"slug":424,"type":16},"Generative Art","generative-art",{"name":426,"slug":427,"type":16},"JavaScript","javascript",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-04-06T17:56:15.455818",{"slug":432,"name":432,"fn":433,"description":434,"org":435,"tags":436,"stars":428,"repoUrl":429,"updatedAt":444},"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},[437,440,441],{"name":438,"slug":439,"type":16},"Branding","branding",{"name":420,"slug":421,"type":16},{"name":442,"slug":443,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":446,"name":446,"fn":447,"description":448,"org":449,"tags":450,"stars":428,"repoUrl":429,"updatedAt":456},"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},[451,452,453],{"name":417,"slug":418,"type":16},{"name":420,"slug":421,"type":16},{"name":454,"slug":455,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":458,"name":458,"fn":459,"description":460,"org":461,"tags":462,"stars":428,"repoUrl":429,"updatedAt":475},"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},[463,466,467,470,472],{"name":464,"slug":465,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":468,"slug":469,"type":16},"Anthropic SDK","anthropic-sdk",{"name":471,"slug":458,"type":16},"Claude API",{"name":473,"slug":474,"type":16},"LLM","llm","2026-07-28T05:36:08.213335",{"slug":477,"name":477,"fn":478,"description":479,"org":480,"tags":481,"stars":428,"repoUrl":429,"updatedAt":488},"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},[482,485],{"name":483,"slug":484,"type":16},"Documentation","documentation",{"name":486,"slug":487,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":490,"name":490,"fn":491,"description":492,"org":493,"tags":494,"stars":428,"repoUrl":429,"updatedAt":509},"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},[495,498,500,503,506],{"name":496,"slug":497,"type":16},"Documents","documents",{"name":499,"slug":490,"type":16},"DOCX",{"name":501,"slug":502,"type":16},"Office","office",{"name":504,"slug":505,"type":16},"Templates","templates",{"name":507,"slug":508,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":511,"name":511,"fn":512,"description":513,"org":514,"tags":515,"stars":428,"repoUrl":429,"updatedAt":529},"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},[516,517,520,523,526],{"name":420,"slug":421,"type":16},{"name":518,"slug":519,"type":16},"Frontend","frontend",{"name":521,"slug":522,"type":16},"React","react",{"name":524,"slug":525,"type":16},"Tailwind CSS","tailwind-css",{"name":527,"slug":528,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":531,"name":531,"fn":532,"description":533,"org":534,"tags":535,"stars":428,"repoUrl":429,"updatedAt":543},"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},[536,539,540],{"name":537,"slug":538,"type":16},"Communications","communications",{"name":504,"slug":505,"type":16},{"name":541,"slug":542,"type":16},"Writing","writing","2026-04-06T17:56:20.695522",{"slug":545,"name":545,"fn":546,"description":547,"org":548,"tags":549,"stars":428,"repoUrl":429,"updatedAt":558},"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},[550,551,554,555],{"name":464,"slug":465,"type":16},{"name":552,"slug":553,"type":16},"API Development","api-development",{"name":473,"slug":474,"type":16},{"name":556,"slug":557,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":455,"name":455,"fn":560,"description":561,"org":562,"tags":563,"stars":428,"repoUrl":429,"updatedAt":566},"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},[564,565],{"name":496,"slug":497,"type":16},{"name":454,"slug":455,"type":16},"2026-04-06T17:56:02.483316",{"slug":568,"name":568,"fn":569,"description":570,"org":571,"tags":572,"stars":428,"repoUrl":429,"updatedAt":579},"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},[573,576],{"name":574,"slug":575,"type":16},"PowerPoint","powerpoint",{"name":577,"slug":578,"type":16},"Presentations","presentations","2026-07-18T05:16:24.1471",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":428,"repoUrl":429,"updatedAt":595},"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},[586,587,588,591,594],{"name":464,"slug":465,"type":16},{"name":483,"slug":484,"type":16},{"name":589,"slug":590,"type":16},"Evals","evals",{"name":592,"slug":593,"type":16},"Performance","performance",{"name":486,"slug":487,"type":16},"2026-04-19T06:45:40.804",490,{"items":598,"total":701},[599,613,625,641,657,676,688],{"slug":600,"name":600,"fn":601,"description":602,"org":603,"tags":604,"stars":29,"repoUrl":30,"updatedAt":612},"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},[605,608,609],{"name":606,"slug":607,"type":16},"Accessibility","accessibility",{"name":420,"slug":421,"type":16},{"name":610,"slug":611,"type":16},"WCAG","wcag","2026-04-06T17:58:05.682394",{"slug":614,"name":614,"fn":615,"description":616,"org":617,"tags":618,"stars":29,"repoUrl":30,"updatedAt":624},"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},[619,620,623],{"name":21,"slug":22,"type":16},{"name":621,"slug":622,"type":16},"Research","research",{"name":24,"slug":25,"type":16},"2026-04-06T17:56:41.410418",{"slug":626,"name":626,"fn":627,"description":628,"org":629,"tags":630,"stars":29,"repoUrl":30,"updatedAt":640},"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},[631,634,637],{"name":632,"slug":633,"type":16},"Analytics","analytics",{"name":635,"slug":636,"type":16},"Data Analysis","data-analysis",{"name":638,"slug":639,"type":16},"SQL","sql","2026-04-06T17:57:21.593647",{"slug":642,"name":642,"fn":643,"description":644,"org":645,"tags":646,"stars":29,"repoUrl":30,"updatedAt":656},"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},[647,650,652,653],{"name":648,"slug":649,"type":16},"ADR","adr",{"name":651,"slug":642,"type":16},"Architecture",{"name":483,"slug":484,"type":16},{"name":654,"slug":655,"type":16},"Engineering","engineering","2026-04-06T17:57:49.26444",{"slug":658,"name":658,"fn":659,"description":660,"org":661,"tags":662,"stars":29,"repoUrl":30,"updatedAt":675},"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},[663,666,669,672],{"name":664,"slug":665,"type":16},"Audit","audit",{"name":667,"slug":668,"type":16},"Finance","finance",{"name":670,"slug":671,"type":16},"Regulatory Compliance","regulatory-compliance",{"name":673,"slug":674,"type":16},"SOX","sox","2026-04-06T17:57:36.714815",{"slug":677,"name":677,"fn":678,"description":679,"org":680,"tags":681,"stars":29,"repoUrl":30,"updatedAt":687},"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},[682,683,686],{"name":438,"slug":439,"type":16},{"name":684,"slug":685,"type":16},"Marketing","marketing",{"name":541,"slug":542,"type":16},"2026-04-06T17:58:19.548331",{"slug":689,"name":689,"fn":690,"description":691,"org":692,"tags":693,"stars":29,"repoUrl":30,"updatedAt":700},"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},[694,695,696,699],{"name":438,"slug":439,"type":16},{"name":537,"slug":538,"type":16},{"name":697,"slug":698,"type":16},"Content Creation","content-creation",{"name":541,"slug":542,"type":16},"2026-04-06T18:00:23.528956",200]