.agents/skills/slate-ar-recipe/SKILL.md
Handle $ARGUMENTS by loading slate-ar and using Codex Autoresearch recipes.
Use this when the user asks what Autoresearch loop to run, or when a task is measured but not obviously performance-specific.
recipes recommend, recipes list, recipes show, and
setup-plan..tmp/slate-v2.node-test-runtime.node-test-runtime / vitest-runtime: test gate repeatability. Often route
to slate-ar-gate.typescript-compile-time: typecheck/runtime graph pressure.bundle-size: package or site bundle footprint.memory-usage: workload memory smoke, after replacing the placeholder with
the real workload.command-latency: custom command duration, after replacing the placeholder.quality-gap: broad research checklist. Usually route to slate-ar-quality.custom: last resort when no built-in recipe fits.Use direct CLI until a root shortcut exists:
node ../codex-autoresearch/plugins/codex-autoresearch/scripts/autoresearch.mjs recipes list --cwd .tmp/slate-v2
node ../codex-autoresearch/plugins/codex-autoresearch/scripts/autoresearch.mjs recipes recommend --cwd .tmp/slate-v2
node ../codex-autoresearch/plugins/codex-autoresearch/scripts/autoresearch.mjs recipes show <recipe-id> --cwd .tmp/slate-v2
node ../codex-autoresearch/plugins/codex-autoresearch/scripts/autoresearch.mjs setup-plan --cwd .tmp/slate-v2 --recipe <recipe-id>
node ../codex-autoresearch/plugins/codex-autoresearch/scripts/autoresearch.mjs doctor --cwd .tmp/slate-v2 --check-benchmark --explain
If the recipe output is customized, run benchmark-lint before any packet.
Report the selected recipe, metric, direction, benchmark command, checks
command, caveats, and recommended owner: slate-ar, slate-ar-quality,
slate-ar-gate, slate-ar-perf, slate-patch, or slate-plan.