Run parity test g
Skill gustavo-meilus/superpipelines/.superpipelines/skills/superpipelines/parity-test-g/run-parity-test-g
Use when the user wants to run the parity-test-g pipeline on Tier 2 (Cursor/Windsurf/Cline) to tokenize a markdown file and produce a top-20 word frequency report.From its SKILL.md
npx -y skills add gustavo-meilus/superpipelines --skill run-parity-test-gAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
7.5 KB, ~1.9k tokens by cl100k_base, as published. Nobody here has run it
run-parity-test-g — Entry Skill
<overview> This skill initializes the pipeline run, resolves the scope root and run ID, surfaces all required Tier 2 degradation warnings, executes the tokenizer and reporter protocol skills inline (same session, sequential), and applies the cleanup contract (C20) on completion. Model is inherit throughout — the host IDE owns model selection. </overview>Entry point for the
parity-test-gpipeline. Orchestrates the sequential inline execution of thetokenizerandreporterprotocol steps on Tier 2 (Cursor/Windsurf/Cline). All steps execute in this skill's session — no subagents, no Task() calls.
Platform Context
- Tier:
tier_2(Cursor/Windsurf/Cline) - Dispatch mechanism:
inline— noTask()primitive, no subagent processes. Both steps execute within this skill's session. - model_field_format:
omit— nomodel:field is emitted for any step. The host IDE owns model selection. - Reviewer isolation:
convention— no structural isolation. Self-skepticism preamble required in any reviewer protocol. - Degradation warnings: 3 active (see PHASE 0 below).
Workflow
<protocol>PHASE 0: PREFLIGHT — DEGRADATION WARNINGS AND INITIALIZATION
Step 0.1 — Surface Tier 2 degradation warnings (MANDATORY before any execution):
Surface ALL of the following warnings to the user verbatim before any other action:
[Tier 2 Degradation Warning 1 of 3] Reviewer isolation impossible on this platform: writer and reviewer are the same agent in the same context. Review steps execute the reviewer protocol but cannot provide assumption-blindness defense or context-bleed isolation. Treat review output as a self-check, not verification.
[Tier 2 Degradation Warning 2 of 3] Parallel fan-out (Pattern 2) requires worktrees and is unavailable on this platform (worktrees: false).
[Tier 2 Degradation Warning 3 of 3] Model selection is owned by the host IDE; per-step model assignment is not emitted.
Step 0.2 — Resolve runtime context:
- Resolve
{ROOT}viask-pipeline-paths(scope root resolved from the active tier profile at runtime — NEVER hardcode.superpipelines/,.cursor/,.claude/, or any platform path). - Resolve
{runId}= ISO-8601 compact timestamp (e.g.,20260526T143000Z). - Create temp directory:
{ROOT}/superpipelines/temp/parity-test-g/{runId}/. - Create
output/directory if absent:{ROOT}/output/.
Step 0.3 — Collect inputs:
If the user has not supplied the path to the input markdown file, ask for it now. Record as {INPUT_PATH}.
Step 0.4 — Initialize pipeline-state.json:
Write pipeline-state.json to {ROOT}/superpipelines/temp/parity-test-g/{runId}/pipeline-state.json:
{
"pipeline_id": "parity-test-g",
"run_id": "{runId}",
"started_at": "{iso8601}",
"plugin_version": "2.0.0",
"pattern": "1",
"status": "running",
"current_phase": 0,
"metadata": {
"source_tier": "tier_2",
"runtime_tier": "tier_2",
"model_field_format": "omit",
"resolved_models": {}
},
"phases": [
{
"index": 0,
"step_id": "tokenizer",
"name": "tokenize",
"status": "pending",
"agent": null,
"outputs": [],
"error": null
},
{
"index": 1,
"step_id": "reporter",
"name": "report",
"status": "pending",
"agent": null,
"outputs": [],
"error": null
}
]
}
Note: agent is null in both phases — Tier 2 has no agent files.
PHASE 1: EXECUTE TOKENIZER (inline)
Load protocol skill into context:
Protocol: {ROOT}/skills/superpipelines/parity-test-g/tokenizer-protocol/SKILL.md
Execute the tokenizer protocol inline (same session) with the following context:
input_path: {INPUT_PATH}
counts_output_path: {ROOT}/superpipelines/temp/parity-test-g/{runId}/frequency-counts.json
state_path: {ROOT}/superpipelines/temp/parity-test-g/{runId}/pipeline-state.json
run_id: {runId}
root: {ROOT}
Wait for terminal status from the tokenizer protocol:
DONE→ updatepipeline-state.jsonphases[0].status = "completed"; advance to Phase 2.DONE_WITH_CONCERNS→ update phases[0].status = "completed_with_concerns"; surface concerns to user; advance to Phase 2.NEEDS_CONTEXT→ update phases[0].status = "blocked"; update top-level status = "blocked"; surface message to user; GO TO CLEANUP (preserve).BLOCKED→ update phases[0].status = "blocked"; update top-level status = "blocked"; surface message to user; GO TO CLEANUP (preserve).
PHASE 2: EXECUTE REPORTER (inline)
Load protocol skill into context:
Protocol: {ROOT}/skills/superpipelines/parity-test-g/reporter-protocol/SKILL.md
Execute the reporter protocol inline (same session) with the following context:
counts_path: {ROOT}/superpipelines/temp/parity-test-g/{runId}/frequency-counts.json
output_path: {ROOT}/output/parity-test-g-word-freq.txt
state_path: {ROOT}/superpipelines/temp/parity-test-g/{runId}/pipeline-state.json
run_id: {runId}
root: {ROOT}
Wait for terminal status from the reporter protocol:
DONE→ update phases[1].status = "completed"; advance to Phase 3.DONE_WITH_CONCERNS→ update phases[1].status = "completed_with_concerns"; surface concerns to user; advance to Phase 3.NEEDS_CONTEXT→ update phases[1].status = "blocked"; update top-level status = "blocked"; surface message to user; GO TO CLEANUP (preserve).BLOCKED→ update phases[1].status = "blocked"; update top-level status = "blocked"; surface message to user; GO TO CLEANUP (preserve).
PHASE 3: FINALIZE
-
Update
pipeline-state.json:status:"completed"(or"completed_with_concerns"if any phase had concerns)completed_at: ISO-8601 timestamp
-
Cleanup contract (C20):
- On
DONEorDONE_WITH_CONCERNS: writestatus: completedtopipeline-state.json, then delete the temp directory{ROOT}/superpipelines/temp/parity-test-g/{runId}/. - On
BLOCKEDorNEEDS_CONTEXT: preserve the temp directory (do NOT delete); it holds resume state for diagnosis.
- On
-
Confirm to the user:
Pipeline
parity-test-gcompleted. Word frequency report written to:{ROOT}/output/parity-test-g-word-freq.txt -
Emit terminal status:
DONE(orDONE_WITH_CONCERNS/BLOCKED/NEEDS_CONTEXTas applicable).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.