slate-ar

Wraps Codex Autoresearch measured loops with Slate v2 routing, session state, and operator modes.

16.5k|997|Updated Dec 2, 2019
One-click install
npx skills add https://github.com/udecode/plate --skill slate-ar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slate-ar
Source: https://github.com/udecode/plate/tree/main/.agents/skills/slate-ar
Command: npx skills add https://github.com/udecode/plate --skill slate-ar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running measured Autoresearch loops against Slate v2 requires consistent session state, correctness routing, and dashboard discipline that generic tooling does not provide, leading to lost packets and unmeasured regressions.

Core Features & Use Cases

  • Slate v2 Loop Defaults: Pins the working directory to .tmp/slate-v2, manages autoresearch.* session files, and enforces keep/discard decisions based on Slate correctness checks.
  • Operator Routing: Routes short commands like continue, status, finalize, research, gate, and perfect to the correct specialized wrapper skill such as slate-ar-perf, slate-ar-gate, or slate-patch.
  • Finalization Discipline: Runs preview-only finalization by default and requires explicit user approval before creating review branches, commits, or PRs.
  • Use Case: A developer iterating on Slate v2 editor behavior invokes slate-ar continue to resume a measured loop, review kept versus discarded packets, and get the next recommended packet without re-initializing state.

Quick Start

Ask the assistant to continue the current Slate v2 Autoresearch session and report status, baseline, and the next recommended packet.

Frequently Asked Questions about slate-ar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a measured Autoresearch loop on Slate v2?

Invoke slate-ar with a target or use `continue` to resume an existing session. It pins the working directory to `.tmp/slate-v2`, reads existing `autoresearch.*` session files, and delegates packet mechanics to codex-autoresearch.

What is the difference between slate-ar and slate-ar-perf?

slate-ar owns generic measured loops, status, research, and finalization for Slate v2. slate-ar-perf handles performance-specific work like benchmarks, pagination, and virtualization with its own target registry and stop rules.

When should I use slate-patch instead of slate-ar?

Use slate-patch when the bug is a direct correctness failure with no existing oracle. slate-ar is for measured loops and quality-gap work; correctness repairs without oracles route to slate-patch first.

Does slate-ar create review branches or commits automatically?

No. Finalization defaults to preview-only mode. Branch creation, cleanup, commits, pushes, and PR work all require explicit user approval in the same turn; short confirmations like `go` or `continue` do not count.

How does slate-ar decide to keep or discard a packet?

A packet is kept only when the measured target improves and Slate correctness checks pass. Regressions in selection, IME, copy, paste, undo, focus, or browser behavior force checks_failed or discard regardless of metric gains.