BD tech-bid-writer
投标人侧「技术标写作专家」——根据招标文件一键产出技术部分可用投标包（技术标正文 Word + 技术偏离表 + 技术合规预检报告 + 评分点覆盖核对表），完全不涉及商务报价与资格审查。采用「评分项↔标题逐项映射防漏分 + 输出纯净（像人写）+ 技术合规零容忍 + 可选知识库溯源 + 内置 Word 直出」流水线。当用户需要写技术标、技术方案、施工组织设计、技术投标文档，或要求按评分表生成技术标大纲/标题体系、生成技术偏离表、检查技术标评分点是否全覆盖时使用。触发词：技术标、技术方案、技术投标、施工组织设计、评分表生成技术标大纲、技术偏离表、技术标评分点覆盖、技术标大纲。
投标人侧「技术标写作专家」——根据招标文件一键产出技术部分可用投标包（技术标正文 Word + 技术偏离表 + 技术合规预检报告 + 评分点覆盖核对表），完全不涉及商务报价与资格审查。采用「评分项↔标题逐项映射防漏分 + 输出纯净（像人写）+ 技术合规零容忍 + 可选知识库溯源 + 内置 Word…
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 41/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
- 40Consistency. Frontmatter name (tech-bid-writer) differs from the folder (tech-bid-writer-1-0-0)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 66 steps
- 100Execution cost. Instruction body is 1833 tokens
- 100Running it twice. No mutating operations
- low 12 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
- +4No input/output examples
- -224 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 288: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 66 items
- +4Reference files are cited in the instructions (5 of 5)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.