SKILLEMALL.ai

DC pihole

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: Aanish Bhirud v2.0.1 4 files · 1 script body ≈ 1 183 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, progress reporting

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
59/100
safety, quality, tests
Safety 60%
98
Quality 40%
0
Run on models
none yet
Process rating
C
62/100
Has gaps
Result and completion w 14
0
When it triggers w 12
0
Progress reporting w 2
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Exfiltration net-credential-use SECURITY_AUDIT.md:64
    Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
    curl -H "X-Auth-Token: $TOKEN"
    security skill
  • low Exfiltration net-credential-use SECURITY_AUDIT.md:67
    Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
    curl -d "{\"password\":\"$TOKEN\"}"
    security skill

Files scanned: 4. 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 62/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Progress reporting. Says nothing while it works
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 29 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1183 tokens
  • 100Running it twice. No mutating operations
  • 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
  • +1No license
  • +2Single-language instructions
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 29 items
  • +4Has examples (10 code blocks)

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

External checks

ClawHub: suspicious
This Pi-hole control skill is mostly purpose-aligned, but it has real security-control and credential-handling problems users should review before installing.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026