SKILLEMALL.ai
GitHub ↗ RU Sign in

BD observability-designer

Observability Designer (POWERFUL)

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 14 files body ≈ 3 271 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Observability Designer (POWERFUL)

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructureData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
99
Quality 40%
56
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
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.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration exfil-webhook-url assets/sample_alerts.json:258
    Webhook / callback URL commonly used for exfiltration (verify the destination) (test fixture / example file; quoted — discussed, not commanded)
    "api_url": "https://hooks.slack.com/services/warnings",
    fixturequoted

Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 48/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 11 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 148 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3271 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)
  • +3Description length 33: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -43 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +4Structure: 52 headings
  • +3Step-by-step instructions: 148 items
  • +3All 3 scripts are documented

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