SKILLEMALL.ai

DF squad-control

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: Wilson Gan v1.4.0 MIT-0 15 files · 2 scripts body ≈ 5 974 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process F 50/100 · Will not run — References files that are not bundled: scripts/wake-listener.sh

ProcedureGitHubInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
58/100
safety, quality, tests
Safety 60%
68
Quality 40%
43
Run on models
none yet
Process rating
F
50/100
Will not run
References files that are not bundled: scripts/wake-listener.sh
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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 · 8

✓ No critical or high findings

Medium and low: 8
  • medium Exfiltration net-credential-use references/advanced-flows.md:10
    Credential used in a network call (verify the destination is the intended service)
    curl -sL "${SC_API_URL}/api/tasks/list?status=working" -H "x-api-key: ${SC_API_KEY}"
  • medium Exfiltration net-credential-use references/advanced-flows.md:41
    Credential used in a network call (verify the destination is the intended service)
    curl -sL "${SC_API_URL}/api/tasks/list?status=done" -H "x-api-key: ${SC_API_KEY}"
  • medium Exfiltration net-credential-use references/advanced-flows.md:49
    Credential used in a network call (verify the destination is the intended service)
    curl -sL -H "Authorization: token ${GITHUB_TOKEN}" \
  • medium Exfiltration net-credential-use SKILL.md:199
    Credential used in a network call (verify the destination is the intended service)
    curl -sL "${SC_API_URL}/api/tasks/list?status=working" -H "x-api-key: ${SC_API_KEY}"
  • medium Exfiltration net-credential-use SKILL.md:217
    Credential used in a network call (verify the destination is the intended service)
    curl -sL "${SC_API_URL}/api/tasks/list?status=done" -H "x-api-key: ${SC_API_KEY}"
  • medium Exfiltration net-credential-use SKILL.md:224
    Credential used in a network call (verify the destination is the intended service)
    curl -sL -H "Authorization: token ${GITHUB_TOKEN}" \
  • low Exfiltration net-credential-use SKILL.md:96
    Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)
    - Pending: `curl -sL "${SC_API_URL}/api/tasks/pending" -H "x-api-key: ${SC_API_KEY}"`
    quoted
  • low Exfiltration net-credential-use SKILL.md:97
    Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)
    - Review: `curl -sL "${SC_API_URL}/api/tasks/list?status=review" -H "x-api-key: ${SC_API_KEY}"`
    quoted

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 24, column 18: description: Optional default git base branch override (fallback: workspace… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5974 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: scripts/wake-listener.sh
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 50/100

Will not run. References files that are not bundled: scripts/wake-listener.sh
  • 0Tools and files. 1 referenced file(s) missing: scripts/wake-listener.sh
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 70Execution cost. Instruction body is 5974 tokens
  • 100Steps. 57 steps
  • 100Failures and branches. 7 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 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
  • -32 of 4 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 57 items
  • +4Has examples (27 code blocks)
  • +4Reference files are cited in the instructions (5 of 8)

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

External checks

ClawHub: suspicious
This skill is not clearly malicious, but it needs review because it gives agents recurring authority to handle GitHub tokens, spawn workers, update tasks, and merge code.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026