Configure Channel
openclaw/openclaw
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
Configure which models p3-stack uses per role and at what reasoning budget.
$ npx skills add uzairansaruzi/p3-stack --skill setup-p3 -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install uzairansaruzi/p3-stack setup-p3 --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/uzairansaruzi/p3-stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/setup-p3 .claude/skills/setup-p3 && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "setup-p3" agent skill from https://github.com/uzairansaruzi/p3-stack/tree/main/skills/setup-p3 into .claude/skills/setup-p3/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-p3", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/uzairansaruzi/p3-stack/tree/main/skills/setup-p3Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add uzairansaruzi/p3-stack --skill setup-p3 -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install uzairansaruzi/p3-stack setup-p3 --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/uzairansaruzi/p3-stack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/setup-p3 .agents/skills/setup-p3 && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "setup-p3" agent skill from https://github.com/uzairansaruzi/p3-stack/tree/main/skills/setup-p3 into .agents/skills/setup-p3/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-p3", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add uzairansaruzi/p3-stack --skill setup-p3 -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install uzairansaruzi/p3-stack setup-p3 --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/uzairansaruzi/p3-stack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/setup-p3 .cursor/skills/setup-p3 && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "setup-p3" agent skill from https://github.com/uzairansaruzi/p3-stack/tree/main/skills/setup-p3 into .cursor/skills/setup-p3/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-p3", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/uzairansaruzi/p3-stack.git --path skills/setup-p3--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add uzairansaruzi/p3-stack --skill setup-p3 -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install uzairansaruzi/p3-stack setup-p3 --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/uzairansaruzi/p3-stack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/setup-p3 .gemini/skills/setup-p3 && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "setup-p3" agent skill from https://github.com/uzairansaruzi/p3-stack/tree/main/skills/setup-p3 into .gemini/skills/setup-p3/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-p3", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install uzairansaruzi/p3-stack setup-p3Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add uzairansaruzi/p3-stack --skill setup-p3 -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/uzairansaruzi/p3-stack.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/setup-p3 .github/skills/setup-p3 && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "setup-p3" agent skill from https://github.com/uzairansaruzi/p3-stack/tree/main/skills/setup-p3 into .github/skills/setup-p3/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-p3", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add uzairansaruzi/p3-stack --skill setup-p3 -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install uzairansaruzi/p3-stack setup-p3 --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/uzairansaruzi/p3-stack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/setup-p3 .opencode/skills/setup-p3 && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "setup-p3" agent skill from https://github.com/uzairansaruzi/p3-stack/tree/main/skills/setup-p3 into .opencode/skills/setup-p3/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-p3", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
setup-p3Configure which models p3-stack uses per role and at what reasoning budget.
Setup P3 is an agent skill from uzairansaruzi/p3-stack. Configure which models p3-stack uses per role and at what reasoning budget. Detects your available models and writes p3-models.md, which overrides the skill defaults. Use for /setup-p3, "configure p3 models", "p3 budget", or changing p3-stack's model choices.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: pstack reworked for T3 Code: delegated subagents, worktree threads, PR watching, scheduled runs. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 09909eb. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Setup P3 loads about 1.5k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 689 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from uzairansaruzi/p3-stack at commit 09909eb, republished under its MIT licence (© uzairansaruzi). 689 words, ~1,471 tokens.
.claude/skills/setup-p3/SKILL.md (or your agent's skills folder).Write p3-models.md, a file that sets p3-stack's model per role. Default location is the current project root. Offer ~/.agents/p3-models.md as the global option, and ask which one. A project file wins over the global one.
Call orchestrator_capabilities. It lists the providers and models you can pass to delegate_task in this session, custom models included, with each one's provider instance ID and any reasoning options. That is the only source. If it returns nothing, stop and tell the user. Never write a provider or model it did not return. inherit-parent is always valid even though it is not a detected model.
The roles are the labels shown in step 5. If p3-models.md already exists at the chosen location, read it and treat its # budget line and its role values as the current choices. Otherwise start from the defaults in step 3(b). A line whose role is not in step 5, such as how critics, is from a retired role. Drop it.
(a) Ask for a budget. Ask plainly in the thread. Offer these four options with these exact labels, and name the current budget when the file records one.
unlimited — keep maxlarge — xhigh reasoningmedium — high reasoningsmall — medium reasoning(b) Apply it. Build the working table. On a fresh run, give code roles (feature, refactoring, bug-fix, perf-issue, hillclimb) and the explorer, investigator, and swarm roles the fastest strong coding model detected. Give judgment and prose, hardest tasks, the explainer, the synthesizers, and reflect tooling the most capable model detected. Fill each panel role with one entry per distinct provider detected, up to three. On a re-run, keep any role the user changed.
When the catalog exposes reasoning options for a model, set each real entry's effort option from the budget: unlimited takes the highest option, and large, medium, and small take xhigh, high, or medium. The ladder is max > xhigh > high > medium > low. If the model does not expose the target, use the highest option at or below it, else mark the role as needing a choice. inherit-parent does not change. When the catalog exposes no reasoning options, map roles only and drop effort tokens; the budget label is still recorded.
(c) Show the roles and confirm. Show every role with its model, marking any entry not in the detected set as needing a choice. Also list each line step 2 dropped. Ask whether to accept as-is or change specific roles, offering the detected models plus inherit-parent (the role runs on the parent thread's model, so omit the model in delegate_task) as the options. For panel roles (arena runners, architect runners, interrogate reviewers) the value is a list, and one delegate_task runs per entry, inherit-parent entries included, so the list length sets the count. arena cross-judge pool is also a list, but Arena selects one value from it whose provider differs from the parent's when possible. swarm workers is the default model for every worker unless a race or comparison assigns another model per arm.
Every real entry written must be in the orchestrator_capabilities result, under the provider instance it came from. inherit-parent always passes. If a chosen entry is not available, stop and ask again.
Write p3-models.md with a # budget line with the chosen label and its target effort, and one line per role, using the same labels p3-mode uses. Write each entry as <providerInstanceId>/<model>, followed by its effort option in parentheses when step 3(b) set one. Overwrite the whole file so re-runs stay idempotent. Shape:
# p3 model configuration. One line per role. Delete a line to fall back to the skill default.
# `inherit-parent` as a value: the role runs on the parent thread's model (omit the delegate_task model). Entries in a panel list still count toward its fan-out.
# budget: unlimited (max)
feature, refactoring: <providerInstanceId>/<model> (<effort>)
bug-fix: <providerInstanceId>/<model> (<effort>)
perf-issue: <providerInstanceId>/<model> (<effort>)
hillclimb: <providerInstanceId>/<model> (<effort>)
judgment and prose: <providerInstanceId>/<model> (<effort>)
hardest tasks: <providerInstanceId>/<model> (<effort>)
how explorer: <providerInstanceId>/<model> (<effort>)
how explainer: <providerInstanceId>/<model> (<effort>)
why investigators: <providerInstanceId>/<model> (<effort>)
why synthesizer: <providerInstanceId>/<model> (<effort>)
reflect tooling: <providerInstanceId>/<model> (<effort>)
reflect judgment, divergent, synthesizer: <providerInstanceId>/<model> (<effort>)
arena runners: <entry>, <entry>, <entry>
arena cross-judge pool: <entry>, <entry>, <entry>
swarm workers: <providerInstanceId>/<model> (<effort>)
architect runners: <entry>, <entry>, <entry>
interrogate reviewers: <entry>, <entry>, <entry>Tell the user the file was written, where, and that it applies to new sessions. Re-running this skill updates it.
Check whether the project has a way to drive the real app for proof (a verify-* skill, or an existing harness). If not, offer once: "want a project-local verification skill, so agents can drive the app the way a user does and prove changes work? I can generate one with /create-verification-skill." On yes, invoke /create-verification-skill. On no, move on without pushing.
© uzairansaruzi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/setup-p3 of uzairansaruzi/p3-stack.
Open the folder on GitHubat commit 09909eb
Setup P3 next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Setup P3 this skilluzairansaruzi/p3-stack | 143 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Configure Channelopenclaw/openclaw | 392k | — | ~946 | Automated safety check: Pass | MIT | |
| ConfigurationBuilderIO/agent-native | 7.1k | — | ~2.1k | Automated safety check: Pass | None | |
| Aria Rolesthedaviddias/Front-End-Checklist | 74k | — | ~515 | Automated safety check: Pass | MIT | |
| Configure Eccaffaan-m/ECC | 276k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Configure Eccaffaan-m/ECC | 276k | — | ~1.3k | Automated safety check: Pass | MIT |
openclaw/openclaw
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
BuilderIO/agent-native
Where a configuration value belongs — app config schema, agent-native.config.ts, or an environment variable — and how the layers resolve.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Use valid ARIA role values.
affaan-m/ECC
Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's…
affaan-m/ECC
Claude Code、Codex、Kimi 内で ECC のインストール、更新、再設定を案内し、各ハーネスが実際に備えるプラグイン、スコープ、フック機能を守ります。
affaan-m/ECC
在 Claude Code、Codex 或 Kimi 内引导 ECC 安装、更新或重新配置,同时严格遵守各家工具真实的插件、范围和 Hook 能力。
uzairansaruzi/p3-stack
Delegate three parallel reviewers over the active thread, surface learnings, and route each to a concrete edit on an existing skill.
uzairansaruzi/p3-stack
Guides users through p3-stack setup, /p3-mode, and picking the skill, playbook, or principle for a task.
uzairansaruzi/p3-stack
p3 agent style for concise, detailed responses, deliberate delegation, unslopped prose, simple code, and verified work.
Configure which models p3-stack uses per role and at what reasoning budget. Setup P3 is an agent skill from uzairansaruzi/p3-stack. Configure which models p3-stack uses per role and at what reasoning budget.
Setup P3 fits situations like: configure p3 models; changing p3-stacks model choices.
Run `npx skills add uzairansaruzi/p3-stack --skill setup-p3 -a claude-code`. Or copy the skill folder (skills/setup-p3 in uzairansaruzi/p3-stack) into .claude/skills/setup-p3 in your project. Claude Code loads it when a task matches its description.
Run `npx skills add uzairansaruzi/p3-stack --skill setup-p3 -a codex`. Or copy the skill folder (skills/setup-p3 in uzairansaruzi/p3-stack) into .agents/skills/setup-p3 in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add uzairansaruzi/p3-stack --skill setup-p3 -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setup-p3, .gemini/skills/setup-p3, .github/skills/setup-p3 and .opencode/skills/setup-p3 in your project.
SKILL.md names no scripts, command-line tools or credentials: Setup P3 is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Setup P3 is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Setup P3: Configure Channel (openclaw/openclaw, 392k stars), Configuration (BuilderIO/agent-native, 7.1k stars), Aria Roles (thedaviddias/Front-End-Checklist, 74k stars) and Configure Ecc (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
uzairansaruzi (a GitHub user) maintains it in uzairansaruzi/p3-stack, which has 143 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 5, 2026.
Source: uzairansaruzi/p3-stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.