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

Run Parity Test C

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

Use when the user wants to run the parity-test-c pipeline on Tier 1c (Antigravity CLI) to analyze a text document and produce a structured markdown summary.

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

Install

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

✓ 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-c)

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 C? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

run-parity-test-c — Entry Skill

> Entry point for the parity-test-c pipeline. Orchestrates the sequential dispatch of analyzer and summarizer agents on Tier 1c (Antigravity CLI) via model_driven dispatch.

This skill initializes the pipeline run, surfaces Tier 1c degradation warnings, dispatches the analyzer and summarizer agents in sequence via the model_driven path of sk-platform-dispatch, and confirms the output file location on completion.

Platform Context

  • Tier: tier_1c (Antigravity CLI)
  • Dispatch mechanism: model_driven — the host orchestrator drives subagent sequencing; no Task() primitive available.
  • modelfieldformat: omit — agents do not declare model: or model_tier: in their dispatch prompts; the host owns model selection.
  • Degradation warning (MUST surface before execution):

> "Antigravity uses dynamic subagents — per-step model assignment is not supported. Only the orchestrator's model tier is user-configurable. Subagent model selection is owned by Antigravity's orchestrator."

Workflow

PHASE 0: PREFLIGHT

  1. Emit the Tier 1c degradation warning above.
  2. Resolve {ROOT} via sk-pipeline-paths (the scope root for tier_1c is the .agents/antigravity subdirectory of the workspace root — resolved at runtime, never hardcoded).
  3. Resolve {runId} = ISO-8601 timestamp (e.g., 20260526T143000Z).
  4. Create temp directory: {ROOT}/superpipelines/temp/parity-test-c/{runId}/.
  5. Create output/ directory if absent: {ROOT}/output/.
  6. Initialize pipeline-state.json at {ROOT}/superpipelines/temp/parity-test-c/{runId}/pipeline-state.json:
{
  "pipeline_id": "parity-test-c",
  "run_id": "{runId}",
  "started_at": "{iso8601}",
  "plugin_version": "2.0.0",
  "pattern": "1",
  "status": "running",
  "current_phase": 0,
  "metadata": {
    "source_tier": "tier_1c",
    "runtime_tier": "tier_1c",
    "orchestrator_tier": "medium",
    "resolved_models": {}
  },
  "phases": [
    {
      "index": 0,
      "step_id": "analyzer",
      "name": "analyze",
      "status": "pending",
      "agent": "agents/superpipelines/parity-test-c/analyzer.md",
      "outputs": [],
      "error": null
    },
    {
      "index": 1,
      "step_id": "summarizer",
      "name": "summarize",
      "status": "pending",
      "agent": "agents/superpipelines/parity-test-c/summarizer.md",
      "outputs": [],
      "error": null
    }
  ]
}
  1. Ask the user to provide the path to the input text document if not already supplied. Record as {INPUT_DOC}.

PHASE 1: DISPATCH ANALYZER (model_driven)

DISPATCH via model_driven orchestration:

Agent: analyzer
Protocol: {ROOT}/skills/superpipelines/parity-test-c/analyzer-protocol/SKILL.md
Context to pass:
  - input_document_path: {INPUT_DOC}
  - state_path: {ROOT}/superpipelines/temp/parity-test-c/{runId}/pipeline-state.json
  - findings_output_path: {ROOT}/superpipelines/temp/parity-test-c/{runId}/analyzer-findings.json
  - run_id: {runId}
  - root: {ROOT}

Wait for terminal status from analyzer:

  • DONE → update pipeline-state.json phases[0].status = "completed"; advance to Phase 2.
  • DONE_WITH_CONCERNS → update phases[0].status = "completedwithconcerns"; emit concerns; advance to Phase 2.
  • NEEDS_CONTEXT → update phases[0].status = "blocked"; surface message to user; STOP.
  • BLOCKED → update phases[0].status = "blocked"; surface message to user; STOP.

PHASE 2: DISPATCH SUMMARIZER (model_driven)

DISPATCH via model_driven orchestration:

Agent: summarizer
Protocol: {ROOT}/skills/superpipelines/parity-test-c/summarizer-protocol/SKILL.md
Context to pass:
  - findings_path: {ROOT}/superpipelines/temp/parity-test-c/{runId}/analyzer-findings.json
  - output_path: {ROOT}/output/parity-test-c-summary.md
  - state_path: {ROOT}/superpipelines/temp/parity-test-c/{runId}/pipeline-state.json
  - run_id: {runId}
  - root: {ROOT}

Wait for terminal status from summarizer:

  • DONE → update phases[1].status = "completed"; advance to Phase 3.
  • DONE_WITH_CONCERNS → update phases[1].status = "completedwithconcerns"; emit concerns; advance to Phase 3.
  • NEEDS_CONTEXT → update phases[1].status = "blocked"; surface message to user; STOP.
  • BLOCKED → update phases[1].status = "blocked"; surface message to user; STOP.

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. Delete the temp run directory: {ROOT}/superpipelines/temp/parity-test-c/{runId}/
  • On BLOCKED or NEEDS_CONTEXT: preserve the directory (do NOT delete); it holds resume state.
  1. Confirm to the user:

> Pipeline parity-test-c completed. Summary written to: {ROOT}/output/parity-test-c-summary.md

  • NEVER use Task() — Tier 1c has task_primitive: false. All dispatch is model_driven.
  • NEVER pass file contents in dispatch prompts — pass file paths only (anti-pattern #3 Context Dumping).
  • ALWAYS surface the Tier 1c degradation warning before dispatching any agent.
  • ALWAYS update pipeline-state.json after each phase completes.
  • NEVER advance past a BLOCKED or NEEDS_CONTEXT status without human input.
  • Emit exactly one terminal status at the end of this skill's own execution (not the subagents').

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.