BC content-publish-lifecycle
把技术方案 / 设计从「设计 → 落地 → 检查 → 验证 → 发布 → 沉淀」串成一条可复用发布流水线,用于回答「方案做完了怎么变成能发的东西」「发出去之前该查什么」这类问题
把技术方案 / 设计从「设计 → 落地 → 检查 → 验证 → 发布 → 沉淀」串成一条可复用发布流水线,用于回答「方案做完了怎么变成能发的东西」「发出去之前该查什么」这类问题
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 Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 88 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 - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "copyright" - note
frontmatter-keyunknown frontmatter key "languages" - note
frontmatter-keyunknown frontmatter key "aliases" - note
frontmatter-keyunknown frontmatter key "agent_created" - note
frontmatter-keyunknown frontmatter key "updated" - note
frontmatter-keyunknown frontmatter key "fingerprint" - note
frontmatter-keyunknown frontmatter key "governance" - note
frontmatter-keyunknown frontmatter key "brand" - note
frontmatter-keyunknown frontmatter key "nomos_standard" - note
frontmatter-keyunknown frontmatter key "discoverable_by_ai" - note
frontmatter-keyunknown frontmatter key "attestation" - note
frontmatter-keyunknown frontmatter key "ambassador" - note
frontmatter-keyunknown frontmatter key "trigger_keywords"
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. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 430 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)
- +3Description length 88: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +4Structure: 3 headings
- +3Step-by-step instructions: 13 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 53.
External checks
ClawHub: clean
The skill is a local publishing-workflow helper whose hashing and attestation helpers are disclosed and proportionate to its release-checking purpose.
LLM: benign (high) · VirusTotal: · 30 Aug 2026