AC it-integration-solution
信息化解决方案 — 用于生成 IT 集成公司面向企业客户的 Word（.docx）格式解决方案文档。当用户要求编写、生成或创建「信息化解决方案」「IT集成解决方案」「IT解决方案」「技术方案」「系统集成方案」「项目实施方桇」「投标技术方案」等面向企业客户的专业文档时使用。覆盖封面、目录、项目概述、需求分析、技术方案设计、系统架构、实施方案、项目管理、培训方案、售后服务、验收方案完整章节。基于国央企Word文档规范，适配企业级方案的专业排版需求。 This skill should be used when the user wants to create IT integration solution proposals for enterprise clients in .docx format.
信息化解决方案 — 用于生成 IT 集成公司面向企业客户的…
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:33High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Sp7+5iiJSbfyYDM+bpZd…hVe/E+F6QC…sWg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:105High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…MR8+oLJn…yG7+A7Gi…X6t/oCki…1dQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:135High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…pjs+EVnW…hE7+ZyY8…tdA==",
detector
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "zh_name" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 57/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
- 30Running it twice. 9 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 56 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1869 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 354: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (3 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.