SKILLEMALL.ai
GitHub ↗ RU Sign in

AC whatpulse

Query WhatPulse computer usage statistics using natural language. Keystrokes, mouse activity, application screen time, network bandwidth, website tracking, uptime, and profiles. Reads the local WhatPulse SQLite database in strict read-only mode. Triggers: "whatpulse", "keystrokes", "mouse distance", "app usage", "screen time", "bandwidth", "computer stats", "typing stats"

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

Query WhatPulse computer usage statistics using natural language.

As a process C 53/100 · Has gaps — weak spots: result and completion, consistency, running it twice

AnalyzerData and analyticsSoftware developmenttype 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
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
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 description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 7 mutating operations with no state check
  • 40Consistency. Frontmatter name (whatpulse) differs from the folder (whatpulse-ai-agent-skill)
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 41 steps, 2 vague phrases
  • 100Execution cost. Instruction body is 2535 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 8 example trigger phrases
  • +3Description length 374: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 41 items
  • +4Has examples (5 code blocks)
  • +1License stated

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