AC omni
The all-in-one master skill — unified interface for every capability domain. Use when the user asks for anything that spans multiple domains or when no single specialized skill clearly applies. Covers: automation & workflows, coding & development, data analysis & databases, web scraping & browsing, finance & accounting, security & hardening, image/video/audio generation & editing, music creation, email & messaging, calendar & scheduling, document processing (PDF/DOCX/PPTX), translation, writing & content creation, project management, deployment & DevOps, IoT & smart home, communication platforms, knowledge management, CLI tools, system administration, API design & testing, and general problem-solving. Triggers on: "do everything", "all in one", "omni", "master skill", "mega skill", or any task where routing to the right domain matters.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 39. 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 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (omni) differs from the folder (omni-master)
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 73 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 2564 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)
- +3Description length 847: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Structure: 19 headings
- +3Step-by-step instructions: 73 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (36 of 36)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.