SKILLEMALL.ai
GitHub ↗ RU Sign in

BB phone-notification-reset-routine

Create a 20-minute phone notification audit card for attention hygiene, without account, credential, surveillance, or monitoring setup.

ClawHub Agent Skills author: haidong v1.0.1 MIT-0 3 files body ≈ 1 513 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 72/100 · Nearly there — weak spots: when it triggers, running it twice

AnalyzerInfrastructureAI and agentstype 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
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
B
72/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
Result and completion w 14
60
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "triggerKeywords"
  • note frontmatter-key unknown frontmatter key "language"
  • note frontmatter-key unknown frontmatter key "hasExecutableCode"
  • note frontmatter-key unknown frontmatter key "promptOnly"
  • note frontmatter-key unknown frontmatter key "execution"

Process rating: all ten parameters 72/100

  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 60Failures and branches. 2 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 69 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1513 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The skill ranks results itself: that belongs to the system behind the tool, not the model

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)
  • +2Single-language instructions
  • +3Description length 135: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 69 items
  • +3Output format is stated explicitly
  • +4Has examples (0 code blocks)
  • +1License stated

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

External checks

ClawHub: clean
This prompt-only skill appears to provide a bounded phone-notification cleanup checklist without code, credentials, network access, or monitoring behavior.
LLM: benign (medium) · VirusTotal: benign · 13 May 2026