CD oss-scaffold
从 0 搭建 GitHub 仓库全部组件的脚手架(腾讯三标杆仓规格)。输入项目名 + 一句话定位,一次性生成 README(三档形态)+ CHANGELOG + CONTRIBUTING + LICENSE + .github 模板 + CI 骨架 + docs 骨架 + .gitignore,并完成本地 git init/commit;推送 GitHub 前强制 R14 放行。文档风格引用 oss-voice,维护者语气引用 oss-persona,文档站调用 vitepress skill。触发词(能力词,场景词「建仓」让渡给 oss-workflow):脚手架生成、从 0 生成组件、初始化组件、scaffold。
从 0 搭建 GitHub 仓库全部组件的脚手架(腾讯三标杆仓规格)。输入项目名 + 一句话定位,一次性生成 README(三档形态)+ CHANGELOG + CONTRIBUTING + LICENSE + .github 模板 + CI 骨架 + docs 骨架 + .gitignore,并完成本地 git…
As a process D 35/100 · Unfinished process — References files that are not bundled: references/settings-profiles/ci/ci-<lang>.yml
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 24. 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") - warning
missing-refreference to a missing file: references/settings-profiles/ci/ci-<lang>.yml
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: references/settings-profiles/ci/ci-<lang>.yml
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1088 tokens
- 100Progress reporting. Reports progress
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 313: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.