smithery.ai

anviloop-deck

Design and write Anviloop nightly deck JSONs that set direction, jobs, and polish tasks for a cycle. Use when the user asks to create a deck, choose nightly direction, or plan nightly tasks.

First seen Mar 28, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,581 B
  • docs SUMMARY.md 211 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Anviloop Deck Builder

Purpose

Create a deck JSON for Polish/run_deck.ps1 that defines the nightly direction, jobs, and polish tasks while respecting Nightly Protocol rules.

Inputs to consult

  • C:/Dev/unityclean/headlessrebuildtool/Polish/rundeck.ps1
  • C:/Dev/unityclean/headlessrebuildtool/Polish/pipelinedefaults.json
  • C:/Dev/unityclean/headlessrebuildtool/Polish/Docs/NIGHTLYPROTOCOL.md
  • C:/Dev/unityclean/headlessrebuildtool/Polish/Docs/ANVILOOPRECURRING_ERRORS.md
  • C:/Dev/unityclean/headlessrebuildtool/Polish/Docs/MORNINGVIEW.md

Guardrails (must follow)

  • Single-variable rule: do not change scenario and code in the same cycle.
  • If a failure signature repeats twice, consult the ledger before changing code.
  • Pins must exist in all requested repos (space4x, godgame) to avoid pathspec errors.

Deck design steps

  1. Choose a single nightly direction:

- Set one primary goalid or scenarioid. - Decide if the cycle is code-only or scenario-only.

  1. Select jobs:

- Use pipeline_defaults.json for defaults (title, scenario, seed, timeout, args). - Add overrides only when necessary.

  1. Apply risk checks:

- Scan the ledger for matching signatures. - Avoid scenarios with known unstable signatures unless explicitly testing a fix.

  1. Set queue + timing:

- Use C:/polish/queue unless instructed otherwise. - Keep pollsec, pendinggracesec, maxminutes aligned to expected run time.

Deck JSON template (minimal)

{
  "queue_root": "C:/polish/queue",
  "poll_sec": 60,
  "pending_grace_sec": 600,
  "max_minutes": 720,
  "jobs": [
    {
      "title": "space4x",
      "scenario_id": "space4x_collision_micro",
      "scenario_rel": "Assets/Scenarios/space4x_collision_micro.json",
      "seed": 7,
      "timeout_sec": 90,
      "repeat": 1,
      "goal_id": "ARC",
      "goal_spec": "Polish/Goals/arc_goal.json",
      "base_ref": "origin/main",
      "required_bank": "BANK_PASS",
      "args": ["--telemetryEnabled", "1"]
    }
  ]
}

Output format (concise)

When asked to create a deck, respond with:

Direction: <goal_id/scenario_id + code-only or scenario-only>
Jobs: <count + titles + repeats>
Risks: <ledger matches or INVALID gates>
Deck: <JSON>