SKILLEMALL.ai
GitHub ↗ RU Sign in

BF seo-geo-growth-agent

Read-only SEO and GEO opportunity analysis with evidence-backed backlog output.

ClawHub Hermes author: ReplyNodes v1.0.0 MIT-0 5 files body ≈ 1 716 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

Read-only SEO and GEO opportunity analysis with evidence-backed backlog output.

As a process F 38/100 · Will not run — References files that are not bundled: ../../README.md

AnalyzerMarketingOperations and projectsInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
F
38/100
Will not run
References files that are not bundled: ../../README.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
  3. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 79 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • warning missing-ref reference to a missing file: ../../README.md

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: ../../README.md
  • 0Tools and files. 1 referenced file(s) missing: ../../README.md
  • 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. 6 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 60Consistency. The Hermes dialect needs category and tags
  • 100Steps. 35 steps
  • 100Execution cost. Instruction body is 1716 tokens
  • 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

  • +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 79: 120–800 characters recommended
  • +4No input/output examples
  • +2Single-language instructions
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 35 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.

External checks

ClawHub: clean
This skill is a read-only SEO/GEO analysis helper that consistently refuses publishing, credential handling, telemetry, and other write actions.
LLM: benign (high) · VirusTotal: · 21 Aug 2026