agentleFS
sammyjoycesammyjoyce/prime-pstack/skills/setup-pstack/SKILL.md

setup-pstack

Skill1 starsChanged 2 months agoMITView on GitHub

Configure which models pstack uses per role and at what reasoning budget. Use for /setup-pstack, /skill:setup-pstack, "pstack budget", or changing pstack's model choices.

29 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use poteto-help, make-bot-ui and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 13 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 15 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 16 projects that use this

  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 6 projects that use this

  • TheOnlyFusionCubeSkill

    statechart

    Draw what an app's user sees as a Mermaid statechart from a TLA+ model. States are gray if they work, red if still wrong, and green if fixed. Each bug TLC finds is a numbered path. Use for /statechart, \"show the PM the bug\", or to turn an agreed chart into a TLA+ skeleton.

    Also in 8 projects that use this

  • TheOnlyFusionCubeSkill

    maintain-formal-verification-skill

    Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.

    Also in 8 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the /setup-pstack command.

    line 9
  2. Distinctive:

    If the command is unavailable, write that JSON yourself:

    line 12
  3. Very specific:

    never write a selector you have not confirmed is available (await rlm.find_models(<query>) returns exact provider/id selectors)

    line 18
  4. Very specific:

    Do not commit it. If ~/.prime/agent/pstack-models.md exists and the JSON does not, the extension migrates it on session start.

    line 52
  5. Very specific:

    If ~/.prime/agent/pstack-models.md exists and the JSON does not, the extension migrates it on session start.

    line 53
  6. Very specific:

    After writing, tell the user it applies to new turns.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup pstack

Run the /setup-pstack command. It asks for a reasoning budget, then lists the models scoped to this Prime Agent session (enabledModels, the same set /scoped-models shows, or every available model when nothing is scoped) for each role, and writes ~/.prime/agent/pstack/models.json.

If the command is unavailable, write that JSON yourself:

  • version: 1
  • budget: unlimited (default), large, medium, small, or inherit. The first four map to a thinking= target of max, xhigh, high, medium on rlm.spawn, clamped per model to what that model supports. inherit means children keep the parent thinking level.
  • roles: one key per role listed below
  • each value is inherit-parent, auto, a provider/id selector, or an array of those
  • never write a selector you have not confirmed is available (await rlm.find_models(<query>) returns exact provider/id selectors)
  • a role you leave out keeps the shipped roster below

Shipped roster (mirrors the upstream split with models that work here: zai/glm-5.3 takes the fast code seat, anthropic/claude-opus-5 the judgment seat, openai/gpt-6-astra the OpenAI seat, and anthropic/claude-fable-5-1 is the panel's fourth member):

feature, refactoring: zai/glm-5.3
bug-fix: zai/glm-5.3
perf-issue: zai/glm-5.3
hillclimb: zai/glm-5.3
judgment and prose: anthropic/claude-opus-5
hardest tasks: anthropic/claude-opus-5
how explorer: zai/glm-5.3
how explainer: anthropic/claude-opus-5
why investigators: zai/glm-5.3
why synthesizer: anthropic/claude-opus-5
reflect tooling: openai/gpt-6-astra
reflect judgment, divergent, synthesizer: anthropic/claude-opus-5
arena runners: anthropic/claude-opus-5, openai/gpt-6-astra, zai/glm-5.3, anthropic/claude-fable-5-1
arena cross-judge pool: anthropic/claude-opus-5, openai/gpt-6-astra, zai/glm-5.3, anthropic/claude-fable-5-1
swarm workers: zai/glm-5.3
architect runners: anthropic/claude-opus-5, openai/gpt-6-astra, zai/glm-5.3, anthropic/claude-fable-5-1
interrogate reviewers: anthropic/claude-opus-5, openai/gpt-6-astra, zai/glm-5.3, anthropic/claude-fable-5-1

A roster entry with no live credentials in a session is dropped from the injected table for that session (the role then runs on the parent model), so the shipped roster is safe on a machine that has only some of these providers.

Roles: feature, refactoring; bug-fix; perf-issue; hillclimb; judgment and prose; hardest tasks; how explorer; how explainer; why investigators; why synthesizer; reflect tooling; reflect judgment, divergent, synthesizer; arena runners; arena cross-judge pool; swarm workers; architect runners; interrogate reviewers.

Panel roles (arena runners, arena cross-judge pool, architect runners, interrogate reviewers) are arrays: one subagent per entry.

The budget is separate from the model. The upstream plugin bakes effort into model slugs (...-thinking-max); Prime Agent passes thinking= on rlm.spawn instead. The injected table already clamps the budget to each model's ceiling (for example xai/grok-4.6 tops out at xhigh and the opencode-go mirrors at high), so copy the thinking= value as written.

The file is user-level. Do not commit it. If ~/.prime/agent/pstack-models.md exists and the JSON does not, the extension migrates it on session start. A Pi-era ~/.pi/agent/pstack/models.json is not read; copy it across by hand.

After writing, tell the user it applies to new turns. Offer /skill:create-verification-skill once if the project has no verify skill, same as before.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.