BC baijimu-bundle-development
使用 `baijimu` CLI 开发、冻结、审核、发布、安装、升级或卸载 Bundle，以及在 Bundle 内开发 Module、Skill、Agent 和平台应用资源。用于 Bundle-first 公开产品生命周期；不用于 Hosted Service 后端构建、数据库迁移或平台内部发布。
使用 baijimu CLI 开发、冻结、审核、发布、安装、升级或卸载 Bundle，以及在 Bundle 内开发 Module、Skill、Agent 和平台应用资源。用于 Bundle-first 公开产品生命周期；不用于 Hosted Service 后端构建、数据库迁移或平台内部发布。
As a process C 50/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 Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 149 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill
Process rating: all ten parameters 50/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
- 60Consistency. The Hermes dialect needs category and tags
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 372 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
- +2Single-language instructions
- +3Description length 149: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 16 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.