all publishers

anthropics

@anthropics source repo

145 published skills · page 1 of 2

  1. ▌
    Wrap Up 2 · anthropics
    Close out (or revisit) a Claude Managed Agent build — refresh the overview page, recap every primitive the founder now owns, show the run log and live status, suggest 1–2 tailored next upgrades, and sweep hygiene (sessions archived, key only in .env, no literal dates in deployment kickoffs). Use when the founder says "/wrap-up", "wrap up", "close it out", "where do things stand with my agent", or at the end of a /launch-your-agent build.
    195k repo stars
  2. ▌
    Launch Your Agent 2 · anthropics bundle
    <!-- Copyright 2026 Anthropic PBC -->
    195k repo stars
  3. ▌
    Verify 5 · anthropics
    Drive this repo's build/release scripts end-to-end without touching the network. Use when verifying changes to scripts/download_cli.py, scripts/build_wheel.py, scripts/update_cli_version.py, or scripts/_cli_version_validation.py.
    195k repo stars
  4. ▌
    Chat Sdk 2 · anthropics bundle
    Setup tips & tricks: Chat SDK web adapter × Claude Managed Agents
    195k repo stars
  5. ▌
    Assistant UI 2 · anthropics bundle
    Setup tips and tricks: assistant-ui × Claude Managed Agents
    195k repo stars
  6. ▌
    Knowledge Wiki 2 · anthropics bundle
    Setting up the knowledge-wiki quickstart
    195k repo stars
  7. ▌
    Verify 3 · anthropics
    Build the computer-use-demo image and drive the Streamlit UI headlessly to verify changes end-to-end.
    195k repo stars
  8. ▌
    First Run 2 · anthropics
    Guide a new user through their first computer-use agent run (env check, safe browser-only task, then open the trajectory viewer).
    195k repo stars
  9. ▌
    Verify 4 · anthropics
    Build and drive the copilot-kit-ag-ui demo to verify changes end-to-end.
    195k repo stars
  10. ▌
    Verify 2 · anthropics
    Build and drive the copilot-kit-ag-ui demo to verify changes end-to-end.
    195k repo stars
  11. ▌
    Single Cell Rna Qc · anthropics bundle
    Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive visualizations. Use when users request QC analysis, filtering low-quality cells, assessing data quality, or following scverse/scanpy best practices for single-cell analysis.
    195k repo stars
  12. ▌
    Code Migration · anthropics
    Run a large-scale language migration with the six-step process: create the map and the rules, stress-test the rules, translate everything, compile, run it, match behavior. Use when the user wants to migrate, port, or rewrite a codebase from one language to another ("migrate this to Rust", "port our Python CLI to TypeScript", "should we rewrite this in Go?"), or asks for a migration feasibility assessment. Not for incremental JS→TS adoption — that needs no machinery — or single-file conversions.
    195k repo stars
  13. ▌
    K12 Lesson Prep · anthropics bundle
    Helps a teacher prepare to teach an existing K-12 lesson (math / ELA / science / social studies) — a prep partner that thinks through the lesson's key student task with the teacher and leaves a short teacher-only prep note. Triggers on asks to internalize, prepare for, get ready to teach, or understand a lesson, including implicit ones ("help me get ready for tomorrow's lesson"), and right after another skill built a lesson, which it can follow. Not for building or adapting a lesson, grading, rubrics, assessment feedback, or generating quizzes or student-facing material, and not for single-fact lookups a sentence would answer ("what standard is this?", "how long is this lesson?").
    195k repo stars
  14. ▌
    K12 Lesson Plan Creation · anthropics bundle
    Creates a lesson plan, student-facing materials, and observation template. Load this skill BEFORE asking the teacher any clarifying question about grade, subject, topic, standard, or timing. Use when a K-12 teacher needs a math, ELA, science, or social studies lesson built from scratch — even if grade, subject, or topic isn't yet stated. Do NOT load for grading, a rubric, assessment feedback, a quiz, or a standards lookup — answer those directly. Triggers on explicit requests (lesson plan, mini-lesson, unit plan, daily plan) and implicit teacher intent: "I'm teaching long division to 5th graders," "need to teach photosynthesis tomorrow." Core signal: teacher needs new instructional content created. A new lesson that asks for differentiated, tiered, or leveled materials is still ONE planning request — this skill produces those materials inside the lesson package; do not also invoke k12-lesson-differentiation. Not for differentiating an existing lesson (use k12-lesson-differentiation) or passage rewrites.
    195k repo stars
  15. ▌
    K12 Lesson Differentiation · anthropics bundle
    Adapts an existing K-12 lesson (math, ELA, science, or social studies) for students at different proficiency levels (below / at / above grade level). Load this skill BEFORE asking the teacher any clarifying question about the lesson, tiers, or student levels. Triggers on explicit asks to differentiate, tier, or scaffold a lesson, and on implicit signals like "my students are at different levels". Produces 1 teacher-facing differentiation plan + 3 student-ready tier documents as editable Word documents in a single output turn, rendered from one material-source JSON via bundled scripts (shared content is written once so tiers cannot drift). Uses the Learning Commons Knowledge Graph when connected; works without it. This skill adapts a lesson the teacher brings or names. Not for creating a new lesson from scratch — a new-lesson request that asks for differentiated or leveled materials is k12-lesson-plan-creation's job, one package. Not for grading, rubrics, assessment feedback, or quizzes.
    195k repo stars
  16. ▌
    K12 Check For Understanding · anthropics bundle
    Creates a Check for Understanding (CFU) for a math topic or standard: 1–3 targeted formative items whose distractors come from documented student misconceptions, plus a teacher guide routing each likely response to a specific next instructional step. Load BEFORE asking any clarifying question about grade, standard, or topic. This skill is for math; for other subjects, help as you normally would and don't mention the skill to the user. Triggers on asks to create, write, generate, or design a check for understanding, formative check, quick check, or exit ticket for a math concept or standard, and on implicit signals like "I need to see who got it before I move on." Not a quiz, test, or practice set — a CFU is read for what it reveals, not scored, so a numbered quiz or a bare answer key is a different job. Does not create a lesson (k12-lesson-plan-creation, which brings its own exit ticket), tier one (k12-lesson-differentiation), or prepare a teacher to teach one (k12-lesson-prep).
    195k repo stars
  17. ▌
    Slack · anthropics bundle
    Setup tips & tricks — Slack × CMA webhook bridge
    195k repo stars
  18. ▌
    Linear · anthropics bundle
    Setup tips & tricks — Linear × CMA webhook bridge
    195k repo stars
  19. ▌
    Sentry · anthropics bundle
    Setup tips & tricks: scheduled Sentry triage with vault env-var credentials
    195k repo stars
  20. ▌
    Cma MCP · anthropics bundle
    Setup tips & tricks — CMA as an MCP server
    195k repo stars
  21. ▌
    Roadtrip Planner · anthropics bundle
    Setup walkthrough
    195k repo stars
  22. ▌
    Chat Sdk · anthropics bundle
    Setup tips & tricks: Chat SDK web adapter × Claude Managed Agents
    195k repo stars
  23. ▌
    Assistant UI · anthropics bundle
    Setup tips and tricks: assistant-ui × Claude Managed Agents
    195k repo stars
  24. ▌
    Knowledge Wiki · anthropics bundle
    Setting up the knowledge-wiki quickstart
    195k repo stars
  25. ▌
    Mining · anthropics
    Where diamonds spawn in Minecraft 1.20.
    195k repo stars
  26. ▌
    Edgartools Sec Data · anthropics
    How to pull SEC EDGAR data with the edgartools Python package — company lookup, filings, XBRL financial statements, and filing sections like Item 1A risk factors. Use whenever a task involves SEC filings, 10-K/10-Q data, or company financials.
    195k repo stars
  27. ▌
    Workshop · anthropics
    Workshop coach for the Research Desk (SEC agents) workshop. Use when the user types /workshop, asks for a workshop act or module ("act 2", "next act", "where am I"), wants a TODO(workshop-N) implemented or explained, or asks for help following WORKSHOP.md.
    195k repo stars
  28. ▌
    Forecasting · anthropics bundle
    How to produce a demand forecast for a SKU, and when to delegate that to a subagent vs. compute it yourself. Load this for any task involving "forecast", "how much will we sell", "next month", promos, or seasonal SKUs.
    195k repo stars
  29. ▌
    Eval Audit And Sweep · anthropics bundle
    <!-- Copyright 2026 Anthropic PBC -->
    195k repo stars
  30. ▌
    Weekly Report · anthropics
    Structure and data sources for the weekly inventory report. Load this when the task is "weekly report", "Monday report", or "summarize inventory status".
    195k repo stars
  31. ▌
    Reorder Policy · anthropics
    How to decide whether and how much to reorder a SKU. Load this whenever a task involves reorder recommendations, purchase orders, or "should we restock" questions.
    195k repo stars
  32. ▌
    Submit Solution · anthropics
    Guide a workshop attendee through committing their starter-agent decomposition and opening a PR with their solution + workshop feedback. Invoke when the user says "submit", "I'm done", "open a PR", or asks how to share their solution.
    195k repo stars
  33. ▌
    Notify Templates · anthropics
    Fixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".
    195k repo stars
  34. ▌
    Supplier Selection · anthropics
    How to rank and pick a supplier for a SKU. Load this whenever a task involves choosing a supplier, comparing quotes, or creating a purchase order.
    195k repo stars
  35. ▌
    Incident Triage Runbook · anthropics
    The SRE team's runbook for triaging production latency and error-rate incidents. Use this whenever investigating an incident, a latency spike, elevated error rates, or when asked "what caused X" about a production service.
    195k repo stars
  36. ▌
    Customer Care · anthropics
    Help after a purchase or booking, covering the status of an order or delivery whether or not the customer names it, returns, refunds, exchanges, and cancellations, an item that arrived damaged, incomplete, or late, and questions about the store's terms or a membership. Not needed for finding, comparing, or choosing something new.
    195k repo stars
  37. ▌
    Planning Goals · anthropics
    Planning a coordinated set of items toward a goal, an event, a trip, or a project, where the request only comes together as several purchases with a structure between them, and later changes to a plan you have presented. Not needed when the customer wants a single item, however carefully chosen.
    195k repo stars
  38. ▌
    Catalog Listings · anthropics
    Creating and improving listing content, covering titles, descriptions, attribute completeness, categorization fixes, image callouts written as text, edits written from material the operator supplies, and content-quality audits and bulk fixes across many listings. Not needed for questions about how a listing is performing.
    195k repo stars
  39. ▌
    Search Discovery · anthropics
    Turning a described need (several constraints, a gift, a choice between candidates already in view, a search that came back empty or sold out) into a shortlist and a pick. Not needed when one search for the thing the customer named answers the request, or when the customer wants to learn what matters in a category first (purchase-research).
    195k repo stars
  40. ▌
    Purchase Research · anthropics
    Teaching a customer how to choose before any candidates appear, when they ask what matters in a category, how two approaches to it differ, or where to begin. Not needed once the customer has named the thing they want, however considered the purchase (that is search work), nor for outfitting a space or an event (planning-goals).
    195k repo stars
  41. ▌
    Pricing Promotions · anthropics
    Price changes within the store's guardrails, rate recommendations from demand, occupancy, or sell-through pace, promotions with their scope, depth, and dates, the markdown option for stock or capacity that is not selling, and the margin preview before any of it is staged. Not needed for explaining why revenue moved (performance-insights) or writing promotional copy (marketing-campaigns).
    195k repo stars
  42. ▌
    Marketing Campaigns · anthropics
    Drafting campaigns and ads as staged drafts, from acquisition and seasonal pushes to lifecycle sends such as win-backs, pre-arrival messages, and presale or last-call notices, choosing audiences and placements by intent, allocating budget across campaigns, and reviewing campaign results with their attribution caveats. Not needed for listing copy (catalog-listings) or overall performance questions (performance-insights).
    195k repo stars
  43. ▌
    Inventory Operations · anthropics
    Stock, capacity, and availability monitoring, acting on low-stock and slow-mover alerts, triaging order exceptions such as delays, return spikes, and complaints, and the operator's daily briefing; any start-of-day or what-needs-attention rundown is this flow, presented as a digest. Not needed for performance questions with no operational action attached.
    195k repo stars
  44. ▌
    Performance Insights · anthropics
    Explaining how the business is doing, meaning why a metric moved, which segment drove it, pace against a comparable, progress against goals the operator has stated, and questions over sales, traffic, conversion, and customers or this operation's equivalents that the snapshot alone does not answer. Not needed when the snapshot's headline figures and their change on the prior period answer the question, how a period went included.
    195k repo stars
  45. ▌
    Memory Personalization · anthropics
    Requests about what is remembered, however short, from an ask to remember one thing to asks to say what is on file, correct it, or forget it; a bare save or an answer from the profile alone does not cover these. Also applying what the store already knows, recalling an older fact (a past recipient, a size, a recurring order) when it would change the pick, and deciding what should outlast the session. Not needed when the request carries no personal context to apply or keep.
    195k repo stars
  46. ▌
    Commerce Evals · anthropics
    Authoring and running behavioral evals for a shopping or merchant agent, covering the case shape, authoring rules, code graders and judges, the run pattern, and poisoned fixtures. Load when writing eval cases or rubrics or deciding how a suite runs.
    195k repo stars
  47. ▌
    Commerce UI Tools · anthropics
    The reference presentation-tool contract, covering server-side enrichment, suggestion chips, the event stream, progressive rendering, both roles' built-in components, and adding a vertical component. Load when building or reviewing how a commerce agent's output reaches a frontend.
    195k repo stars
  48. ▌
    Commerce Architecture · anthropics
    How the reference commerce agents of either role are structured, covering the loop, where each rule lives, skills, the backend interface, delegates, and model fields. Load when designing or reviewing the structure of a shopping or merchant agent.
    195k repo stars
  49. ▌
    Commerce Trust Safety · anthropics
    The rules the reference agents enforce in code for third-party content, writes, grounding, identity, and memory, each with its module, plus two adversarial-eval rules. Load when handling untrusted tool results, guarding a write tool, or scoping what an agent remembers.
    195k repo stars
  50. ▌
    Commerce Prompt Caching · anthropics
    The reference agents' cache-stable request assembly, covering the static system and per-request context split, the fixed tool list, the rolling conversation breakpoint, which config fields are prompt bytes, and verification. Load when writing or reviewing a commerce agent's prompt assembly, when cache reads are zero, or when a turn's latency or cost is the question.
    195k repo stars
  51. ▌
    Commerce Merchant Operations · anthropics
    The reference merchant agent, covering its flows, staged changes and host approval, metrics grounding, the analysis delegate, store memory, components, and marketplace rules. Load when building or reviewing an agent for the operators of a store, property, subscriber base, or venue.
    195k repo stars
  52. ▌
    Jira API · anthropics bundle
    Read and manage Jira Cloud issues, projects, boards, sprints, comments, and transitions. Use this whenever the user wants to search issues with JQL, create or update a ticket, transition an issue (move to In Progress / Done), add a comment, check a sprint or board, look up a project, or ask "what's in my Jira queue" — even if they don't say "API". Also use it for any *.atlassian.net URL, an issue key like "PROJ-123", or a JQL string. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  53. ▌
    Asana API · anthropics bundle
    Read and manage Asana tasks, projects, sections, comments, and workspaces. Use this whenever the user wants to list or search tasks, create or update a task, complete a task, comment on a task, move tasks between projects or sections, look up a project or workspace, or ask "what's on my Asana list" — even if they don't say "API". Also use it for any app.asana.com URL or an Asana task/project gid. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  54. ▌
    Linear API · anthropics bundle
    Read and manage Linear issues, projects, cycles, teams, comments, and labels. Use this whenever the user wants to list their issues, search issues, create or update an issue, move an issue between states, add a comment, check a project or cycle, look up a team, or ask "what's on my plate in Linear" — even if they don't say "API" or "GraphQL". Also use it for any linear.app URL or an issue identifier like "ENG-123". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  55. ▌
    Notion API · anthropics bundle
    Search, read, and write Notion pages, databases, and blocks. Use this whenever the user wants to find a page in Notion, read a database, add a row, create or append content to a page, or asks "what's in my Notion" — even if they don't say "API". Also use it for any URL under notion.so or a mention of a Notion page/database ID. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  56. ▌
    Sentry API · anthropics bundle
    Query and manage Sentry error-tracking data — list and search issues, drill into events and stack traces, inspect projects and releases, resolve/ignore issues, and pull stats. Use this whenever the user mentions a Sentry issue, crash, error group, or exception; pastes a sentry.io or self-hosted Sentry URL; asks "why is this erroring", "how many times has this happened", "what's the top error in {project}", "resolve this issue", or wants a Sentry-based digest — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  57. ▌
    Datadog API · anthropics bundle
    Query and manage Datadog monitoring data — logs, metrics, monitors, dashboards, events, SLOs, traces, and incidents. Use this whenever the user wants to search logs, look at a metric, check which monitors are alerting, investigate a trace, pull SLO status, mute an alert, or ask "what's happening in Datadog" — even if they don't say "API". Also use it for any URL under *.datadoghq.com. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  58. ▌
    Grafana API · anthropics bundle
    Work with a Grafana instance — search and read dashboards, run datasource queries (Prometheus, Loki, PostgreSQL, etc.), inspect alert rules and silences, post annotations, and manage folders. Use this whenever the user mentions a Grafana dashboard, panel, or alert; pastes a Grafana URL; asks "what does this dashboard show", "query this metric in Grafana", "is this alert firing", "silence this alert", or wants to create/export a dashboard — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  59. ▌
    Hubspot API · anthropics bundle
    Read, create, update, search, and associate HubSpot CRM records — contacts, companies, deals, tickets, and custom objects. Use this whenever the user wants to look up a contact, create a deal, update a company, search the CRM, link two records, or asks "what's in HubSpot" — even if they don't say "API". Also use it for any URL under app.hubspot.com or a mention of a HubSpot object/record ID. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  60. ▌
    Bigquery API · anthropics bundle
    Run SQL against Google BigQuery and browse its catalog — submit queries (sync or async), poll job status, page through results, list datasets/tables, and read table schemas. Use this whenever the user wants to query a BigQuery table, ask "what's in this dataset", check a BigQuery job's status, or mentions bigquery.googleapis.com or a `project.dataset.table` path. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  61. ▌
    Redshift API · anthropics bundle
    Run SQL against Amazon Redshift — submit statements, poll status, page through results, and browse databases/schemas/tables. Use this whenever the user wants to query Redshift (provisioned cluster or Serverless), ask "what tables are in this schema", check a query's status, or mentions `redshift-data`, a Redshift cluster identifier / workgroup name, or a `redshift-data.{region}.amazonaws.com` endpoint. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  62. ▌
    Pagerduty API · anthropics bundle
    Query and manage PagerDuty — find out who's on call, list and manage incidents, read escalation policies and schedules, trace who got paged and why, acknowledge/resolve/snooze/escalate incidents, and create or update services. Use this whenever the user mentions PagerDuty, on-call, paging, escalation, an incident ID like `PXXXXXX` or `Q...`, asks "who's on call", "page the on-call", "ack this incident", "why wasn't I paged", or pastes a pagerduty.com URL — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  63. ▌
    Snowflake API · anthropics bundle
    Run SQL against Snowflake — submit statements, poll async handles, fetch result partitions, cancel, and browse warehouses/databases/schemas/tables. Use this whenever the user wants to query Snowflake, ask "what tables are in this schema", check a warehouse's status, or mentions `snowflakecomputing.com`, `/api/v2/statements`, or a Snowflake account identifier (like `xy12345.us-east-1`). Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  64. ▌
    Confluence API · anthropics bundle
    Read, search, and manage Confluence Cloud pages, spaces, blog posts, comments, attachments, and labels. Use this whenever the user wants to find a page, read a doc, search the wiki with CQL, create or update a page, add a comment, list pages in a space, pull an attachment, or ask "what does the wiki say about X" — even if they don't say "API". Also use it for any *.atlassian.net/wiki URL, or a CQL string when the context is wiki content rather than tickets. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  65. ▌
    Salesforce API · anthropics bundle
    Query, read, create, update, and describe Salesforce records — Accounts, Contacts, Opportunities, Leads, Cases, and custom objects. Use this whenever the user wants to look up a Salesforce record, run a SOQL query, update an Opportunity, check an object's fields, or asks "what's in Salesforce" — even if they don't say "API". Also use it for any URL under *.salesforce.com / *.lightning.force.com or a mention of a Salesforce record ID or SOQL. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  66. ▌
    Graphing · anthropics bundle
    Compose polished charts (timeseries, bar, line, area, pie, scatter, or anything else the data calls for) from tabular data using the chartkit primitives, producing PNG, SVG, or self-contained interactive HTML. Use when the user asks to chart, graph, plot, or visualize data and wants something better than raw matplotlib defaults.
    195k repo stars
  67. ▌
    Oncall Init · anthropics bundle
    Set up Claude Tag for oncall for a team, from that team's standing (public) oncall / monitoring channel. It does two things: it sets the channel up for monitoring, so alerts and incident posts here (from a person or from another Slack bot) get triaged and acted on automatically, and it finds and sets up the connectors, plugins and skills Claude can use for oncall. A workspace can have several such channels (one per team or rotation); run it once in each, by anyone, and every run adds or updates that team's section in the one oncall memory in shared workspace memory, never touching another team's part. Running it again in the same channel updates that section. Use when someone says "set up oncall", "init oncall", "get Claude ready for incidents", "configure Claude for on-call". Surveys the agent connectors a workspace admin has configured for Claude and proves one of them with a single read-only pull, so access is verified rather than assumed, explores the tools, Slack, repos and docs to learn what's available
    195k repo stars
  68. ▌
    Google Drive API · anthropics bundle
    Search, read, create, update, export, and share files in Google Drive. Use this whenever the user wants to find a file in Drive, read a Google Doc or Sheet, upload a file, move something into a folder, change sharing permissions, or asks "what's in my Drive" — even if they don't say "API". Also use it for any URL under drive.google.com or docs.google.com, or a mention of a Drive file ID. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  69. ▌
    Incident Init · anthropics
    Automatic init the first time Claude acts in an incident or alerts channel — a channel named like #inc-…, #incident-…, #sev0-…/#sev1-…, or one whose recent messages are pages or alerts — posted by PagerDuty, Opsgenie, incident.io, Datadog, Sentry or Grafana, or typed by people relaying them; ordinary talk about having been paged is not an alert — and that is not already set up as a team's oncall / monitoring channel. Run it once per channel, on first contact (just invited, first @-mention, channel just created), before doing whatever was asked: load the oncall memory that oncall setup wrote to shared workspace memory, pick the owning team's section, work out which monitoring / paging / error-tracking / code tools Claude can reach directly and which are missing, post one short message a reader with zero context can follow, note what was found in this channel's memory so threads don't repeat it, then hand off to `incident-investigate` if something was asked — or immediately, with nobody having asked, when the c
    195k repo stars
  70. ▌
    Oncall Handoff · anthropics bundle
    Run the oncall handoff for a rotation window — the whole handoff, not just a document: build the summary (what the incoming oncall needs to know first, what is still open, incidents with impact numbers, alert and page counts, hygiene suggestions, every number traceable to a source), post it as the report for the outgoing oncall to correct, walk the incoming oncall through the open items and answer their questions in the thread, update the open-items list as they respond, and note when the incoming person acknowledges. Runs mainly in the team's standing oncall / monitoring channel, normally as a scheduled routine that fires at rotation change so the report is waiting when the shift turns over; it can also be asked for by hand ("@Claude run the handoff"), and works from an incident channel too. Use when a scheduled handoff routine fires, or on "handoff", "hand-off", "hand over", "oncall summary", "shift summary", "weekly oncall report", "what happened this shift / this week", "write up the rotation", or when so
    195k repo stars
  71. ▌
    Incident Sitrep · anthropics
    Post a sitrep (situation report) for a live incident, in its incident channel: a short update in a fixed layout for people who have not read the whole channel — the current picture and what moved since the previous update, nothing more. Use on "sitrep", "status update", "where are we", "what's the latest", "catch me up", "summarize the incident so far", "update for leadership / support / customers", or when asked to keep posting one on a schedule ("post a sitrep every hour until this is resolved"); also when the oncall memory sets an update cadence for incidents of this severity and the person running the incident asks Claude to keep it. Reads the channel, the alert thread and the findings already posted, re-reads the one key signal, and writes: status line, TL;DR, impact, what changed since the last sitrep, what is in progress and who has it, what is needed, when the next update comes, one chart. Facts come only from what people in the channel said or what Claude read first-hand; cause and recovery time are
    195k repo stars
  72. ▌
    Enterprise Search · anthropics bundle
    Search the company's enterprise knowledge index. Use this FIRST when starting any task that touches company-specific context - projects, people, policies, internal docs, prior decisions - before searching individual sources like Drive, Slack, or Jira directly. Also use it when the user asks "do we have a doc about X", "what's our policy on Y", or references internal initiatives by name. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
    195k repo stars
  73. ▌
    Config Guide · anthropics bundle
    Reference guide for configuring @Claude agents — agents, agent scopes, identity profiles, presets, connections, rules, GitHub repositories, and custom instructions. Explains the inheritance model and configuration best practices.
    195k repo stars
  74. ▌
    Incident Postmortem · anthropics
    Write the postmortem for an incident, in its incident channel, once it is mitigated or resolved. Use on "write up this incident", "postmortem", "incident summary", "what happened here for people who weren't around", "draft the retro", or when the oncall memory says incidents of this severity get one. Reads the incident channel (and the alert thread it came from), the investigation findings and the data behind them, and writes a one-screen, zero-context write-up: what happened, impact with numbers, detection, timeline with durations, why it happened, what fixed it, follow-ups with proposed owners, and one before/during/after chart. Posted and pinned in the incident channel as its final pinned post, with edit requests updating that one pinned post in place — unless the person or the team's conventions say write-ups live elsewhere, in which case it is written there and only a link is posted, nothing pinned. A person edits and publishes it; never assigns blame.
    195k repo stars
  75. ▌
    Debug Plugins · anthropics
    Diagnose why a plugin or skill configured in @Claude admin settings isn't loading. Checks mount directories, the Claude Code launch command, and startup logs from inside the running container, then explains what failed and how to fix it.
    195k repo stars
  76. ▌
    Patch · anthropics bundle
    Generate candidate fixes for verified security findings. Consumes TRIAGE.json (preferred), VULN-FINDINGS.json, INCIDENTS.json, or a vuln-pipeline results directory. Pipeline input is delegated to the execution-verified `vuln-pipeline patch` ladder; static-analysis input gets a per-finding patch subagent + independent reviewer and is written as inert diffs for human review. Writes PATCHES/bug_NN/{patch.diff,patch_result.json}, PATCHES.md, and PATCHES.json. Use when asked to "fix the findings", "patch these vulns", "generate fixes", or "close the loop on triage".
    195k repo stars
  77. ▌
    Triage · anthropics bundle
    Triage a batch of raw security findings. Verify each is real, collapse duplicates, re-rank by derived exploitability, and tag with an owner. Takes a directory or file of scanner output and writes TRIAGE.json + TRIAGE.md sorted by what actually needs engineering attention. Use when asked to "triage findings", "validate scanner output", "prioritize vulns", or "review the backlog". Runs interactively by default; pass --auto to skip the interview.
    195k repo stars
  78. ▌
    Verify · anthropics
    Verify harness changes end-to-end without docker — drive the real pinned CLI against a header-capturing stub server with the exact env resolve_auth_env() produces.
    195k repo stars
  79. ▌
    Dnr Hunt · anthropics bundle
    Proactive threat hunt over web/application logs — no alert in hand. Profiles the corpus, runs a hypothesis-driven hunt loop with a mandatory written ledger, confirms suspects in source, detonates a local PoC, and writes INCIDENTS.json + INCIDENT_REPORT.md. Use when asked to "hunt the logs", "find the campaign", "look for signs of compromise", or "run dnr-hunt". The no-alert entry to the detection & response track; /dnr-respond is the lead-in-hand entry.
    195k repo stars
  80. ▌
    Customize · anthropics bundle
    Adapt this C/C++ ASAN vulnerability pipeline to a different vulnerability class, target shape, language, or detection mechanism. Use when the user wants to port, migrate, retarget, customize, or fork the pipeline for something other than C/C++ memory-safety bugs — web apps, smart contracts, deserialization, ML systems, or any other domain.
    195k repo stars
  81. ▌
    Vuln Scan · anthropics
    Static source-code vulnerability scan. Reads a target directory (and THREAT_MODEL.md if present), spawns parallel review subagents per focus area, and writes VULN-FINDINGS.json + .md for /triage to consume. Read-only — no building, running, or network. For execution-verified crashes, use vuln-pipeline instead. Use when asked to "scan for vulns", "review this code for security issues", "find bugs in <dir>", or as the step between /threat-model and /triage.
    195k repo stars
  82. ▌
    Quickstart · anthropics
    The front door for this repo. With no argument: a 30-second intro, then an offer to walk you through your first run on the canary target. With a question: answers it from this repo's own docs and source, cites where it looked, and hands you the next command. Use for "how do I…", "why does…", "where is…", "can this…", or just "/quickstart" to get oriented.
    195k repo stars
  83. ▌
    Dnr Respond · anthropics bundle
    Incident response workup for a lead in hand — an alert, an IOC, or a /dnr-hunt finding. Scopes the lead across the logs, verdicts whether the attack succeeded, quantifies blast radius, confirms root cause in source with a local PoC, and writes a proposed (never executed) containment/remediation/recovery plan. Use when asked to "respond to this alert", "work this incident", "how bad is this", or "run dnr-respond". /dnr-hunt is the no-alert entry to the same track.
    195k repo stars
  84. ▌
    Threat Model · anthropics bundle
    Build a threat model for a target codebase. Three modes: "interview" walks an application owner through the four-question framework and produces a threat model from their answers; "bootstrap" derives a threat model from the code plus past vulnerabilities (CVEs, git history, pentest reports) when no owner is available; "bootstrap-then-interview" chains the two when both owner and codebase are present. All write THREAT_MODEL.md in a shared schema. Use when asked to "threat model", "build a threat model", "map the attack surface", or "what should we be worried about in this codebase".
    195k repo stars
  85. ▌
    Tres Erp Rule Suggestions · anthropics
    Guide users through creating ERP accounting rules for crypto organizations on the Tres Finance platform. Maps every transaction type to the correct chart of accounts entries using a layered rule engine. Trigger: user asks to create, review, or fix ERP rules / accounting mappings for an organization.
    195k repo stars
  86. ▌
    Tres Request Skill Update · anthropics
    Submit feedback about the TRES Claude plugin — bug reports, feature requests, skill improvements, new skill ideas, MCP issues, workflow friction, or positive feedback about what's working well. Use this skill whenever the user wants to share any kind of feedback about the plugin, its skills, or the TRES MCP. Trigger phrases include: "submit feedback", "report a bug", "request a feature", "suggest an improvement", "I have an idea", "something is broken", "the skill isn't working", "I love this skill", "this worked great", "the MCP is returning wrong data", "the flow is confusing", "can you fix the skill", "file a skill request", "give feedback", "this could be better". Also trigger proactively when the conversation appears to be wrapping up — e.g. the user says "thanks", "that's all", "looks good", "we're done", "nothing else", or any other signal that the task is complete. In that case, offer a brief feedback prompt instead of launching the full guided flow. Do NOT trigger for general questions about how a sk
    195k repo stars
  87. ▌
    Skill Development 3 · anthropics bundle
    This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
    195k repo stars
  88. ▌
    Skill Development 2 · anthropics bundle
    This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
    195k repo stars
  89. ▌
    Configure 3 · anthropics
    Check iMessage channel setup and review access policy. Use when the user asks to configure iMessage, asks "how do I set this up" or "who can reach me," or wants to know why texts aren't reaching the assistant.
    195k repo stars
  90. ▌
    Access 2 · anthropics
    Manage iMessage channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the iMessage channel.
    195k repo stars
  91. ▌
    Example Skill 2 · anthropics
    This skill should be used when the user asks to "demonstrate skills", "show skill format", "create a skill template", or discusses skill development patterns. Provides a reference template for creating Claude Code plugin skills.
    195k repo stars
  92. ▌
    Access 3 · anthropics
    Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.
    195k repo stars
  93. ▌
    Skill Creator 2 · anthropics
    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.
    195k repo stars
  94. ▌
    Theme Factory · anthropics
    Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
    195k repo stars
  95. ▌
    Internal Comms 2 · anthropics
    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.).
    195k repo stars
  96. ▌
    Brand Guidelines 2 · anthropics
    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.
    195k repo stars
  97. ▌
    Claude Academy Guide · anthropics
    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
    195k repo stars
  98. ▌
    Claude Automation Recommender · anthropics bundle
    Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
    195k repo stars
  99. ▌
    Analyzing Financial Statements · anthropics bundle
    This skill calculates key financial ratios and metrics from financial statement data for investment analysis
    195k repo stars
  100. ▌
    Build MCP App · anthropics bundle
    This skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build "MCP UI resources", make a tool that shows a "form", "picker", "dashboard" or "confirmation dialog" inline in the conversation, or mentions "apps SDK" in the context of MCP. Use AFTER the build-mcp-server skill has settled the deployment model, or when the user already knows they want UI widgets.
    195k repo stars