SKILLEMALL.ai

BD Remindy - Smart Reminder Service

Email and browser push notification reminders delivered 15 minutes before scheduled events.

ClawHub Agent Skills author: ToolWeb v1.0.0 MIT-0 3 files body ≈ 1 588 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
99
Quality 40%
64
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
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.
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 Secrets in code secret-high-entropy-token SKILL.md:128
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "publicKey": "BEX_…ing"
    quoted

Files scanned: 3. 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")

Process rating: all ten parameters 49/100

  • 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 (Remindy - Smart Reminder Service) differs from the folder (toolweb-remindy)
  • 100Tools and files. No external tools needed
  • 100Steps. 24 steps
  • 100Execution cost. Instruction body is 1588 tokens
  • 100Running it twice. Mutating operations check current state

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 91: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 24 items
  • +4Has examples (13 code blocks)

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

External checks

ClawHub: suspicious
Remindy is a coherent reminder API, but it stores and changes personal reminder and push-notification data without documenting authentication, ownership checks, privacy handling, or deletion safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026