BD capability-pipeline-os
通用能力管线操作系统。基于"万物皆可单元化"思想，将任意领域的任意任务分解为可执行、可组合的能力单元，通过管线编排完成。6大元操作集群（感知/认知/行动/组织/交互/守护）覆盖一切任务类型的原子操作，领域差异通过推导规则注入。触发词：能力单元、管线、Pipeline、任务分解、工作流、原子任务、单元化、编排、执行框架、能力管线、任务编排、流水线、自动编排、分解执行、元操作。
As a process D 38/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
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: 3. 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 38/100
- 0Steps. Prose only: no discrete steps
- 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
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 183 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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 188: enough signal without eating the budget
- +4Structure: 3 headings
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: clean
This is an instruction-only planning framework, with broad activation language and tool-use examples that users should supervise for important actions.
LLM: benign (high) · VirusTotal: · 29 May 2026