SKILLEMALL.ai

BF ai-code-review

Automated code review with LLM analysis, voice transcription, and Discord notifications

ClawHub Agent Skills author: terrycarter1985 v1.1.1 MIT-0 3 files body ≈ 873 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 33/100 · Will not run — References files that are not bundled: scripts/healthcheck.sh

AnalyzerDiscordSoftware developmentInfrastructureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
99
Quality 40%
63
Run on models
none yet
Process rating
F
33/100
Will not run
References files that are not bundled: scripts/healthcheck.sh
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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.
  2. The text references files that are not there: add them or drop the references.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration exfil-webhook-url SKILL.md:28
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    export DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."  # optional
    placeholder

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")
  • warning missing-ref reference to a missing file: scripts/healthcheck.sh

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: scripts/healthcheck.sh
  • 0Tools and files. 1 referenced file(s) missing: scripts/healthcheck.sh
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 10 mutating operations with no state check
  • 40Consistency. Frontmatter name (ai-code-review) differs from the folder (ai-code-review-svc)
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 16 steps
  • 100Execution cost. Instruction body is 873 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 87: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 16 items
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: suspicious
This skill mostly describes an AI code-review workflow, but it also claims system health checks can auto-restart services such as nginx and Docker without clear scoping or included implementation to review.
LLM: suspicious (high) · VirusTotal: · 29 May 2026