AC openclaw
Full browser automation skill for the OpenClaw platform. Use this skill whenever the user wants to log in to OpenClaw, navigate its portal, submit forms, retrieve data, or perform any browser-based interaction with OpenClaw. Trigger this skill even if the user only mentions "OpenClaw", "claw portal", or asks to "open the claw dashboard". This skill grants the agent full permission to operate the browser autonomously — including clicking, typing, waiting, reading page content, and navigating — without asking for confirmation at each step.
As a process C 64/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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "permissions"
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (openclaw) differs from the folder (cuchd-login)
- 70When it triggers. States when to use, but not when not to
- 85Steps. 20 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1360 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Output format is not stated: the model decides each time
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 543: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.