SKILLEMALL.ai
GitHub ↗ RU Sign in

BF DOM Observer Pro

Efficient DOM monitoring system for real-time content detection in web browsers. Uses MutationObserver, IntersectionObserver, and intelligent debouncing to detect AI-generated content as it appears...

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 917 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Efficient DOM monitoring system for real-time content detection in web browsers.

As a process F 28/100 · Will not run — References files that are not bundled: examples/dom-observer-pro-examples.js

AnalyzerInfrastructuretype 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
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
F
28/100
Will not run
References files that are not bundled: examples/dom-observer-pro-examples.js
Tools and files w 18
0
Result and completion w 14
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.
  2. 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: examples/dom-observer-pro-examples.js

Process rating: all ten parameters 28/100

Will not run. References files that are not bundled: examples/dom-observer-pro-examples.js
  • 0Tools and files. 1 referenced file(s) missing: examples/dom-observer-pro-examples.js
  • 0Result and completion. Does not say what the result is
  • 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
  • 40Consistency. Frontmatter name (DOM Observer Pro) differs from the folder (dom-observer-pro)
  • 85Steps. 43 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 917 tokens
  • 100Running it twice. No mutating operations
  • low 10 top-level sections: this looks like several domains in one skill

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 200: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 43 items
  • +4Has examples (3 code blocks)

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