SKILLEMALL.ai

DD sql-dreamer

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: Oblio v0.1.0 MIT-0 22 files body ≈ 819 tokens Open the sourceclawhub.ai analyzed 2 d ago

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

ProcedureConfluenceInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
58/100
safety, quality, tests
Safety 60%
96
Quality 40%
0
Run on models
none yet
Process rating
D
41/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
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 · 4

✓ No critical or high findings

Medium and low: 4
  • low Exfiltration read-dotenv GETTING_STARTED.md:64
    Reads a .env file
    cp .env.example .env
  • low Dangerous commands cmd-cron-mention GETTING_STARTED.md:291
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention README.md:166
    Mentions editing / listing crontab (quoted — discussed, not commanded)
    Add these entries to your crontab (`crontab -e`). Adjust timezone as needed (shown in EDT = UTC-4):
    quoted
  • low Dangerous commands cmd-cron-mention SKILL_REFERENCE.md:449
    Mentions editing / listing crontab (quoted — discussed, not commanded)
    - Check crontab: `crontab -l`
    quoted

Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger

Process rating: all ten parameters 41/100

  • 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. 6 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 100Steps. 10 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 819 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

  • +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
  • +3Output format is not stated: the model decides each time
  • -31 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 10 items
  • +4Has examples (4 code blocks)

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

External checks

ClawHub: clean
The skill’s behavior matches its stated purpose, but it handles durable memory data, scheduled cleanup, SQL credentials, and optional Confluence publishing that users should configure carefully.
LLM: benign (high) · VirusTotal: · 29 May 2026