AC openclaw-geo-content-ops
Use when Ray asks to design, operate, audit, or improve OpenClaw GEO content operations beyond single-article writing: knowledge sources, topic clusters, content tasks, publish targets, llms.txt, schema, multi-site distribution, receipts, AI crawler visibility, or GEO analytics.
As a process C 57/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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Use when Ray asks to design, operate, audit, or improve OpenClaw G… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 57/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-geo-content-ops) differs from the folder (geo-content-ops)
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 85Steps. 51 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1890 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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
- +2Single-language instructions
- +3Description length 279: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 51 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.