b-urge

Managed Agents Workshop — Development skill for Claude Code

Development community

Enablement workshop for Claude Managed Agents: a 20-minute session with a live demo, a 60-minute hands-on lab where engineers build a support-ticket triage agent, an instructor hand-off guide, and a d.

How to install Managed Agents Workshop

This entry records only its repository, not the path inside it, so there is no exact command to give. Open b-urge/managed-agents-workshop and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Managed Agents Workshop does

Enablement workshop for Claude Managed Agents: a 20-minute session with a live demo, a 60-minute hands-on lab where engineers build a support-ticket triage agent, an instructor hand-off guide, and a design note.

Alternatives in Development

  • Create Handoff — You are tasked with writing a handoff document to hand off your work to another agent in a new session 10k ★
  • Hackingtool Plugin — Claude Code plugin: 183+ pentesting & OSINT tools from Z4nzu/hackingtool 1k ★
  • Harness Remote — Native-session control plane for Codex, Claude Code, OpenCode, OMP and PI 356 ★

README

Claude Managed Agents: enablement workshop

A workshop that takes engineers who have used the Messages API to building their first agent on Claude Managed Agents. It has a 20-minute session with a live demo, a 60-minute hands-on lab, and a hand-off guide for the instructor who teaches it.

In the lab, learners build a support-ticket triage agent. The agent works in Anthropic's sandbox, and learners write the code that answers it when it needs account data only their system has.

The four deliverables

Deliverable Where
Session (20 min, presented live) Live deck · `session/session.pdf` · `session/speaker-script.md` · `session/demo.ipynb`, with `demo_prerun.ipynb` as the offline fallback
Lab (60 min, self-guided) `lab/`. Start with its README, then `lab.ipynb`. The answer key is in `lab/solutions/`.
Instructor hand-off guide `handoff-guide.md`
Design note `design-note.md`, with `design-log.md` as the record behind it

Where to start

  1. Page through the deck, reading the speaker notes, to see what the cohort hears first.
  2. Open `lab/lab.ipynb` to see what they build. It reads fine on GitHub without running it.
  3. Read the design note for the decisions behind both, including what I changed from Claude's drafts.

Testing

The lab and demo were run end to end against the live API. One pilot tester, an engineer new to Managed Agents, completed the lab in 50 minutes without help. The package versions the lab was tested with are pinned in [`lab/requirements.txt`](lab/requirements.txt).