USE IN CLAUDE / GITHUB REPO / EXACT SETUP
Take the GitHub repo. Run it in Claude.
This page exists for the competition requirement. It shows exactly how to go from the public GitHub repo to a working Claude operator: what to download, what to upload, what to skip, and what prompt to run first.
Recommended path
Use a Claude Project. Upload the operator files once, set the instructions once, and keep testing real prospect messages in the same place.
What not to do
Do not upload the whole website folder as operator context. The operator is the repo logic files, not the public demo pages.
Open the public GitHub repository
Start at github.com/Georgewashingtoncarver/max-muscles-operator. This repo contains both the operator and the public site, but Claude only needs the operator files.
Claude needs these
identity.mdrules.mdexamples.md- everything inside
reference/
Claude does not need these
website/- brand or deploy files
- local-only handoff notes
Download the repo as a ZIP
Click the green Code button, then Download ZIP. Unzip it somewhere easy to find.
Create a new Claude Project
In claude.ai, open Projects, then create a new project named MAX MUSCLES Operator.
Projects
+ New ProjectCreate a project
Upload the operator files into Project knowledge
Inside the new project, click Add content and upload the core operator files plus the contents of reference/.
Drag and drop files into project knowledge
Upload this
identity.md,rules.md,examples.md- all files inside
reference/
Skip this
website/- deployment config
- screenshots or image assets unless you want them for presentation only
Set the Claude project instructions
Paste these instructions once. This tells Claude to act like the operator instead of a general assistant.
Paste this into Claude Project instructions
Run a real test prompt
Start a new chat inside the project and paste a messy prospect message. The operator should decide and act, not ask what to do.
Good first test
What you should expect back
- a clear primary problem, not just "weight loss"
- a route decision
- logic for why that route was chosen
- a finished plan, partial plan, or redirect
Judge test: feed it at least three different prospect cases. One normal send case, one review case, and one redirect case.
Verify the operator is doing the assignment
The competition is about building an operator, not a chatbot. Use this checklist before you submit.
Decision
Claude returns one route every time instead of bouncing the call back to you.
Edge cases
Medical context, surgery history, readiness problems, and symptom-vs-problem cases are handled explicitly.
Finished work
The output is something you could actually use: a full plan, safe partial plan, or reason-specific redirect.
SEE THE LOGIC
The setup is here. The operator logic is elsewhere.
Once you know how to load it into Claude, use the judges page and worked examples to inspect how it actually thinks.
Judges Overview Worked Examples