SKILLEMALL.ai

BC laomo-github

老默 GitHub 助手 - 多账户管理、PR 一键推送/清理、代码审查、通知推送。v2.0 完整功能。

ClawHub Agent Skills author: mrzhangkris v2.0.0 MIT-0 8 files · 5 scripts body ≈ 1 292 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceGitHubInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
97
Quality 40%
68
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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.
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 · 3

✓ No critical or high findings

Medium and low: 3
  • low Exfiltration exfil-webhook-url github-notify.sh:191
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    "https://api.telegram.org/bot${bot_token}/sendMessage" \
    placeholder
  • low Exfiltration exfil-webhook-url SKILL.md:231
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    export DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."
    placeholder
  • low Exfiltration exfil-webhook-url SKILL.md:241
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    export SLACK_WEBHOOK_URL="https://hooks.slack.com/services/..."
    placeholder

Files scanned: 8. 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")
  • note frontmatter-key unknown frontmatter key "slug"

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 63 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1292 tokens
  • low 10 top-level sections: this looks like several domains in one skill

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 52: 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: 63 items
  • +4Has examples (15 code blocks)

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

External checks

ClawHub: suspicious
The skill is mostly purpose-aligned GitHub automation, but it can make live repository changes, delete remote branches, store account metadata, and send project details to chat services with limited safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026