CD oz-upload-file
Upload a local file to the Oz platform as a conversation artifact.
The skill promises to upload local files to the Oz platform as conversation artifacts. One instruction file, 200 tokens, no scripts, no critical errors. Code quality scored at 62, process at 42. No model runs or sandbox tests performed.
Functionality is basic: the skill just sends the file to the platform. No medium or low-severity issues found, but no working proof either. Install if you need minimal Oz integration and can test it yourself on your model.
Upload a local file to the Oz platform as a conversation artifact.
As a process D 42/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 42/100
- 0Steps. Prose only: no discrete steps
- 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
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 200 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 66: 120–800 characters recommended
- +4Structure: 0 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.