[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-handoff":3,"mdc--tfm9bj-key":37,"related-org-anthropic-handoff":393,"related-repo-anthropic-handoff":579},{"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},"handoff","draft weekly on-call handoff reports","Write the weekly on-call handoff: everything the incoming on-call needs, triage-ready, posted to the channel at shift boundary. Use when the weekly routine fires, or when someone asks for a handoff \u002F shift summary \u002F \"catch the next on-call up\".\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},"Runbooks","runbooks",{"name":21,"slug":22,"type":16},"Management","management",{"name":24,"slug":25,"type":16},"Communications","communications",3,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Foncall-kit","2026-08-19T03:58:55.767403",null,0,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"Starter kit for a Claude-assisted on-call: mines your incident history into triage playbooks, sets up through human-approved gates, and runs read-only in your Slack channel — humans deploy every fix.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Foncall-kit\u002Ftree\u002FHEAD\u002Fskills\u002Fhandoff","---\nname: handoff\ndescription: >\n  Write the weekly on-call handoff: everything the incoming on-call needs,\n  triage-ready, posted to the channel at shift boundary. Use when the weekly\n  routine fires, or when someone asks for a handoff \u002F shift summary \u002F \"catch\n  the next on-call up\".\n---\n\n\u003C!-- Copyright 2026 Anthropic PBC -->\n\u003C!-- SPDX-License-Identifier: Apache-2.0 -->\n\n# Handoff\n\nStanding rules in `CLAUDE.md` apply — especially rules 10 and 11: fresh\nreader, lead with what to do. The incoming on-call missed everything; this\ndocument is their entire week's context, and it must arrive as **work they\ncan start**, not \"here's what happened\".\n\n## Sources — sweep all of them\n\nFan out across every capability in `STACK.md` for the shift window\n(default: the week since the last handoff):\n\n- `pager` — every page and incident: state, severity, resolution\n- `alert-channels` — what fired, what people said, what never got a thread\n- `code` — merges\u002FPRs touching on-call-relevant paths; reverts; deploys\n- `metrics` — week-over-week trend of the health signals in `ONCALL.md`\n- `lessons.md` — every entry appended this shift\n- each incident record's history over the shift window\n\nCross-reference: an alert with no thread, a lessons entry with no incident,\na metric trending wrong with no alert — these orphans are usually the \"watch\nthis week\" items.\n\n## Format\n\nPost to the channel as a message with the exec summary, full doc attached or\nlinked:\n\n> 📋 **On-call handoff — week of {{date}}**\n>\n> **Exec summary:** N incidents (n resolved, n monitoring). N pages.\n> Anything systemic in one clause.\n> **On-call health:** the required weekly metric — incidents and pages\n> vs. last week, split by business-hours \u002F off-hours, false pages, the\n> **rubber-stamp fraction** (diagnoses acted on with no recorded\n> verification step — the early warning that humans stopped\n> cross-examining; see eval\u002Freplay.md), and whether the trend is up or\n> down. This section is how the whole setup is\n> measured over time (see eval\u002Freplay.md), so never omit it and never\n> soften it.\n> **Intake health:** median and worst time from symptom onset to incident\n> declared this week (onset from the alert\u002Fthread timeline; declaration\n> from the incident record). If incidents routinely run 40 minutes before\n> anyone declares one, that's the process finding of the week — you can't\n> fix an intake path you don't measure.\n> **Watch this week:** the 1–3 things most likely to page you, each with\n> why and a link to its pattern (`lessons.md` tag or reference file).\n> **Start here:** the single highest-priority open item, with its current\n> state and next action.\n> **Full doc:** [link] · New to this channel? Read `ONBOARD.md` — how to\n> read a diagnosis, challenge one, or silence a routine.\n\nThe full doc, per incident: **what happened** (one fresh-reader sentence,\nlinks) · **what it means** (pattern or one-off? systemic risk?) · **what you\nshould do** (nothing \u002F monitor \u002F action, with the action named).\n\nThen: open items ranked by \"will this page you?\", not by age. Preventable\nrepeats called out as playbook gaps with proposed reference-file amendments\n(rule 9 — fix the playbook, not just the incident).\n\n## Drift check (required section)\n\nThe ground moves between incidents; this is where the kit notices. Each\nweek, flag:\n\n- any `STACK.md` binding that failed or 403'd during the week's work\n- any reference file whose first-checks cite a tool or query that no\n  longer responds\n- anything in the `deploys` feed or announcement channels suggesting the\n  infrastructure changed under the playbooks — a migration completed, a\n  tool replaced, a service renamed\n- the routine registry vs. reality: does the \"Standing work\" canvas match\n  the channel's actual routines? Fix the registry; flag any routine that\n  exists but was never registered\n- open incidents with no update in >{{72h}} — the zombie list, each with\n  its three-leg staleness evidence per ONCALL.md's lifecycle section,\n  framed as \"close it or update it\", never closed by Claude (rule 2)\n\nEach flag arrives as a proposal, never an edit (rule 9): \"re-run Discover\nfor this binding,\" a reference-file amendment PR, or \"re-run the replay\nagainst post-change incidents\" (see eval\u002Freplay.md's re-validation\ntriggers). A quiet week with no drift gets one line: \"no drift detected.\"\n\n## Discipline\n\n- \"Here's what happened\" without \"start here\" is a diary, not a handoff —\n  the priorities are the point.\n- Never soften a preventable repeat. Write it plainly: \"2 auto-reverts,\n  both preventable.\"\n- If the week was quiet, say so in two lines and stop. Padding a quiet week\n  erodes trust in loud ones.\n",{"data":38,"body":39},{"name":4,"description":6},{"type":40,"children":41},"root",[42,50,73,80,93,163,168,174,179,273,299,304,310,315,364,369,375],{"type":43,"tag":44,"props":45,"children":46},"element","h1",{"id":4},[47],{"type":48,"value":49},"text","Handoff",{"type":43,"tag":51,"props":52,"children":53},"p",{},[54,56,63,65,71],{"type":48,"value":55},"Standing rules in ",{"type":43,"tag":57,"props":58,"children":60},"code",{"className":59},[],[61],{"type":48,"value":62},"CLAUDE.md",{"type":48,"value":64}," apply — especially rules 10 and 11: fresh\nreader, lead with what to do. The incoming on-call missed everything; this\ndocument is their entire week's context, and it must arrive as ",{"type":43,"tag":66,"props":67,"children":68},"strong",{},[69],{"type":48,"value":70},"work they\ncan start",{"type":48,"value":72},", not \"here's what happened\".",{"type":43,"tag":74,"props":75,"children":77},"h2",{"id":76},"sources-sweep-all-of-them",[78],{"type":48,"value":79},"Sources — sweep all of them",{"type":43,"tag":51,"props":81,"children":82},{},[83,85,91],{"type":48,"value":84},"Fan out across every capability in ",{"type":43,"tag":57,"props":86,"children":88},{"className":87},[],[89],{"type":48,"value":90},"STACK.md",{"type":48,"value":92}," for the shift window\n(default: the week since the last handoff):",{"type":43,"tag":94,"props":95,"children":96},"ul",{},[97,109,120,130,147,158],{"type":43,"tag":98,"props":99,"children":100},"li",{},[101,107],{"type":43,"tag":57,"props":102,"children":104},{"className":103},[],[105],{"type":48,"value":106},"pager",{"type":48,"value":108}," — every page and incident: state, severity, resolution",{"type":43,"tag":98,"props":110,"children":111},{},[112,118],{"type":43,"tag":57,"props":113,"children":115},{"className":114},[],[116],{"type":48,"value":117},"alert-channels",{"type":48,"value":119}," — what fired, what people said, what never got a thread",{"type":43,"tag":98,"props":121,"children":122},{},[123,128],{"type":43,"tag":57,"props":124,"children":126},{"className":125},[],[127],{"type":48,"value":57},{"type":48,"value":129}," — merges\u002FPRs touching on-call-relevant paths; reverts; deploys",{"type":43,"tag":98,"props":131,"children":132},{},[133,139,141],{"type":43,"tag":57,"props":134,"children":136},{"className":135},[],[137],{"type":48,"value":138},"metrics",{"type":48,"value":140}," — week-over-week trend of the health signals in ",{"type":43,"tag":57,"props":142,"children":144},{"className":143},[],[145],{"type":48,"value":146},"ONCALL.md",{"type":43,"tag":98,"props":148,"children":149},{},[150,156],{"type":43,"tag":57,"props":151,"children":153},{"className":152},[],[154],{"type":48,"value":155},"lessons.md",{"type":48,"value":157}," — every entry appended this shift",{"type":43,"tag":98,"props":159,"children":160},{},[161],{"type":48,"value":162},"each incident record's history over the shift window",{"type":43,"tag":51,"props":164,"children":165},{},[166],{"type":48,"value":167},"Cross-reference: an alert with no thread, a lessons entry with no incident,\na metric trending wrong with no alert — these orphans are usually the \"watch\nthis week\" items.",{"type":43,"tag":74,"props":169,"children":171},{"id":170},"format",[172],{"type":48,"value":173},"Format",{"type":43,"tag":51,"props":175,"children":176},{},[177],{"type":48,"value":178},"Post to the channel as a message with the exec summary, full doc attached or\nlinked:",{"type":43,"tag":180,"props":181,"children":182},"blockquote",{},[183,198],{"type":43,"tag":51,"props":184,"children":185},{},[186,188],{"type":48,"value":187},"📋 ",{"type":43,"tag":66,"props":189,"children":190},{},[191,193],{"type":48,"value":192},"On-call handoff — week of ",{"type":43,"tag":194,"props":195,"children":197},"binding",{"value":196},"date",[],{"type":43,"tag":51,"props":199,"children":200},{},[201,206,208,213,215,220,222,227,229,234,236,241,243,248,250,255,257,263,265,271],{"type":43,"tag":66,"props":202,"children":203},{},[204],{"type":48,"value":205},"Exec summary:",{"type":48,"value":207}," N incidents (n resolved, n monitoring). N pages.\nAnything systemic in one clause.\n",{"type":43,"tag":66,"props":209,"children":210},{},[211],{"type":48,"value":212},"On-call health:",{"type":48,"value":214}," the required weekly metric — incidents and pages\nvs. last week, split by business-hours \u002F off-hours, false pages, the\n",{"type":43,"tag":66,"props":216,"children":217},{},[218],{"type":48,"value":219},"rubber-stamp fraction",{"type":48,"value":221}," (diagnoses acted on with no recorded\nverification step — the early warning that humans stopped\ncross-examining; see eval\u002Freplay.md), and whether the trend is up or\ndown. This section is how the whole setup is\nmeasured over time (see eval\u002Freplay.md), so never omit it and never\nsoften it.\n",{"type":43,"tag":66,"props":223,"children":224},{},[225],{"type":48,"value":226},"Intake health:",{"type":48,"value":228}," median and worst time from symptom onset to incident\ndeclared this week (onset from the alert\u002Fthread timeline; declaration\nfrom the incident record). If incidents routinely run 40 minutes before\nanyone declares one, that's the process finding of the week — you can't\nfix an intake path you don't measure.\n",{"type":43,"tag":66,"props":230,"children":231},{},[232],{"type":48,"value":233},"Watch this week:",{"type":48,"value":235}," the 1–3 things most likely to page you, each with\nwhy and a link to its pattern (",{"type":43,"tag":57,"props":237,"children":239},{"className":238},[],[240],{"type":48,"value":155},{"type":48,"value":242}," tag or reference file).\n",{"type":43,"tag":66,"props":244,"children":245},{},[246],{"type":48,"value":247},"Start here:",{"type":48,"value":249}," the single highest-priority open item, with its current\nstate and next action.\n",{"type":43,"tag":66,"props":251,"children":252},{},[253],{"type":48,"value":254},"Full doc:",{"type":48,"value":256}," ",{"type":43,"tag":258,"props":259,"children":260},"span",{},[261],{"type":48,"value":262},"link",{"type":48,"value":264}," · New to this channel? Read ",{"type":43,"tag":57,"props":266,"children":268},{"className":267},[],[269],{"type":48,"value":270},"ONBOARD.md",{"type":48,"value":272}," — how to\nread a diagnosis, challenge one, or silence a routine.",{"type":43,"tag":51,"props":274,"children":275},{},[276,278,283,285,290,292,297],{"type":48,"value":277},"The full doc, per incident: ",{"type":43,"tag":66,"props":279,"children":280},{},[281],{"type":48,"value":282},"what happened",{"type":48,"value":284}," (one fresh-reader sentence,\nlinks) · ",{"type":43,"tag":66,"props":286,"children":287},{},[288],{"type":48,"value":289},"what it means",{"type":48,"value":291}," (pattern or one-off? systemic risk?) · ",{"type":43,"tag":66,"props":293,"children":294},{},[295],{"type":48,"value":296},"what you\nshould do",{"type":48,"value":298}," (nothing \u002F monitor \u002F action, with the action named).",{"type":43,"tag":51,"props":300,"children":301},{},[302],{"type":48,"value":303},"Then: open items ranked by \"will this page you?\", not by age. Preventable\nrepeats called out as playbook gaps with proposed reference-file amendments\n(rule 9 — fix the playbook, not just the incident).",{"type":43,"tag":74,"props":305,"children":307},{"id":306},"drift-check-required-section",[308],{"type":48,"value":309},"Drift check (required section)",{"type":43,"tag":51,"props":311,"children":312},{},[313],{"type":48,"value":314},"The ground moves between incidents; this is where the kit notices. Each\nweek, flag:",{"type":43,"tag":94,"props":316,"children":317},{},[318,330,335,348,353],{"type":43,"tag":98,"props":319,"children":320},{},[321,323,328],{"type":48,"value":322},"any ",{"type":43,"tag":57,"props":324,"children":326},{"className":325},[],[327],{"type":48,"value":90},{"type":48,"value":329}," binding that failed or 403'd during the week's work",{"type":43,"tag":98,"props":331,"children":332},{},[333],{"type":48,"value":334},"any reference file whose first-checks cite a tool or query that no\nlonger responds",{"type":43,"tag":98,"props":336,"children":337},{},[338,340,346],{"type":48,"value":339},"anything in the ",{"type":43,"tag":57,"props":341,"children":343},{"className":342},[],[344],{"type":48,"value":345},"deploys",{"type":48,"value":347}," feed or announcement channels suggesting the\ninfrastructure changed under the playbooks — a migration completed, a\ntool replaced, a service renamed",{"type":43,"tag":98,"props":349,"children":350},{},[351],{"type":48,"value":352},"the routine registry vs. reality: does the \"Standing work\" canvas match\nthe channel's actual routines? Fix the registry; flag any routine that\nexists but was never registered",{"type":43,"tag":98,"props":354,"children":355},{},[356,358,362],{"type":48,"value":357},"open incidents with no update in >",{"type":43,"tag":194,"props":359,"children":361},{"value":360},"72h",[],{"type":48,"value":363}," — the zombie list, each with\nits three-leg staleness evidence per ONCALL.md's lifecycle section,\nframed as \"close it or update it\", never closed by Claude (rule 2)",{"type":43,"tag":51,"props":365,"children":366},{},[367],{"type":48,"value":368},"Each flag arrives as a proposal, never an edit (rule 9): \"re-run Discover\nfor this binding,\" a reference-file amendment PR, or \"re-run the replay\nagainst post-change incidents\" (see eval\u002Freplay.md's re-validation\ntriggers). A quiet week with no drift gets one line: \"no drift detected.\"",{"type":43,"tag":74,"props":370,"children":372},{"id":371},"discipline",[373],{"type":48,"value":374},"Discipline",{"type":43,"tag":94,"props":376,"children":377},{},[378,383,388],{"type":43,"tag":98,"props":379,"children":380},{},[381],{"type":48,"value":382},"\"Here's what happened\" without \"start here\" is a diary, not a handoff —\nthe priorities are the point.",{"type":43,"tag":98,"props":384,"children":385},{},[386],{"type":48,"value":387},"Never soften a preventable repeat. Write it plainly: \"2 auto-reverts,\nboth preventable.\"",{"type":43,"tag":98,"props":389,"children":390},{},[391],{"type":48,"value":392},"If the week was quiet, say so in two lines and stop. Padding a quiet week\nerodes trust in loud ones.",{"items":394,"total":578},[395,411,430,444,456,475,491,502,523,543,555,570],{"slug":396,"name":396,"fn":397,"description":398,"org":399,"tags":400,"stars":408,"repoUrl":409,"updatedAt":410},"academy-guide","recommend Claude Academy resources","Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: \"how do I\", \"how can I\", \"getting started with\", \"what can Claude do\", \"teach me\", \"learn to use\"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[401,402,405],{"name":9,"slug":8,"type":16},{"name":403,"slug":404,"type":16},"Documentation","documentation",{"name":406,"slug":407,"type":16},"Education","education",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-08-19T03:59:01.021254",{"slug":412,"name":412,"fn":413,"description":414,"org":415,"tags":416,"stars":408,"repoUrl":409,"updatedAt":429},"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},[417,420,423,426],{"name":418,"slug":419,"type":16},"Creative","creative",{"name":421,"slug":422,"type":16},"Design","design",{"name":424,"slug":425,"type":16},"Generative Art","generative-art",{"name":427,"slug":428,"type":16},"JavaScript","javascript","2026-04-06T17:56:15.455818",{"slug":431,"name":431,"fn":432,"description":433,"org":434,"tags":435,"stars":408,"repoUrl":409,"updatedAt":443},"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},[436,439,440],{"name":437,"slug":438,"type":16},"Branding","branding",{"name":421,"slug":422,"type":16},{"name":441,"slug":442,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":445,"name":445,"fn":446,"description":447,"org":448,"tags":449,"stars":408,"repoUrl":409,"updatedAt":455},"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},[450,451,452],{"name":418,"slug":419,"type":16},{"name":421,"slug":422,"type":16},{"name":453,"slug":454,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":457,"name":457,"fn":458,"description":459,"org":460,"tags":461,"stars":408,"repoUrl":409,"updatedAt":474},"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},[462,465,466,469,471],{"name":463,"slug":464,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":467,"slug":468,"type":16},"Anthropic SDK","anthropic-sdk",{"name":470,"slug":457,"type":16},"Claude API",{"name":472,"slug":473,"type":16},"LLM","llm","2026-08-16T03:33:37.191126",{"slug":476,"name":476,"fn":477,"description":478,"org":479,"tags":480,"stars":408,"repoUrl":409,"updatedAt":490},"discernment-nudge","provide discernment nudges for user decisions","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[481,484,487],{"name":482,"slug":483,"type":16},"Coaching","coaching",{"name":485,"slug":486,"type":16},"Productivity","productivity",{"name":488,"slug":489,"type":16},"Strategy","strategy","2026-08-19T03:59:01.539281",{"slug":492,"name":492,"fn":493,"description":494,"org":495,"tags":496,"stars":408,"repoUrl":409,"updatedAt":501},"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},[497,498],{"name":403,"slug":404,"type":16},{"name":499,"slug":500,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":503,"name":503,"fn":504,"description":505,"org":506,"tags":507,"stars":408,"repoUrl":409,"updatedAt":522},"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},[508,511,513,516,519],{"name":509,"slug":510,"type":16},"Documents","documents",{"name":512,"slug":503,"type":16},"DOCX",{"name":514,"slug":515,"type":16},"Office","office",{"name":517,"slug":518,"type":16},"Templates","templates",{"name":520,"slug":521,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":524,"name":524,"fn":525,"description":526,"org":527,"tags":528,"stars":408,"repoUrl":409,"updatedAt":542},"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},[529,530,533,536,539],{"name":421,"slug":422,"type":16},{"name":531,"slug":532,"type":16},"Frontend","frontend",{"name":534,"slug":535,"type":16},"React","react",{"name":537,"slug":538,"type":16},"Tailwind CSS","tailwind-css",{"name":540,"slug":541,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":544,"name":544,"fn":545,"description":546,"org":547,"tags":548,"stars":408,"repoUrl":409,"updatedAt":554},"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},[549,550,551],{"name":24,"slug":25,"type":16},{"name":517,"slug":518,"type":16},{"name":552,"slug":553,"type":16},"Writing","writing","2026-04-06T17:56:20.695522",{"slug":556,"name":556,"fn":557,"description":558,"org":559,"tags":560,"stars":408,"repoUrl":409,"updatedAt":569},"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},[561,562,565,566],{"name":463,"slug":464,"type":16},{"name":563,"slug":564,"type":16},"API Development","api-development",{"name":472,"slug":473,"type":16},{"name":567,"slug":568,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":454,"name":454,"fn":571,"description":572,"org":573,"tags":574,"stars":408,"repoUrl":409,"updatedAt":577},"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},[575,576],{"name":509,"slug":510,"type":16},{"name":453,"slug":454,"type":16},"2026-04-06T17:56:02.483316",493,{"items":580,"total":588},[581],{"slug":4,"name":4,"fn":5,"description":6,"org":582,"tags":583,"stars":26,"repoUrl":27,"updatedAt":28},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[584,585,586,587],{"name":24,"slug":25,"type":16},{"name":21,"slug":22,"type":16},{"name":14,"slug":15,"type":16},{"name":18,"slug":19,"type":16},1]