[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-procedure-coding":3,"mdc-o3qrxz-key":36,"related-repo-anthropic-procedure-coding":339,"related-org-anthropic-procedure-coding":444},{"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":34,"mdContent":35},"procedure-coding","assign CPT and HCPCS procedure codes","Assign CPT and HCPCS Level II procedure codes from clinical documentation the way a professional coder builds the claim. Use when users say \"code this encounter for procedures\", \"what CPT codes apply\", \"assign HCPCS codes\", \"code this op note\", or when turning visit notes or operative reports into claim-ready procedure codes.",{"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},"Compliance","compliance","tag",{"name":18,"slug":19,"type":16},"Healthcare","healthcare",{"name":21,"slug":22,"type":16},"Coding","coding",{"name":24,"slug":25,"type":16},"Medical Necessity","medical-necessity",356,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fhealthcare","2026-07-04T07:03:36.500522",null,91,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":29},[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fhealthcare\u002Ftree\u002FHEAD\u002Fplugins\u002Fhealthcare\u002Fskills\u002Fprocedure-coding","---\nname: procedure-coding\ndescription: Assign CPT and HCPCS Level II procedure codes from clinical documentation the way a professional coder builds the claim. Use when users say \"code this encounter for procedures\", \"what CPT codes apply\", \"assign HCPCS codes\", \"code this op note\", or when turning visit notes or operative reports into claim-ready procedure codes.\n---\n\n# Procedure Coding from Encounter Documentation\n\nTurn one encounter's clinical documentation into the procedure codes a professional coder would submit on the claim: CPT (five digits, or four digits + F for Category II tracking codes) for physician services, procedures, and quality measures, plus HCPCS Level II (letter + four digits) for supplies, devices, and non-physician services CPT does not cover.\n\n## Step 1 — Abstract every billable service from the note\n\nRead the documentation and list each distinct billable service performed at this encounter. Work by category:\n\n- **Evaluation and management** — the visit itself: office, emergency, observation, inpatient, consultation. One E\u002FM code per encounter unless a separately identifiable service is documented. When the visit is for ongoing management of a single serious or complex chronic condition, the complexity add-on may apply alongside the office E\u002FM code.\n- **Ancillary services that ride alongside the visit** — a blood draw for any lab is a separately billable venipuncture; each lab test ordered with a result in the note bills its own code; an ECG or pulse-ox performed in the visit is its own code; an injection, infusion, or IV push administered during the visit codes the administration plus an add-on for each additional sequential push or hour.\n- **Procedures and surgery** — anything with an incision, injection, scope, repair, or manipulation. Abstract from the procedure note, not the plan.\n- **Laboratory and pathology** — each ordered test that has a result in the note. Panels (CBC, BMP, CMP) bill as the panel code, not the components.\n- **Imaging** — each study by modality and body part, with the view\u002Fcontrast detail documented.\n- **Medicine services** — vaccinations administered, infusions, therapeutic injections, ECGs, pulmonary function, physical therapy.\n\nLeave off the list: services planned but not performed, results referenced from a prior date, and items already bundled into a procedure's global package.\n\n## HCPCS Level II — what to look for and what to leave off\n\nHCPCS Level II codes (one letter + four digits) cover items CPT does not. Check the documentation for these specifically:\n\n- **Hospital observation hours** — when the note shows the patient was placed in or remained in observation status, code the per-hour observation service (and the direct-referral code when the patient was placed in observation without a preceding ED visit).\n- **Devices and implants used during a facility procedure (C-codes)** — for any catheterization, endoscopy, interventional, or implant procedure, read the operative\u002Fprocedure narrative and the supply or implant log for each single-use device the operator names: guide wire, introducer or sheath, diagnostic or guiding catheter, lead, stent, closure or embolization device, balloon. Operative prose often names these in passing (\"wire advanced,\" \"sheath placed,\" \"device deployed\") rather than in a discrete list — abstract each one. Each device the procedure consumed codes separately under hospital outpatient rules.\n- **Drugs administered in the facility (C-codes)** — certain injectable drugs given during a hospital outpatient encounter carry their own pass-through code. Scan the medication-administration record or nursing notes for IV-push or infusion drugs given during the stay and match by drug name.\n- **Specimen collection performed by facility staff** — a documented swab or draw billed by the facility separately from the lab test.\n- **Supplies dispensed** (A-codes) — sterile saline, dressings, trays, ostomy supplies, when the note or supply record names the specific item.\n- **High-throughput infectious-disease lab tests** (U-codes) — when the lab order or result names the specific assay platform.\n- **Medicare preventive and screening services** (G0-codes) — annual wellness visit, advance-care-planning, depression or alcohol screening, diabetes prevention. Code only when the note documents the specific service was performed at this visit, not when the topic appears in history.\n\n**Do not output quality-reporting G-codes (G8-\u002FG9- range) or non-covered-item codes.** These report participation in a quality program or a coverage determination; whether they belong on the claim depends on the practice's program enrollment and the payer, not on the clinical documentation. A data point appearing in the note (BMI in vitals, medication list reviewed, tobacco status in social history) is not by itself a reason to report the corresponding quality code.\n\n## CPT Category II (####F) — same rule as quality G-codes\n\nCategory II tracking codes are reported when the encounter is part of a quality-reporting workflow, not whenever the data point happens to appear in routine vitals or history. Output a ####F code only when the note shows the measure was deliberately captured for reporting: a quality-measure or health-maintenance section, measure-specific attestation language, or a structured screening result.\n\n## Step 2 — Find each code with the lookup tools\n\nFor every item on your abstracted list, search before you commit.\n\n**HCPCS Level II (letter + four digits):** use `search_codes` for the supply, device, drug, or service name, passing the encounter date as `as_of`. Confirm with `validate_code` and the same `as_of`.\n\n**CPT (five-digit and ####F):** if a CPT lookup connector is available (`cpt_search_codes`), use it with the service in plain words taken from the note and confirm with `cpt_lookup_code`. If no CPT connector is available, propose CPT codes from your knowledge of the current code set and state that they are pending verification against the user's licensed CPT reference — CPT descriptors are AMA-licensed and not bundled with this skill.\n\nOne or two searches per item is sufficient. If the right code is not in the first results, refine the query once with more specific wording from the note; then commit or move on. Do not loop on the same item.\n\n## Step 3 — Output\n\nAfter tool calls, output only the codes that belong on the claim, one per line, no other text. List each code once. Do not output J#### or Q#### codes. If a service you abstracted has no matching code in the lookup results and you cannot confidently propose one, omit it rather than guessing.\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,50,56,63,68,134,139,145,150,223,233,239,244,250,255,297,323,328,334],{"type":42,"tag":43,"props":44,"children":46},"element","h1",{"id":45},"procedure-coding-from-encounter-documentation",[47],{"type":48,"value":49},"text","Procedure Coding from Encounter Documentation",{"type":42,"tag":51,"props":52,"children":53},"p",{},[54],{"type":48,"value":55},"Turn one encounter's clinical documentation into the procedure codes a professional coder would submit on the claim: CPT (five digits, or four digits + F for Category II tracking codes) for physician services, procedures, and quality measures, plus HCPCS Level II (letter + four digits) for supplies, devices, and non-physician services CPT does not cover.",{"type":42,"tag":57,"props":58,"children":60},"h2",{"id":59},"step-1-abstract-every-billable-service-from-the-note",[61],{"type":48,"value":62},"Step 1 — Abstract every billable service from the note",{"type":42,"tag":51,"props":64,"children":65},{},[66],{"type":48,"value":67},"Read the documentation and list each distinct billable service performed at this encounter. Work by category:",{"type":42,"tag":69,"props":70,"children":71},"ul",{},[72,84,94,104,114,124],{"type":42,"tag":73,"props":74,"children":75},"li",{},[76,82],{"type":42,"tag":77,"props":78,"children":79},"strong",{},[80],{"type":48,"value":81},"Evaluation and management",{"type":48,"value":83}," — the visit itself: office, emergency, observation, inpatient, consultation. One E\u002FM code per encounter unless a separately identifiable service is documented. When the visit is for ongoing management of a single serious or complex chronic condition, the complexity add-on may apply alongside the office E\u002FM code.",{"type":42,"tag":73,"props":85,"children":86},{},[87,92],{"type":42,"tag":77,"props":88,"children":89},{},[90],{"type":48,"value":91},"Ancillary services that ride alongside the visit",{"type":48,"value":93}," — a blood draw for any lab is a separately billable venipuncture; each lab test ordered with a result in the note bills its own code; an ECG or pulse-ox performed in the visit is its own code; an injection, infusion, or IV push administered during the visit codes the administration plus an add-on for each additional sequential push or hour.",{"type":42,"tag":73,"props":95,"children":96},{},[97,102],{"type":42,"tag":77,"props":98,"children":99},{},[100],{"type":48,"value":101},"Procedures and surgery",{"type":48,"value":103}," — anything with an incision, injection, scope, repair, or manipulation. Abstract from the procedure note, not the plan.",{"type":42,"tag":73,"props":105,"children":106},{},[107,112],{"type":42,"tag":77,"props":108,"children":109},{},[110],{"type":48,"value":111},"Laboratory and pathology",{"type":48,"value":113}," — each ordered test that has a result in the note. Panels (CBC, BMP, CMP) bill as the panel code, not the components.",{"type":42,"tag":73,"props":115,"children":116},{},[117,122],{"type":42,"tag":77,"props":118,"children":119},{},[120],{"type":48,"value":121},"Imaging",{"type":48,"value":123}," — each study by modality and body part, with the view\u002Fcontrast detail documented.",{"type":42,"tag":73,"props":125,"children":126},{},[127,132],{"type":42,"tag":77,"props":128,"children":129},{},[130],{"type":48,"value":131},"Medicine services",{"type":48,"value":133}," — vaccinations administered, infusions, therapeutic injections, ECGs, pulmonary function, physical therapy.",{"type":42,"tag":51,"props":135,"children":136},{},[137],{"type":48,"value":138},"Leave off the list: services planned but not performed, results referenced from a prior date, and items already bundled into a procedure's global package.",{"type":42,"tag":57,"props":140,"children":142},{"id":141},"hcpcs-level-ii-what-to-look-for-and-what-to-leave-off",[143],{"type":48,"value":144},"HCPCS Level II — what to look for and what to leave off",{"type":42,"tag":51,"props":146,"children":147},{},[148],{"type":48,"value":149},"HCPCS Level II codes (one letter + four digits) cover items CPT does not. Check the documentation for these specifically:",{"type":42,"tag":69,"props":151,"children":152},{},[153,163,173,183,193,203,213],{"type":42,"tag":73,"props":154,"children":155},{},[156,161],{"type":42,"tag":77,"props":157,"children":158},{},[159],{"type":48,"value":160},"Hospital observation hours",{"type":48,"value":162}," — when the note shows the patient was placed in or remained in observation status, code the per-hour observation service (and the direct-referral code when the patient was placed in observation without a preceding ED visit).",{"type":42,"tag":73,"props":164,"children":165},{},[166,171],{"type":42,"tag":77,"props":167,"children":168},{},[169],{"type":48,"value":170},"Devices and implants used during a facility procedure (C-codes)",{"type":48,"value":172}," — for any catheterization, endoscopy, interventional, or implant procedure, read the operative\u002Fprocedure narrative and the supply or implant log for each single-use device the operator names: guide wire, introducer or sheath, diagnostic or guiding catheter, lead, stent, closure or embolization device, balloon. Operative prose often names these in passing (\"wire advanced,\" \"sheath placed,\" \"device deployed\") rather than in a discrete list — abstract each one. Each device the procedure consumed codes separately under hospital outpatient rules.",{"type":42,"tag":73,"props":174,"children":175},{},[176,181],{"type":42,"tag":77,"props":177,"children":178},{},[179],{"type":48,"value":180},"Drugs administered in the facility (C-codes)",{"type":48,"value":182}," — certain injectable drugs given during a hospital outpatient encounter carry their own pass-through code. Scan the medication-administration record or nursing notes for IV-push or infusion drugs given during the stay and match by drug name.",{"type":42,"tag":73,"props":184,"children":185},{},[186,191],{"type":42,"tag":77,"props":187,"children":188},{},[189],{"type":48,"value":190},"Specimen collection performed by facility staff",{"type":48,"value":192}," — a documented swab or draw billed by the facility separately from the lab test.",{"type":42,"tag":73,"props":194,"children":195},{},[196,201],{"type":42,"tag":77,"props":197,"children":198},{},[199],{"type":48,"value":200},"Supplies dispensed",{"type":48,"value":202}," (A-codes) — sterile saline, dressings, trays, ostomy supplies, when the note or supply record names the specific item.",{"type":42,"tag":73,"props":204,"children":205},{},[206,211],{"type":42,"tag":77,"props":207,"children":208},{},[209],{"type":48,"value":210},"High-throughput infectious-disease lab tests",{"type":48,"value":212}," (U-codes) — when the lab order or result names the specific assay platform.",{"type":42,"tag":73,"props":214,"children":215},{},[216,221],{"type":42,"tag":77,"props":217,"children":218},{},[219],{"type":48,"value":220},"Medicare preventive and screening services",{"type":48,"value":222}," (G0-codes) — annual wellness visit, advance-care-planning, depression or alcohol screening, diabetes prevention. Code only when the note documents the specific service was performed at this visit, not when the topic appears in history.",{"type":42,"tag":51,"props":224,"children":225},{},[226,231],{"type":42,"tag":77,"props":227,"children":228},{},[229],{"type":48,"value":230},"Do not output quality-reporting G-codes (G8-\u002FG9- range) or non-covered-item codes.",{"type":48,"value":232}," These report participation in a quality program or a coverage determination; whether they belong on the claim depends on the practice's program enrollment and the payer, not on the clinical documentation. A data point appearing in the note (BMI in vitals, medication list reviewed, tobacco status in social history) is not by itself a reason to report the corresponding quality code.",{"type":42,"tag":57,"props":234,"children":236},{"id":235},"cpt-category-ii-f-same-rule-as-quality-g-codes",[237],{"type":48,"value":238},"CPT Category II (####F) — same rule as quality G-codes",{"type":42,"tag":51,"props":240,"children":241},{},[242],{"type":48,"value":243},"Category II tracking codes are reported when the encounter is part of a quality-reporting workflow, not whenever the data point happens to appear in routine vitals or history. Output a ####F code only when the note shows the measure was deliberately captured for reporting: a quality-measure or health-maintenance section, measure-specific attestation language, or a structured screening result.",{"type":42,"tag":57,"props":245,"children":247},{"id":246},"step-2-find-each-code-with-the-lookup-tools",[248],{"type":48,"value":249},"Step 2 — Find each code with the lookup tools",{"type":42,"tag":51,"props":251,"children":252},{},[253],{"type":48,"value":254},"For every item on your abstracted list, search before you commit.",{"type":42,"tag":51,"props":256,"children":257},{},[258,263,265,272,274,280,282,288,290,295],{"type":42,"tag":77,"props":259,"children":260},{},[261],{"type":48,"value":262},"HCPCS Level II (letter + four digits):",{"type":48,"value":264}," use ",{"type":42,"tag":266,"props":267,"children":269},"code",{"className":268},[],[270],{"type":48,"value":271},"search_codes",{"type":48,"value":273}," for the supply, device, drug, or service name, passing the encounter date as ",{"type":42,"tag":266,"props":275,"children":277},{"className":276},[],[278],{"type":48,"value":279},"as_of",{"type":48,"value":281},". Confirm with ",{"type":42,"tag":266,"props":283,"children":285},{"className":284},[],[286],{"type":48,"value":287},"validate_code",{"type":48,"value":289}," and the same ",{"type":42,"tag":266,"props":291,"children":293},{"className":292},[],[294],{"type":48,"value":279},{"type":48,"value":296},".",{"type":42,"tag":51,"props":298,"children":299},{},[300,305,307,313,315,321],{"type":42,"tag":77,"props":301,"children":302},{},[303],{"type":48,"value":304},"CPT (five-digit and ####F):",{"type":48,"value":306}," if a CPT lookup connector is available (",{"type":42,"tag":266,"props":308,"children":310},{"className":309},[],[311],{"type":48,"value":312},"cpt_search_codes",{"type":48,"value":314},"), use it with the service in plain words taken from the note and confirm with ",{"type":42,"tag":266,"props":316,"children":318},{"className":317},[],[319],{"type":48,"value":320},"cpt_lookup_code",{"type":48,"value":322},". If no CPT connector is available, propose CPT codes from your knowledge of the current code set and state that they are pending verification against the user's licensed CPT reference — CPT descriptors are AMA-licensed and not bundled with this skill.",{"type":42,"tag":51,"props":324,"children":325},{},[326],{"type":48,"value":327},"One or two searches per item is sufficient. If the right code is not in the first results, refine the query once with more specific wording from the note; then commit or move on. Do not loop on the same item.",{"type":42,"tag":57,"props":329,"children":331},{"id":330},"step-3-output",[332],{"type":48,"value":333},"Step 3 — Output",{"type":42,"tag":51,"props":335,"children":336},{},[337],{"type":48,"value":338},"After tool calls, output only the codes that belong on the claim, one per line, no other text. List each code once. Do not output J#### or Q#### codes. If a service you abstracted has no matching code in the lookup results and you cannot confidently propose one, omit it rather than guessing.",{"items":340,"total":443},[341,352,370,390,406,417,432],{"slug":342,"name":342,"fn":343,"description":344,"org":345,"tags":346,"stars":26,"repoUrl":27,"updatedAt":351},"clinical-note-extract-skill","extract structured data from clinical notes","Extract structured data from clinical notes with span-level provenance and null-safety. Use when users say \"extract [variables] from this note\", \"abstract this chart\", \"pull structured data from these notes\", \"what does this note say about [field]\", or when building a chart-abstraction, registry, or cohort dataset from unstructured clinical text.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[347,350],{"name":348,"slug":349,"type":16},"Data Analysis","data-analysis",{"name":18,"slug":19,"type":16},"2026-06-28T07:57:18.332447",{"slug":353,"name":353,"fn":354,"description":355,"org":356,"tags":357,"stars":26,"repoUrl":27,"updatedAt":369},"contracts","analyze contract documents with citations","Answer a question across a corpus of contract documents with verified citations. Use when the user asks what a contract says, which contracts have a clause, what changed between amendments, or any question that needs reading and citing across a set of contract files. The corpus must be on the local filesystem (see README).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[358,360,363,366],{"name":359,"slug":353,"type":16},"Contracts",{"name":361,"slug":362,"type":16},"Documents","documents",{"name":364,"slug":365,"type":16},"Legal","legal",{"name":367,"slug":368,"type":16},"Research","research","2026-07-18T05:15:17.073689",{"slug":371,"name":371,"fn":372,"description":373,"org":374,"tags":375,"stars":26,"repoUrl":27,"updatedAt":389},"doc-extract","extract text from documents","Extract plain text from a document file - PDF, DOCX, XLSX, PPTX, RTF, or plain text\u002Fmarkdown\u002FHTML. Use when a binary document needs to be turned into text, for example a contract PDF or an EHR DocumentReference attachment. Other skills (fhir) invoke scripts\u002Fextract.ts directly; the contracts MCP server bundles its own copy (servers\u002Fdocuments\u002Fsrc\u002Fextract.mjs) so its bundle stays self-contained — port fixes to both.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[376,379,380,383,386],{"name":377,"slug":378,"type":16},"Data Cleaning","data-cleaning",{"name":361,"slug":362,"type":16},{"name":381,"slug":382,"type":16},"DOCX","docx",{"name":384,"slug":385,"type":16},"PDF","pdf",{"name":387,"slug":388,"type":16},"Spreadsheets","spreadsheets","2026-07-18T05:15:15.766116",{"slug":391,"name":391,"fn":392,"description":393,"org":394,"tags":395,"stars":26,"repoUrl":27,"updatedAt":405},"fhir","extract clinical data from FHIR servers","Connect to a hospital's FHIR R4 server (Epic, Oracle Health\u002FCerner, MEDITECH, athenahealth, or any SMART-on-FHIR endpoint), pull a patient's clinical data and notes, and extract structured findings. Use when users say \"connect to the EHR\", \"connect to Epic\u002FCerner\", \"pull notes for patient X\", \"what do the last 6 months of notes say about Y\", or any task that starts from a live EHR rather than pasted text.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[396,399,401,402],{"name":397,"slug":398,"type":16},"API Development","api-development",{"name":400,"slug":391,"type":16},"FHIR",{"name":18,"slug":19,"type":16},{"name":403,"slug":404,"type":16},"Interoperability","interoperability","2026-07-03T16:28:01.476883",{"slug":407,"name":407,"fn":408,"description":409,"org":410,"tags":411,"stars":26,"repoUrl":27,"updatedAt":416},"fhir-developer-skill","build FHIR REST healthcare endpoints","FHIR API development guide for building healthcare endpoints. Use when: (1) Creating FHIR REST endpoints (Patient, Observation, Encounter, Condition, MedicationRequest), (2) Validating FHIR resources and returning proper HTTP status codes and error responses, (3) Implementing SMART on FHIR authorization and OAuth scopes, (4) Working with Bundles, transactions, batch operations, or search pagination. Covers FHIR R4 resource structures, required fields, value sets (status codes, gender, intent), coding systems (LOINC, SNOMED, RxNorm, ICD-10), and OperationOutcome error handling.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[412,413,414,415],{"name":397,"slug":398,"type":16},{"name":400,"slug":391,"type":16},{"name":18,"slug":19,"type":16},{"name":403,"slug":404,"type":16},"2026-06-16T09:39:06.471928",{"slug":418,"name":418,"fn":419,"description":420,"org":421,"tags":422,"stars":26,"repoUrl":27,"updatedAt":431},"fraud-detection","detect fraud in healthcare claims","Screen a Medicare\u002FMedicaid claims corpus for fraud, waste, and abuse and produce ranked, fully-cited investigation referrals for an SIU \u002F program-integrity team. Use when asked to run a fraud sweep, screen claims for FWA, find billing anomalies, or generate investigation referrals over a claims dataset.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[423,426,427,428],{"name":424,"slug":425,"type":16},"Audit","audit",{"name":14,"slug":15,"type":16},{"name":18,"slug":19,"type":16},{"name":429,"slug":430,"type":16},"Insurance","insurance","2026-06-26T07:50:49.129616",{"slug":433,"name":433,"fn":434,"description":435,"org":436,"tags":437,"stars":26,"repoUrl":27,"updatedAt":442},"icd10-cm-skill","extract ICD-10-CM diagnosis codes","Extract billable ICD-10-CM diagnosis codes from a clinical note the way a professional coder builds the claim. Use when users say \"code this encounter\", \"assign ICD-10 codes\", \"what diagnosis codes apply\", \"code this chart\", or when turning clinical documentation into claim-ready diagnosis codes.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[438,439,440,441],{"name":21,"slug":22,"type":16},{"name":18,"slug":19,"type":16},{"name":429,"slug":430,"type":16},{"name":24,"slug":25,"type":16},"2026-06-19T09:34:31.578353",9,{"items":445,"total":624},[446,467,481,491,510,523,540,560,574,587,595,608],{"slug":447,"name":447,"fn":448,"description":449,"org":450,"tags":451,"stars":464,"repoUrl":465,"updatedAt":466},"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},[452,455,458,461],{"name":453,"slug":454,"type":16},"Creative","creative",{"name":456,"slug":457,"type":16},"Design","design",{"name":459,"slug":460,"type":16},"Generative Art","generative-art",{"name":462,"slug":463,"type":16},"JavaScript","javascript",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-04-06T17:56:15.455818",{"slug":468,"name":468,"fn":469,"description":470,"org":471,"tags":472,"stars":464,"repoUrl":465,"updatedAt":480},"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},[473,476,477],{"name":474,"slug":475,"type":16},"Branding","branding",{"name":456,"slug":457,"type":16},{"name":478,"slug":479,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":482,"name":482,"fn":483,"description":484,"org":485,"tags":486,"stars":464,"repoUrl":465,"updatedAt":490},"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},[487,488,489],{"name":453,"slug":454,"type":16},{"name":456,"slug":457,"type":16},{"name":384,"slug":385,"type":16},"2026-04-06T17:56:03.794732",{"slug":492,"name":492,"fn":493,"description":494,"org":495,"tags":496,"stars":464,"repoUrl":465,"updatedAt":509},"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},[497,500,501,504,506],{"name":498,"slug":499,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":502,"slug":503,"type":16},"Anthropic SDK","anthropic-sdk",{"name":505,"slug":492,"type":16},"Claude API",{"name":507,"slug":508,"type":16},"LLM","llm","2026-07-28T05:36:08.213335",{"slug":511,"name":511,"fn":512,"description":513,"org":514,"tags":515,"stars":464,"repoUrl":465,"updatedAt":522},"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},[516,519],{"name":517,"slug":518,"type":16},"Documentation","documentation",{"name":520,"slug":521,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":382,"name":382,"fn":524,"description":525,"org":526,"tags":527,"stars":464,"repoUrl":465,"updatedAt":539},"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},[528,529,530,533,536],{"name":361,"slug":362,"type":16},{"name":381,"slug":382,"type":16},{"name":531,"slug":532,"type":16},"Office","office",{"name":534,"slug":535,"type":16},"Templates","templates",{"name":537,"slug":538,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":541,"name":541,"fn":542,"description":543,"org":544,"tags":545,"stars":464,"repoUrl":465,"updatedAt":559},"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},[546,547,550,553,556],{"name":456,"slug":457,"type":16},{"name":548,"slug":549,"type":16},"Frontend","frontend",{"name":551,"slug":552,"type":16},"React","react",{"name":554,"slug":555,"type":16},"Tailwind CSS","tailwind-css",{"name":557,"slug":558,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":561,"name":561,"fn":562,"description":563,"org":564,"tags":565,"stars":464,"repoUrl":465,"updatedAt":573},"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},[566,569,570],{"name":567,"slug":568,"type":16},"Communications","communications",{"name":534,"slug":535,"type":16},{"name":571,"slug":572,"type":16},"Writing","writing","2026-04-06T17:56:20.695522",{"slug":575,"name":575,"fn":576,"description":577,"org":578,"tags":579,"stars":464,"repoUrl":465,"updatedAt":586},"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},[580,581,582,583],{"name":498,"slug":499,"type":16},{"name":397,"slug":398,"type":16},{"name":507,"slug":508,"type":16},{"name":584,"slug":585,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":385,"name":385,"fn":588,"description":589,"org":590,"tags":591,"stars":464,"repoUrl":465,"updatedAt":594},"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},[592,593],{"name":361,"slug":362,"type":16},{"name":384,"slug":385,"type":16},"2026-04-06T17:56:02.483316",{"slug":596,"name":596,"fn":597,"description":598,"org":599,"tags":600,"stars":464,"repoUrl":465,"updatedAt":607},"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},[601,604],{"name":602,"slug":603,"type":16},"PowerPoint","powerpoint",{"name":605,"slug":606,"type":16},"Presentations","presentations","2026-07-18T05:16:24.1471",{"slug":609,"name":609,"fn":610,"description":611,"org":612,"tags":613,"stars":464,"repoUrl":465,"updatedAt":623},"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},[614,615,616,619,622],{"name":498,"slug":499,"type":16},{"name":517,"slug":518,"type":16},{"name":617,"slug":618,"type":16},"Evals","evals",{"name":620,"slug":621,"type":16},"Performance","performance",{"name":520,"slug":521,"type":16},"2026-04-19T06:45:40.804",490]