submit-solution

$npx mdskill add anthropics/cwc-workshops/submit-solution

Guide users to commit code and open PRs with feedback.

  • Collects experience questions before code submission.
  • Displays git diff to show starter-agent changes.
  • Gathers final eval scores from report files.
  • Writes PR body combining code changes and feedback.

SKILL.md

.github/skills/submit-solutionView on GitHub ↗
---
name: submit-solution
description: 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.
---
<!-- Copyright 2026 Anthropic PBC -->
<!-- SPDX-License-Identifier: Apache-2.0 -->


# Submit your StockPilot solution

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.

## Step 1 — Ask about their experience first

Before touching git, ask these three questions (use AskUserQuestion or just
conversational):

1. **Which subagent approach did you go with for cycle 3?**
   (callable_agents / spawn_subagent / inline / something else)
2. **What was the hardest part of the workshop?**
   (a specific cycle, a concept, the tooling, the timing)
3. **One thing you'd change about it?**

Hold onto their answers — they go in the PR body.

## Step 2 — Show them what they're submitting

```bash
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:

```bash
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%}')"
```

## Step 3 — Commit and push

```bash
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.

## Step 4 — Open the PR with feedback in the body

```bash
gh pr create --title "Workshop solution — <name>" --body-file -
```

PR body template (fill from step 1 + step 2):

```markdown
## 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>
```

## Step 5 — Confirm

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.

## Don't

- Don't open the PR before they've seen the diff and the body
- Don't skip the feedback questions to "save time" — that's the point
- Don't include `evals/reports/` or `.stockpilot_ids.json` in the commit

More from anthropics/cwc-workshops

SkillDescription
edgartools-sec-dataHow 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.
forecastingHow 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.
incident-triage-runbookThe 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.
miningWhere diamonds spawn in Minecraft 1.20.
notify-templatesFixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".
postmortem-reportHow 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.
reorder-policyHow 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.
supplier-selectionHow 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.
weekly-reportStructure and data sources for the weekly inventory report. Load this when the task is "weekly report", "Monday report", or "summarize inventory status".
workshopWorkshop 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.