CC onimi-pages
Create and edit Onimi Pages or Slides, validate and preview the result, save private drafts, and publish or manage controlled sharing when requested. Use for Onimi works and local artifacts intended for Onimi.
Create and edit Onimi Pages or Slides, validate and preview the result, save private drafts, and publish or manage controlled sharing when requested.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 1
-
high Concealment
en-hide-from-userreferences/migration.md:10Instruction to hide actions from the useror silently install a second active entrypoint. If the host cannot preserve or restore a
Files scanned: 33. 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 56/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 18 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 819 tokens
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)
- +4Structure: 2 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -37 of 8 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 209: enough signal without eating the budget
- +3Step-by-step instructions: 4 items
- +4Reference files are cited in the instructions (7 of 11)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.