BC proflow
项目全流程标准化交付技能。深度整合 openspec 与 superpowers，覆盖从需求脑暴到规格文档的完整开发周期。核心能力：智能功能规模评估（fix/小功能自动跳过脑暴直达代码）、全局唯一需求ID注入与防重、标准化文档命名与归档、全流程阶段追踪与回退。支持 proflow full/brainstorm/plan/execute/spec/status/reset 命令。触发条件：用户提及 proflow、项目全流程、标准项目流程、一键全自动项目文档、需求脑暴与执行计划等。
As a process C 53/100 · Has gaps — 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.
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: 6. 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")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 51 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 843 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
- +1No license
- +2Single-language instructions
- +3Description length 243: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 51 items
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
This workflow skill is not malicious, but it can create repository files, alter .gitignore, and modify code from broad triggers without a clear approval gate.
LLM: suspicious (high) · VirusTotal: · 29 May 2026