SKILLEMALL.ai
GitHub ↗ RU Sign in

CC biaoshu-bailian

上传招标/投标文件，AI 一站式完成智能解读（废标红线/评分标准/控标洞察）、成品投标文件(.docx)生成、标书审查（分级风险+雷同检测）和标书查重（2-3份投标文件相似/雷同风险检查）。覆盖投标、招标、标书、投标文件、竞标、围标、控标、废标、评分标准、资格条件、技术标、商务标、暗标、响应文件、应答文件、雷同检测、相似检查、标书查重等场景——当用户提供或提及招标/投标文件、问「这个标能不能投 / 有哪些废标红线 / 帮我写投标书 / 检查标书有没有问题 / 两份投标文件像不像 / 会不会被判雷同」，或想解读招标文件、生成投标文件、做标书审查或查重时使用。需百炼®标书 Api Key（官网注册可领赠送字数）；文件经百炼®标书云端处理，智能解读免费，标书制作/审查/查重按可用字数计费。

ClawHub Agent Skills author: 标书筑造师 v1.0.17 MIT-0 26 files · 17 scripts body ≈ 2 365 tokens Open the sourceclawhub.ai↗ analyzed 7 d ago

上传招标/投标文件，AI…

As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationWordPDFProcurementtype 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
82/100
safety, quality, tests
Safety 60%
95
Quality 40%
62
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: biaoshu-bailian (ClawHub)

What is at stake

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

Broad scope 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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Bash

Files scanned: 26. 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")
  • note frontmatter-key unknown frontmatter key "permissions"

Process rating: all ten parameters 59/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 55Failures and branches. 1 branches
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 67 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2365 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)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • -224 emoji in the instructions: noise for the model
  • -31 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 346: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 67 items
  • +4Reference files are cited in the instructions (2 of 7)

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

External checks

ClawHub: suspicious
The skill largely does what it says, but it needs Review because it handles sensitive bid files and credentials while allowing uncontained file writes, undeclared local metadata persistence, and risky API-key redirect behavior.
LLM: suspicious (high) · 16 Sept 2026