AD codex-run-to-completion
Autonomous Codex run-to-completion workflow for low quota/cota situations. Use when the user asks for an uninterrupted agent run, says "nao me peca confirmacao", "nao trave", "nao pare", "rode ate o final", or wants Codex to self-manage terminal waits, sleep, polling, long-running commands, tests, builds, and verification instead of stopping for avoidable questions.
Autonomous Codex run-to-completion workflow for low quota/cota situations.
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 13 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 552 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 368: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 13 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.