SKILLEMALL.ai
RU Sign in

BD regulatory-change-monitor

Monitors FCA, PRA, APRA, SEC, and EIOPA regulatory pages for changes. Summarises updates, flags what matters for financial services teams.

ClawHub Hermes author: quest-commits v1.0.0 MIT-0 2 files body ≈ 1 385 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process D 49/100 · Unfinished process — weak spots: when it triggers, inputs and preconditions, failures and branches

ProcedureInfrastructureWriting and documentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
D
49/100
Unfinished process
Inputs and preconditions w 11
0
Failures and branches w 10
0
When it triggers w 12
20
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.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 138 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
  • note frontmatter-key unknown frontmatter key "trigger"
  • note frontmatter-key unknown frontmatter key "price"

Process rating: all ten parameters 49/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 40Consistency. Frontmatter name (regulatory-change-monitor) differs from the folder (regchangemtr)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 25 steps
  • 100Execution cost. Instruction body is 1385 tokens
  • 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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 138: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 25 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

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

External checks

ClawHub: clean
This skill monitors public regulator websites and writes a small disclosed local state file to avoid duplicate alerts.
LLM: benign (high) · VirusTotal: · 29 May 2026