FC best-practice-skill-creator
Create OpenClaw skills from best practice videos or image sequences. Use when creating skill from video, generating skill from screenshots, converting tutorial to skill, building best practice automation.
As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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 files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Remove the critical guard findings (secrets, dangerous commands, hidden instructions): while they stand the skill is blocked and cannot grade above F.
- 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 · 6
-
critical Secrets in code
secret-openai-keyconfig.yaml:11OpenAI-style API key (quoted — discussed, not commanded)api_key: "sk-9…nRs"
quoted
Medium and low: 5
-
medium Secrets in code
secret-labelled-tokenconfig.yaml:11Labelled token / key literal (vendor format unknown — verify it is not a live credential)api_key: "sk-9…nRs"
-
medium Exfiltration
net-redirectable-api-keymain.py:88Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Exfiltration
net-redirectable-api-keysrc/config.py:64Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
low Secrets in code
secret-high-entropy-tokenconfig.yaml:11High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)api_key: "sk-9…nRs"
quoted -
low Secrets in code
secret-password-literalconfig.yaml:11Hard-coded password / key literal (may be an example)api_key: "sk-9…nRs"
Files scanned: 17. 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 59/100
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 436 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)
- +1No license
- +2Single-language instructions
- +3Description length 204: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 13 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.