AC continue-codex-work
Continues interrupted OpenAI Codex work only after read-codex-history verifies the selected rollout identity and complete fork/compaction lineage. Use when the user provides a Codex Session ID, asks to pick up a prior Codex run, says Codex was interrupted, fused, compacted, or stuck, or wants the current Agent to take over without `codex resume`. Restores the original business outcome, unfulfilled requests, user corrections, proven prior assets, current workspace truth, and the next action that directly advances the goal. Do not use when Codex itself natively resumed this same conversation and its prior turns or compaction state are already present in the current context.
Continues interrupted OpenAI Codex work only after read-codex-history verifies the selected rollout identity and complete fork/compaction lineage.
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
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: 1. 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 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 15 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1120 tokens
- 100Running it twice. Mutating operations check current state
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
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 680: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 15 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.