CD setup-pstack
Configure which models pstack uses per role. Detects available models and writes the current runtime's override sheet. Use for /setup-pstack, "configure pstack models", changing pstack's model choices, or turning the SessionStart hook on or off.
Configure which models pstack uses per role.
As a process D 43/100 · Unfinished process — References files that are not bundled: ../poteto-mode/references/codex-tools.md, ../poteto-mode/references/copilot-tools.md, ../poteto-mode/references/muse-tools.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../poteto-mode/references/codex-tools.md - warning
missing-refreference to a missing file: ../poteto-mode/references/copilot-tools.md - warning
missing-refreference to a missing file: ../poteto-mode/references/muse-tools.md - warning
missing-refreference to a missing file: ../create-verification-skill/SKILL.md - warning
missing-refreference to a missing file: ../create-formal-verification-skill/SKILL.md - warning
missing-refreference to a missing file: ../poteto-mode/references/codex-tools.md - warning
missing-refreference to a missing file: ../poteto-mode/references/pi-tools.md - warning
missing-refreference to a missing file: ../poteto-mode/references/copilot-tools.md - warning
missing-refreference to a missing file: ../poteto-mode/references/muse-tools.md
Process rating: all ten parameters 43/100
- 0Tools and files. 9 referenced file(s) missing: ../poteto-mode/references/codex-tools.md, ../poteto-mode/references/copilot-tools.md, ../poteto-mode/references/muse-tools.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3119 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low The response is described with custom markup (13 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 245: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.