메뉴
Run one verified, scored improvement tick and write its receipt. Use when the user asks to improve, make this better, ship one thing, run a tick, or get smarter. `atris improve` alone shows metabolism vitals; use `atris improve tick` to ship work.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | improve |
| description | Run one verified, scored improvement tick and write its receipt. Use when the user asks to improve, make this better, ship one thing, run a tick, or get smarter. `atris improve` alone shows metabolism vitals; use `atris improve tick` to ship work. |
| version | 1.1.0 |
| tags | ["rl","improve","reward","tick","autopilot"] |
Run one improvement tick on the workspace. A successful tick ships one result, passes a real verifier, receives a score, and writes a machine-readable scorecard.
One call means one verifiable result. Never turn one invocation into a hidden batch.
atris improve alone shows the self-improvement metabolism vitals. It does not ship a change.
Use the explicit tick subcommand when the user asks for improvement work:
atris improve tick # one full tick: plan, build, verify, score
atris improve tick --json # the same tick as machine-readable output
atris improve tick plan # plan only; no change or receipt
atris improve tick --dry-run # execute without committing; no shipping receipt
atris improve tick --no-fallback # report API failure instead of running locally
atris improve history # reward trend, credits, and pass rate
atris improve # vitals only
atris improve --json # vitals only as JSON
atris improve tick, adding --json only when structured output is useful.ok is true, verification passed, and the scorecard was written.For a paid API tick, the CLI:
utils/auth.loadCredentials.POST /api/improve with the workspace, mode, model, and dry-run setting..atris/state/scorecards.jsonl and the human trail to the daily Atris journal.The full response may omit the billed credit count. In that case the CLI reports that billing happened server-side instead of inventing a number.
Local fallback is allowed when there is no login, the backend is unreachable, or the hosted backend cannot access the local workspace path. The CLI runs this exact bounded command internally:
atris mission run --due --headless --max-ticks 1 --complete-on-pass --json
The local result succeeds only when all of these are true:
A verified local tick earns the conservative local reward of +1 and deducts no credits. No due headless mission, a skipped worker, a failed or missing verifier, or a receipt write failure makes the improve command fail without a reward.
Do not silently fall back for answerable API failures such as insufficient credits, unrelated authorization failures, or server errors.
User says: "Improve this once."
Action: run atris improve tick.
Expected shape:
improved.
task: fixed the stale wiki reference
verify: pass
reward: 4
files: atris/wiki/auth-flow.md
scorecard: .atris/state/scorecards.jsonl
For local fallback, the first line is improved (local fallback). and the report still names the task, passing verifier, reward, and scorecard.
Frontend aesthetics policy. Use when building UI, components, landing pages, dashboards, or any frontend work. Prevents generic ai-generated look.
Backward partner to /flow. Picks the next horizon from inbox + wiki + lessons, writes the reverse path as tagged tasks to TODO.md so /autopilot can pursue it tick by tick. Triggers on: endgame, what's the last move, where are we heading, reverse engineer, work backward.
Dispatch coding work to an installed terminal agent — Codex, Cursor, Devin, Grok, or Atris Fast — as an interchangeable worker engine. Claude orchestrates: writes the bounded prompt, the engine builds, Claude verifies and lands. Triggers on: use codex, use cursor, use devin, use grok, use atris, engine, dispatch to, worker agent, second opinion build.
Working method distilled from Claude Fable 5 for daily-driver models (Opus, Sonnet). Use at session start, before any multi-step task, or when output feels shallow, hedged, or prematurely "done". Triggers on fable method, think like fable, deep pass.
Use the Render.com CLI v2.x (`render`) to inspect Render services, check CLI auth, list services and deploys, trigger deploys when explicitly requested, and view logs. Use when an agent needs Render CLI commands, non-interactive flags, deploy status polling, or service auto-deploy checks.
Install and use Atris as an on-disk brain for agent work. Use when starting in any repo, navigating code, claiming tasks, proving work, or running missions that should survive the session.