AgentStack
SKILL verified MIT Self-run

Run Parity Test G

skill-gustavo-meilus-superpipelines-run-parity-test-g · by gustavo-meilus

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.

No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-gustavo-meilus-superpipelines-run-parity-test-g

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Run Parity Test G? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

run-parity-test-g — Entry Skill

> Entry point for the parity-test-g pipeline. Orchestrates the sequential inline execution of the tokenizer and reporter protocol steps on Tier 2 (Cursor/Windsurf/Cline). All steps execute in this skill's session — no subagents, no Task() calls.

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.

Platform Context

  • Tier: tier_2 (Cursor/Windsurf/Cline)
  • Dispatch mechanism: inline — no Task() primitive, no subagent processes. Both steps execute within this skill's session.
  • modelfieldformat: omit — no model: 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

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:

  1. Resolve {ROOT} via sk-pipeline-paths (scope root resolved from the active tier profile at runtime — NEVER hardcode .superpipelines/, .cursor/, .claude/, or any platform path).
  2. Resolve {runId} = ISO-8601 compact timestamp (e.g., 20260526T143000Z).
  3. Create temp directory: {ROOT}/superpipelines/temp/parity-test-g/{runId}/.
  4. 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 → update pipeline-state.json phases[0].status = "completed"; advance to Phase 2.
  • DONE_WITH_CONCERNS → update phases[0].status = "completedwithconcerns"; 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 = "completedwithconcerns"; 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

  1. Update pipeline-state.json:
  • status: "completed" (or "completed_with_concerns" if any phase had concerns)
  • completed_at: ISO-8601 timestamp
  1. Cleanup contract (C20):
  • On DONE or DONE_WITH_CONCERNS: write status: completed to pipeline-state.json, then delete the temp directory {ROOT}/superpipelines/temp/parity-test-g/{runId}/.
  • On BLOCKED or NEEDS_CONTEXT: preserve the temp directory (do NOT delete); it holds resume state for diagnosis.
  1. Confirm to the user:

> Pipeline parity-test-g completed. Word frequency report written to: {ROOT}/output/parity-test-g-word-freq.txt

  1. Emit terminal status: DONE (or DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT as applicable).
  • NEVER call Task() — Tier 2 has task_primitive: false and subagents: false. All execution is inline.
  • NEVER emit a model: field for any step — model_field_format: omit; host IDE owns model selection.
  • NEVER hardcode platform paths (.superpipelines/, .cursor/, .claude/, etc.) — always use {ROOT} resolved via sk-pipeline-paths.
  • NEVER pass file contents in execution context — pass file paths only (anti-pattern #3 Context Dumping).
  • ALWAYS surface all 3 Tier 2 degradation warnings before any execution begins (Phase 0.1 is mandatory).
  • ALWAYS update pipeline-state.json after each phase completes.
  • NEVER advance past a BLOCKED or NEEDS_CONTEXT status without human input.
  • ALWAYS apply the C20 cleanup contract: delete temp dir on DONE/DONEWITHCONCERNS, preserve on BLOCKED/NEEDS_CONTEXT.
  • Emit exactly one terminal status at the end of this skill's own execution: DONE / DONEWITHCONCERNS / NEEDS_CONTEXT / BLOCKED.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.