AC opencreator-skills
Operate and build OpenCreator workflows via API. Use when the user wants to search templates, run workflows, poll results, deliver generated media, or design custom workflow graphs with nodes and edges on OpenCreator. Triggers: opencreator, workflow, template, UGC, ecommerce images, storyboard video, lipsync, content creation pipeline.
As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenreferences/node-catalog.md:616High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"id": "text…2c3",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/node-catalog.md:644High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"id": "cust…ext",
quoted
Files scanned: 48. 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 63/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
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 100Steps. 80 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2105 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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
- +1No license
- +2Single-language instructions
- +3Description length 337: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 80 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.