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.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
You're helping a workshop attendee package up their agents/starter/agent.py
decomposition and open a PR. The PR is how facilitators see what approaches
people took, and the description doubles as the workshop feedback form.
Before touching git, ask these three questions (use AskUserQuestion or just conversational):
Hold onto their answers — they go in the PR body.
git diff main -- agent-decomposition/agents/starter/agent.py
Walk through the diff briefly: which tools they dropped, which skills they enabled, which subagent approach they wired. If the diff is empty, they haven't edited starter — ask if they worked in a different file.
Also grab their final eval score:
ls -t evals/reports/*/starter.json | head -1 | xargs cat | python -c "import json,sys; d=json.load(sys.stdin); print(f'{d[\"score\"]:.0%}')"
git checkout -b solution/<their-name-or-handle>
git add agent-decomposition/agents/starter/agent.py
git commit -m "Workshop solution: <subagent approach>, <score>%"
git push -u origin solution/<their-name-or-handle>
Ask for their name/handle if you don't have it. If they don't have push
rights to anthropics/cwc-workshops, have them fork first
(gh repo fork --clone=false) and push to their fork.
gh pr create --title "Workshop solution — <name>" --body-file -
PR body template (fill from step 1 + step 2):
## My decomposition
- Subagent approach: <callable_agents | spawn_subagent | inline | other>
- Final eval score: <NN>%
- Tools I dropped: <list>
- Skills I enabled: <list>
## Workshop feedback
**Hardest part:** <their answer>
**One thing I'd change:** <their answer>
**Anything else:** <free text — leave blank if nothing>
Give them the PR URL and thank them. Mention that facilitators read every PR and the feedback directly shapes the next run of this workshop.
evals/reports/ or .stockpilot_ids.json in the commitNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Where diamonds spawn in Minecraft 1.20.
The English summary is being prepared. Showing the original description.
Fixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".
The English summary is being prepared. Showing the original description.
How the SRE team writes a postmortem PDF. Use this whenever asked for a postmortem, an incident report, a write-up to share, or a PDF of what happened.
The English summary is being prepared. Showing the original description.