wandb/senpai / plugins/senpai/skills/assign-experiment
assign-experiment
VerifiedCreate a typed assignment branch and draft PR for one student. Use when the advisor has a concrete hypothesis and the student has no open `status:wip` or `status:review` assignment.
Assign an experiment
Read the current baseline. Use the immutable program.md snapshot embedded in your system prompt as policy when you write one complete assignment:
- a falsifiable hypothesis and mechanism;
- exact files and changes in scope;
- baseline metrics and W&B evidence; and
- one student, one branch, and one experiment.
State commands, metrics, run limits, and stop conditions. Explain when results become informative, including required training, scale, or tuning. State uncertainty and evidence needed to continue. Follow programme limits.
Call sync_advisor_branch to fetch the configured advisor branch and record
the exact remote SHA it returns; this checkout does not see merges on its own.
Then call create_assignment with this operation-specific payload; the runtime
supplies and enforces the configured advisor branch and student allowlist:
{
"assignment_id": "stable-assignment-id",
"revision_id": "initial-revision-id",
"student": "student-name",
"expected_base_sha": "FETCHED_REMOTE_ADVISOR_SHA",
"head_branch": "student-name/hypothesis-slug",
"title": "Concise hypothesis title",
"body": "Complete actionable experiment brief"
}
The tool creates an empty assignment commit without changing the advisor worktree, pushes the branch with a lease, creates or reconciles one draft PR, adds the exact routing labels, embeds the typed assignment marker, verifies the result, and rejects a second active assignment for the student.
Do not create the branch, PR, labels, or assignment marker through shell commands. If the tool reports stale state, refresh the named SHA and re-evaluate rather than bypassing the precondition.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |