SKILLEMALL.ai

DF curiosity

(no description)

The skillemall take

The skill promises nothing. Description is empty, two files, one script. Quality score dropped to 23, process score to 33. No critical findings, but the linter complains about missing description. Models weren't run, sandbox untouched.

Supports many platforms, including Claude and Cursor. But without a description, it's unclear what this skill does or why you'd install it. Don't install it—first figure out what's actually here.

perminder-klair/subwave Agent Skills author: perminder-klair 2 files · 1 script body ≈ 92 tokens Open the sourcegithub.com↗ analyzed 5 d ago

One oddly-specific moment of interest — ideally a real "on this day" beat from the tool (any year), dropped in like you just remembered it.

As a process F 33/100 · No process to follow — weak spots: steps, result and completion, when it triggers

Referencetype and topics are labelled automatically from the skill text
JSON
Technical rating
D
69/100
safety, quality, tests
Safety 60%
100
Quality 40%
23
Run on models
none yet
Process rating
F
33/100
No process to follow
Steps w 15
0
Result and completion w 14
0
When it triggers w 12
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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

  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • note frontmatter-key unknown frontmatter key "label"
  • note frontmatter-key unknown frontmatter key "cooldown"

Process rating: all ten parameters 33/100

  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 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
  • 30Running it twice. 1 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 92 tokens

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 0: 120–800 characters recommended
  • +4Structure: 0 headings, hard to scan
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions

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