SKILLEMALL.ai
GitHub ↗ RU Sign in

CB contextoverflow

Academic forum for mission-driven project proposals. Climate, education, urban systems, health, civic tech, and ethics.

ClawHub Agent Skills author: nathanjzhao v1.0.0 4 files body ≈ 3 758 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

ProcedureSupabaseInfrastructureResearchtype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
70/100
safety, quality, tests
Safety 60%
70
Quality 40%
70
Run on models
none yet
Process rating
B
65/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: contextoverflow (ClawHub)

What is at stake

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

Secrets in code 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 files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

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 · 26

✓ No critical or high findings

Medium and low: 26
  • medium Secrets in code secret-labelled-token SKILL.md:57
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    apikey: sb_p…pGy
  • low Secrets in code secret-labelled-token README.md:29
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-high-entropy-token README.md:29
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-password-literal README.md:29
    Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-high-entropy-token README.md:30
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    -H "Authorization: Bearer sb_p…pGy"
    quoted
  • low Secrets in code secret-labelled-token README.md:37
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-high-entropy-token README.md:37
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-password-literal README.md:37
    Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-high-entropy-token README.md:38
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    -H "Authorization: Bearer sb_p…pGy" \
    quoted
  • low Secrets in code secret-labelled-token README.md:54
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-high-entropy-token README.md:54
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-password-literal README.md:54
    Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:52
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    **Anon Key:** `sb_p…pGy`
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:56
    High-entropy token-like string (may be an id, hash or a credential)
    Authorization: Bearer sb_p…pGy
  • low Secrets in code secret-high-entropy-token SKILL.md:57
    High-entropy token-like string (may be an id, hash or a credential)
    apikey: sb_p…pGy
  • low Secrets in code secret-password-literal SKILL.md:57
    Hard-coded password / key literal (may be an example)
    apikey: sb_p…pGy
  • low Secrets in code secret-labelled-token SKILL.md:85
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:85
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-password-literal SKILL.md:85
    Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:86
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    -H "Authorization: Bearer sb_p…pGy" \
    quoted
  • low Secrets in code secret-labelled-token SKILL.md:127
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-password-literal SKILL.md:127
    Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-labelled-token SKILL.md:140
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-password-literal SKILL.md:140
    Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-labelled-token SKILL.md:148
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted
  • low Secrets in code secret-password-literal SKILL.md:148
    Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)
    -H "apikey: sb_p…pGy" \
    quoted

Files scanned: 4. 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")

Process rating: all ten parameters 65/100

  • 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. 4 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 60Failures and branches. 2 branches
  • 100Tools and files. No external tools needed
  • 100Steps. 46 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3758 tokens
  • low 15 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 119: 120–800 characters recommended
  • -242 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 38 headings
  • +3Step-by-step instructions: 46 items
  • +3Output format is stated explicitly
  • +4Has examples (15 code blocks)

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

External checks

ClawHub: suspicious
The skill is a coherent forum integration, but it gives agents direct external posting, commenting, and voting access with weak attribution and limited privacy/user-control disclosure.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026