Individual skill
prime-worker
Use when delegating multi-turn work to a cheap local prime-agent subagent that must remember context across turns — iterating on a refactor, working through a subsystem, branching a what-if from an established investigation. Triggers when a delegated task needs more than one exchange, or when an earlier delegation should be continued rather than restarted. For one-shot descriptive reading that needs no follow-up, use delegate-bulk-read instead.
skills/prime-worker/SKILL.md
Source commit 94c050d24ddadf6274ee68f51b607f34226928b3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 0
- Repository last updated
- Oct 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude-code Repository topic
- claude-skill Repository topic
- llm-agents Repository topic
- prime-agent Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Prime Worker
## Overview
`prime-agent` is installed locally and runs models from the user's **OpenCode Go subscription**. Because that is a subscription, per-token price is *not* the thing to optimize — the real axes are context window, latency, and how much the model can be trusted with the task.
**A worker is a named directory.** `~/.claude/prime-workers/<name>/` holds exactly one session `.jsonl` plus a `worker.env` recording the `--cwd` and `--model` it was spawned with. The name is the only handle you ever need.
Drive it with the `pw` script bundled beside this skill: `scripts/pw`, relative to this file's own directory, or plain `pw` when it is on `PATH`. Do not hand-roll `prime-agent` invocations — the raw CLI has a trap that silently breaks continuity (see Failure Modes).
## Choosing the Model: Ask First
**Ask the user which model to use before spawning a worker.** Default to `deepseek-v4-flash`, but present the choice — the user tracks which models are performing well and that changes faster than this file does.
