Setup Pstack

Walks you through mapping pstack's different roles,feature work, bug fixes, how/why/reflect modes, arena runners, architects,to whichever models you actually have access to in your Cursor session. It detects available models first so you don't accidentally pick something you can't use, then writes an always-applied rule file that overrides the skill defaults. The rule is idempotent, so you can re-run this whenever your model access changes or you want to shift which model handles judgment tasks versus fast iteration. Useful if you have specific preferences about which model does what, or if the defaults assume models you don't have. At the end it offers to generate a project-specific verification skill so agents can drive your app like a user would.

skills.sh installs: 4.6K
GitHub stars: 15.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cursor/plugins --skill setup-pstack --agent claude-code

Installs into .claude/skills of the current project.

Files

Setup pstack

Write ~/.cursor/rules/pstack-models.mdc, an always-applied rule that sets pstack's model per role.

Steps

1. Detect available models

Enumerate the model slugs you can pass to a Task subagent in this session. That is the dependable source. If Cursor also exposes a models API or CLI that lists the user's entitled models, prefer it for completeness. If you cannot detect any, ask the user to paste the slugs they have access to. Never write a real slug you have not confirmed is available. The aliases inherit-parent and auto are always valid even though they are not detected slugs.

2. Load current state

The default role-to-model mapping is the rule shape shown in step 5 below. If ~/.cursor/rules/pstack-models.mdc already exists, read it and treat its # budget line and its role values as the current choices. Otherwise start from those defaults. A line whose role is not in step 5, such as how critics, is from a retired role. Drop it.