SKILLEMALL.ai

CD skillhub-upload-guide

(no description)

ClawHub Agent Skills author: clawhub-master v1.0.0 MIT-0 3 files body ≈ 1 612 tokens Open the sourceclawhub.ai analyzed 34 h ago

这是最容易踩的坑,必须严格遵守,否则会造成 API Key 泄露。 1.

As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationData and analyticsAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
60/100
safety, quality, tests
Safety 60%
98
Quality 40%
4
Run on models
none yet
Process rating
D
41/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
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 Secrets in code secret-password-literal SKILL.md:239
    Hard-coded password / key literal (may be an example)
    apiKey: '+3mGg…4Bg=='
  • low Secrets in code secret-password-literal SKILL.md:251
    Hard-coded password / key literal (may be an example)
    apiKey: '+3mGg…4Bg=='

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

Against the Agent Skills spec

  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"

Process rating: all ten parameters 41/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 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
  • 30Running it twice. 4 mutating operations with no state check
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 36 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1612 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 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 36 items
  • +4Has examples (11 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
The skill is a publishing guide, but it includes a real-looking IMA ClientID and API key in the published instructions, creating a credential exposure risk.
LLM: suspicious (high) · 27 Jun 2026