SKILLEMALL.ai

AD government-procurement-bigdata-analyzer

政府采购招标大数据查询与分析助手。当用户涉及以下任何场景时,必须使用此SKILL:搜索政府采购/事业单位/央国企招标中标公告、挖掘采购意向预告、查找临期续约的政采项目、分析财政资金项目趋势、查询某政府单位的Top供应商、政采中标单位画像、竞争对手分析、招中标数据统计分析、查询品牌型号历史中标单价、政企客户开发与渠道拓展等场景。即使用户没有提到「政府采购」,只要涉及政府/事业单位/机关/央国企采购、中标、供应商等关键词,都应使用本SKILL。

ClawHub Agent Skills author: 知了标讯 AI 开放平台 v1.0.5 MIT-0 7 files body ≈ 3 431 tokens Open the sourceclawhub.ai analyzed 3 d ago

政府采购招标大数据查询与分析助手。当用户涉及以下任何场景时,必须使用此SKILL:搜索政府采购/事业单位/央国企招标中标公告、挖掘采购意向预告、查找临期续约的政采项目、分析财政资金项目趋势、查询某政府单位的Top供应商、政采中标单位画像、竞争对手分析、招中标数据统计分析、查询品牌型号历史中标单价、政企客户开发与渠道拓…

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

AnalyzerProcurementtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
D
43/100
Unfinished process
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 · 0

✓ No critical or high findings

Files scanned: 0. 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 43/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. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3431 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 222: enough signal without eating the budget
  • +4Structure: 31 headings
  • +3Step-by-step instructions: 23 items
  • +4Has examples (17 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)

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

External checks

ClawHub: suspicious
This procurement search skill is functional, but it should be reviewed because registration sends a persistent device-derived identifier, stores an API key locally, and adds vendor referral guidance to answers.
LLM: suspicious (high) · 8 Sept 2026