SKILLEMALL.ai
GitHub ↗ RU Sign in

BF Notifications Engine

Multi-channel notification delivery with customizable templates, email and SMS sending, and full delivery logging — built for AI agents.

ClawHub Agent Skills author: Cameron48 v1.0.0 MIT-0 2 files body ≈ 258 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 26/100 · Will not run — weak spots: steps, result and completion, when it triggers

TemplateAI and agentsInfrastructuretype 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
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
58
Run on models
none yet
Process rating
F
26/100
Will not run
Steps w 15
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.
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 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")
  • note frontmatter-key unknown frontmatter key "pricing"
  • note frontmatter-key unknown frontmatter key "gateway"

Process rating: all ten parameters 26/100

  • 0Steps. Prose only: no discrete steps
  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (Notifications Engine) differs from the folder (mcf-notifications-engine)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Execution cost. Instruction body is 258 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)
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 136: enough signal without eating the budget
  • +4Structure: 3 headings

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

External checks

ClawHub: clean
This is a straightforward paid notification API skill, but users should be careful because email/SMS content and delivery logs go to an external service.
LLM: benign (medium) · VirusTotal: · 29 May 2026