AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Run Parity Test J

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

Use when the user wants to run the parity-test-j pipeline on Tier 1b (OpenCode) to read a CSV file and produce a markdown data quality document listing columns with nulls, outliers, and type inconsistencies.

— No reviews yet
0 installs
31 views
0.0% view→install

Install

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

✓ 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-gustavo-meilus-superpipelines-run-parity-test-j)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Run Parity Test J? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

run-parity-test-j — Entry Skill

> Entry point for the parity-test-j pipeline. Orchestrates the sequential native-subagent dispatch of the analyzer, reviewer, and reporter agents on Tier 1b (OpenCode v1.15.10). Each step runs as a distinct subagent process — no inline execution, no Task() calls.

This skill initializes the pipeline run, resolves the scope root and run ID, surfaces the required Tier 1b degradation warning, dispatches the analyzer subagent, dispatches the reviewer subagent (structural isolation: plan + disallowedTools), dispatches the reporter subagent (only on approved verdict), and applies the cleanup contract (C20) on completion. Model is declared per-agent in frontmatter (opencode/big-pickle); the entry skill itself uses disable-model-invocation: true.

Platform Context

  • Tier: tier_1b (OpenCode v1.15.10)
  • Dispatch mechanism: native_subagent — DISPATCH(mode="subagent", agent="{name}", context={...}). NOT Task(). NOT inline.
  • modelfieldformat: provider_prefixed — model: opencode/big-pickle declared in each agent's YAML frontmatter.
  • Reviewer isolation: structural — reviewer runs with permissionMode: plan + disallowedTools: Write, Edit, Bash.
  • Degradation warnings: 1 active (see PHASE 0 below).

DEGRADATION WARNINGS (Tier 1b — Active)

The following warning from the tier_1b platform profile MUST be surfaced before execution:

  1. Parallel fan-out (Pattern 2) degrades to sequential on OpenCode.

Workflow

PHASE 0: PREFLIGHT — DEGRADATION WARNING AND INITIALIZATION

Step 0.1 — Surface Tier 1b degradation warning (MANDATORY before any execution):

Surface the following warning to the user verbatim before any other action:

> [Tier 1b Degradation Warning 1 of 1] Parallel fan-out (Pattern 2) degrades to sequential on OpenCode.

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 .opencode/, .superpipelines/, .claude/, or any platform path).
  2. Resolve {runId} = ISO-8601 compact timestamp (e.g., 20260526T143000Z).
  3. Create temp directory: {ROOT}/superpipelines/temp/parity-test-j/{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 CSV 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-j/{runId}/pipeline-state.json:

{
  "pipeline_id": "parity-test-j",
  "run_id": "{runId}",
  "started_at": "{iso8601}",
  "plugin_version": "2.0.0",
  "pattern": "1",
  "status": "running",
  "current_phase": 0,
  "metadata": {
    "source_tier": "tier_1b",
    "runtime_tier": "tier_1b",
    "model_field_format": "provider_prefixed",
    "resolved_models": {
      "analyzer": "opencode/big-pickle",
      "reviewer": "opencode/big-pickle",
      "reporter": "opencode/big-pickle"
    }
  },
  "phases": [
    {
      "index": 0,
      "step_id": "analyzer",
      "name": "analyze",
      "status": "pending",
      "agent": "agents/superpipelines/parity-test-j/analyzer.md",
      "outputs": [],
      "error": null
    },
    {
      "index": 1,
      "step_id": "reviewer",
      "name": "review",
      "status": "pending",
      "agent": "agents/superpipelines/parity-test-j/reviewer.md",
      "reviewer_isolation": "structural",
      "outputs": [],
      "error": null
    },
    {
      "index": 2,
      "step_id": "reporter",
      "name": "render",
      "status": "pending",
      "agent": "agents/superpipelines/parity-test-j/reporter.md",
      "outputs": [],
      "error": null
    }
  ]
}

PHASE 1: DISPATCH ANALYZER (native subagent)

Dispatch the analyzer as a native subagent:

DISPATCH(
  mode="subagent",
  agent="analyzer",
  context={
    "input_path": "{INPUT_PATH}",
    "findings_output_path": "{ROOT}/superpipelines/temp/parity-test-j/{runId}/findings.json",
    "state_path": "{ROOT}/superpipelines/temp/parity-test-j/{runId}/pipeline-state.json",
    "run_id": "{runId}",
    "root": "{ROOT}"
  }
)

Wait for terminal status from the analyzer subagent:

  • 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: DISPATCH REVIEWER (native subagent — structural isolation)

Dispatch the reviewer as a native subagent. The reviewer has permissionMode: plan and disallowedTools: Write, Edit, Bash — it cannot write files. Capture the REVIEWER VERDICT block from its terminal output text.

DISPATCH(
  mode="subagent",
  agent="reviewer",
  context={
    "findings_path": "{ROOT}/superpipelines/temp/parity-test-j/{runId}/findings.json",
    "state_path": "{ROOT}/superpipelines/temp/parity-test-j/{runId}/pipeline-state.json",
    "run_id": "{runId}",
    "root": "{ROOT}"
  }
)

After the reviewer subagent completes:

  1. Extract the REVIEWER VERDICT block from the reviewer's terminal output text. Record as {REVIEWER_OUTPUT}.
  2. Parse verdict from the block: approved, approved_with_concerns, or rejected.
  3. Update pipeline-state.json:
  • phases[1].outputs → [{ "verdict": "{verdict}", "reviewer_notes": "{REVIEWER_OUTPUT}" }]

Wait for terminal status:

  • DONE (verdict: approved) → update phases[1].status = "completed"; advance to Phase 3.
  • DONE_WITH_CONCERNS (verdict: approvedwithconcerns) → update phases[1].status = "completedwithconcerns"; surface concerns; advance to Phase 3.
  • BLOCKED (verdict: rejected or validation failure) → update phases[1].status = "blocked"; update top-level status = "blocked"; surface rejection message; GO TO CLEANUP (preserve). DO NOT dispatch reporter.
  • NEEDS_CONTEXT → update phases[1].status = "blocked"; update top-level status = "blocked"; GO TO CLEANUP (preserve).

PHASE 3: DISPATCH REPORTER (native subagent)

Only dispatched if reviewer verdict is approved or approved_with_concerns.

DISPATCH(
  mode="subagent",
  agent="reporter",
  context={
    "findings_path": "{ROOT}/superpipelines/temp/parity-test-j/{runId}/findings.json",
    "reviewer_verdict": "{verdict}",
    "reviewer_notes": "{REVIEWER_OUTPUT}",
    "report_output_path": "{ROOT}/output/parity-test-j-report.md",
    "state_path": "{ROOT}/superpipelines/temp/parity-test-j/{runId}/pipeline-state.json",
    "run_id": "{runId}",
    "root": "{ROOT}"
  }
)

Wait for terminal status from the reporter subagent:

  • DONE → update pipeline-state.json phases[2].status = "completed"; advance to Phase 4.
  • DONE_WITH_CONCERNS → update phases[2].status = "completedwithconcerns"; surface concerns to user; advance to Phase 4.
  • NEEDS_CONTEXT → update phases[2].status = "blocked"; update top-level status = "blocked"; GO TO CLEANUP (preserve).
  • BLOCKED → update phases[2].status = "blocked"; update top-level status = "blocked"; surface message; GO TO CLEANUP (preserve).

PHASE 4: 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-j/{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-j completed. Data quality document written to: {ROOT}/output/parity-test-j-report.md

  1. Emit terminal status: DONE (or DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT as applicable).
  • NEVER call Task() — Tier 1b has task_primitive: false. Use DISPATCH(mode="subagent", ...) exclusively.
  • NEVER execute steps inline — each step MUST run as a distinct native subagent process.
  • NEVER hardcode platform paths (.opencode/, .superpipelines/, .claude/, etc.) — always use {ROOT} resolved via sk-pipeline-paths.
  • NEVER pass file contents in dispatch context — pass file paths only (anti-pattern #3 Context Dumping).
  • NEVER dispatch the reporter if the reviewer verdict is rejected or the reviewer emits BLOCKED.
  • ALWAYS surface the Tier 1b degradation warning before any execution begins (Phase 0.1 is mandatory).
  • ALWAYS capture the REVIEWER VERDICT block from the reviewer's terminal output before advancing.
  • 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.