AC genesis-ouroboros
Genesis constitution and scaffold generator for creating a new self-evolving agent. Use when the user asks to create, birth, or scaffold a new agent (e.g. via $genesis-ouroboros followed by agent requirements; Chinese triggers include 创建/孵化/脚手架一个新 agent), especially setups where AGENTS.md/CLAUDE.md serve as a constitution, skills act as evolving pipeline stations, experience is distilled after every interaction, and mature workflows crystallize into scripts.
Genesis constitution and scaffold generator for creating a new self-evolving agent.
As a process C 50/100 · Has gaps — 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 50/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
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 48 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2118 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +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
- +3Description length 462: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 48 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.