SKILLEMALL.ai

BC traffic-standards-kb

Use when writing Chinese smart transportation solutions (智慧路口, 智能停车, V2X, MaaS, ETC, 智慧公交, 智慧高速, 智慧服务区, 智慧交管, 智慧交运, 车路云一体化, 智能网联, 低空经济, 智慧物流, 自动驾驶, 智慧公交) or technical proposals requiring GB/JT/GA industry standards citation. Requires API key from https://solvexpert.net

ClawHub Agent Skills author: solvex-top v1.0.0 MIT-0 4 files body ≈ 1 042 tokens Open the sourceclawhub.ai analyzed 34 h ago

Use when writing Chinese smart transportation solutions (智慧路口, 智能停车, V2X, MaaS, ETC, 智慧公交, 智慧高速, 智慧服务区, 智慧交管, 智慧交运, 车路云一体化, 智能网联, 低空经济, 智慧物流, 自动驾驶, 智慧公交) or…

As a process C 62/100 · Has gaps — weak spots: when it triggers, failures and branches, progress reporting

GeneratorLogistics and warehouseAI and agentsResearchtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
90
Quality 40%
87
Run on models
none yet
Process rating
C
62/100
Has gaps
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

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

    ✓ No critical or high findings

    Medium and low: 10
    • low Secrets in code secret-high-entropy-token api-reference.md:44
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      2. **Request Body Parameter:** `searchAuthToken: "Thn5…Z4U"` **(MANDATORY)**
      quoted
    • low Secrets in code secret-high-entropy-token api-reference.md:56
      High-entropy token-like string (may be an id, hash or a credential)
      | searchAuthToken | string | ✅ | **MANDATORY** SearchBots auth token | Thn5…Z4U |
    • low Secrets in code secret-high-entropy-token api-reference.md:73
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "searchAuthToken": "Thn5…Z4U"
      quoted
    • low Secrets in code secret-high-entropy-token api-reference.md:127
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      - **Fix:** Always include `searchAuthToken: "Thn5…Z4U"` in request body
      quoted
    • low Secrets in code secret-high-entropy-token README.md:112
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      2. **请求体参数:** `searchAuthToken: "Thn5…Z4U"`(必须)
      quoted
    • low Secrets in code secret-high-entropy-token README.md:121
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | `searchAuthToken` | string | 是 | SearchBots 认证令牌 | `Thn5…Z4U` |
      table
    • low Secrets in code secret-high-entropy-token README.md:160
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "searchAuthToken": "Thn5…Z4U"
      quoted
    • low Secrets in code secret-high-entropy-token SKILL.md:77
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "searchAuthToken": "Thn5…Z4U"
      quoted
    • low Secrets in code secret-high-entropy-token SKILL.md:88
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | `searchAuthToken` | string | ✅ | **REQUIRED**: `Thn5…Z4U` |
      table
    • low Secrets in code secret-high-entropy-token SKILL.md:136
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | Missing `searchAuthToken` | ❌ "Authentication error: API key is invalid!" | **ALWAYS include** `searchAuthToken: "Thn5…Z4U"` |
      table

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 62/100

    • 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
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 18 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1042 tokens
    • 100Running it twice. No mutating operations

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 269: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 18 items
    • +3Output format is stated explicitly
    • +4Has examples (5 code blocks)

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

    External checks

    ClawHub: suspicious
    The skill does what it claims, but it embeds a mandatory shared authentication token and encourages broad automatic use of an external API, so users should review it before installing.
    LLM: suspicious (high) · VirusTotal: · 10 Jun 2026