⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
notify-templates
Fixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
cwc-workshops
Workshop materials. Not maintained and not accepting contributions.
Materials from Anthropic-run Code with Claude workshops.
Workshops
rightmodel/— Picking the Right Model: use a Claude Code SKILL to audit an LLM eval suite and sweep it across models and inference parameters (extended thinking, effort) to find the best quality-per-dollar and quality-per-second configuration.agent-decomposition/— Compose Multi-Agent Systems with Skills and MCP: decompose a 400-line-prompt inventory agent into skills + code execution + callable_agents on Claude Managed Agents, with evals to verify each step.how-we-claude-code/— How We Claude Code: a three-phase walkthrough of an AI-assisted product workflow — interview to spec, four divergent design explorations as static HTML, and a Vite + React app whose components emit a machine-readable DOM contract so an agent (or CI) can verify them at runtime.ship-your-first-managed-agent/— Ship Your First Managed Agent: a Streamlit on-call dashboard with three pages open and an offline SRE Agent panel. Claude Code fills inagent.pyone part at a time while you make the judgment calls: one agent with a runbook Skill and custom tools, then multiagent (an incident commander with an investigator thread per page), memory stores (team history plus the agent's own notebook), and file output (a postmortem PDF you download). Built to run with a whole room on one API key.agent-battle/— Agent Battle: a 45-minute competition to configure a Claude Managed Agent — system prompt, skills, MCP servers, model — that drives a local game bot over MCP. Most diamonds wins, fewest tokens breaks ties; a fast--evaldecision-probe loop lets you test config changes in ~30s before committing to a 5-minute run.agents-that-remember/— Agents That Remember: start with a Managed Agent that's visibly amnesiac across sessions, then layer in memory primitives one at a time — a memory store for cross-session persistence, then the Dreaming Service to consolidate past transcripts — going "goldfish to colleague" in 45 minutes.eval-driven-agent-development/— Eval-Driven Agent Development: iterate a PPTX-generating Managed Agent through six variants (naive → visual → typography → palette → density → QA-loop), scoring each against a 10-task suite with a two-layer grader (programmatic.pptxXML metrics + LLM-as-judge on rendered slides) so every prompt change is measured, not vibed.production-ready-agent/— Deal Desk: a chat-first UI over a multi-agent M&A research team on Claude Managed Agents — a coordinator delegates to four parallel research sub-agents, reads prior-deal lessons from a memory store, reaches Linear via MCP, and emits a graded investment thesis while the UI streams every event and gated tool call.research-desk/— The Research Desk: build an SEC-filings research desk on Claude Managed Agents behind a self-hosted Next.js console — say hello to a bare agent you wire up yourself, then promote that same agent (versioned update) into a head of research that dispatches one analyst session per ticker through a custom tool your server fulfils, with sub-agent specialists, an edgartools Skill, outcome-graded scorecards, a shared memory store, and a weekly memo deployment.building-blocks/— Building Blocks: six short Python programs, one per Claude developer platform feature, against the plain Messages API: code execution with the Files API, programmatic tool calling, tool search, the advisor tool, effort, and the memory tool with context editing. Each file has one line to change and run again, so you can follow along on a laptop.
License
Apache License 2.0. See LICENSE.
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
agent-decomposition/.claude/skills/notify-templates/SKILL.md3.6 KBupstream ↗
--- name: notify-templates description: Fixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops". --- <!-- Copyright 2026 Anthropic PBC --> <!-- SPDX-License-Identifier: Apache-2.0 --> # Notification Templates Notifications are template fills, not creative writing. **Do not spawn a subagent for this.** Fill the slots from data you already have, then append the result to the outbox. ## Low-stock Slack alert ``` :warning: *Low stock* — {{sku}} ({{product_name}}) On hand: {{on_hand}} · Reorder point: {{reorder_point}} · Days of cover: {{days_cover}} {{action_line}} ``` `action_line` is either `PO {{po_id}} placed for {{qty}} units (ETA {{eta}})` or `Awaiting review — {{reason}}`. ## Supplier email ``` Subject: PO {{po_id}} — {{qty}} × {{sku}} Hi {{supplier_name}}, Please confirm PO {{po_id}} for {{qty}} units of {{sku}} ({{product_name}}) at ${{unit_price}}/unit. Requested delivery: {{requested_date}}. {{expedite_note}} Thanks, StockPilot ``` ## Escalation (human review needed) ``` :octagonal_sign: *Review needed* — {{sku}} Recommended qty: {{qty}} (confidence {{confidence}}) Flags: {{flags_csv}} Reason: {{reason}} ``` ## Routing (who gets what) | Audience | When | Example | |---|---|---| | `ops` channel (default) | Low-stock alerts, reorder recs, cycle-count adjustments, weekly reports. | Almost everything. | | `ops` with `@here` | Active or imminent stockout on a top-100 SKU, or a supplier delay that causes a stockout within 7 days. | "0 on hand at WH-EAST, network out in <1d" | | Purchasing lead (DM/email, not channel) | Single PO > $25k, deviation from the scored supplier, or new-supplier consideration. | | | Finance | Only if open-PO balance for one supplier would exceed $100k, or suspected duplicate POs. Nothing routine. | | When you escalate beyond the default channel, add one line saying which threshold was crossed. ## Batch, don't spam For sweeps and daily checks, send **one summary notification**, not one per SKU. The low-stock template above is for a single-SKU task; for a sweep, compose a single message listing the actioned SKUs (and any deferred) and send it once at the end. **When the task explicitly asks for one alert per SKU** (e.g. "send a personalized alert for each of the top 10"): fill the template once per SKU and write all lines to the outbox in one Bash heredoc, like: ```bash python -c ' import json rows = [...top-10 from batch_days_of_cover.py...] with open("/mnt/user/sinks/outbox.jsonl", "a") as f: for r in rows: f.write(json.dumps({"channel": "ops", "sku": r["sku"], "message": f":warning: Low stock — {r[\"sku\"]} ..."}) + "\n") ' ``` Do **not** call `send_slack_alert` (or any subagent) once per SKU — that's N model round-trips for template-filling. After sending a batch, your final response should be a **brief confirmation** ("✓ 10 alerts sent to ops — see outbox") plus a compact table of SKU + on-hand + days-of-cover. Do not echo the full alert text in your reply; it's already in the outbox. ## How to send Append directly to `/mnt/user/sinks/outbox.jsonl` via Bash — one JSON object per line, e.g.: ```bash python -c 'import json; print(json.dumps({"channel": "ops", "sku": "SKU-0012", "message": "..."}))' \ >> /mnt/user/sinks/outbox.jsonl ``` Use `json.dumps` so newlines in the message are escaped (raw `echo` would break the JSONL). That's the whole job: one read for the data you need (if you don't have it), one append. If you're making more than two calls to send a notification, you've over-engineered it.README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/anthropics-cwc-workshops-agent-decomposition-claude-skills-notify-templates.md