BD launch-readiness-auditor
Use when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons. Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor. 发布就绪审计/RAMP分阶段评估/发布前放行
runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons.
As a process D 45/100 · Unfinished process — References files that are not bundled: ../../../references/runtime-invocation.md, ../../../references/ramp-benchmark.md, ../../../references/auditor-runbook.md
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 338 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: ../../../references/runtime-invocation.md - warning
missing-refreference to a missing file: ../../../references/ramp-benchmark.md - warning
missing-refreference to a missing file: ../../../references/auditor-runbook.md - warning
missing-refreference to a missing file: ../../../references/scoring-semantics.md - warning
missing-refreference to a missing file: ../../../references/measurement-protocol.md - warning
missing-refreference to a missing file: ../../../protocol/launch-registry/SKILL.md - warning
missing-refreference to a missing file: ../../assemble/launch-asset-packager/SKILL.md - warning
missing-refreference to a missing file: ../launch-day-conductor/SKILL.md - warning
missing-refreference to a missing file: ../../prove/launch-monitor/SKILL.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "class"
Process rating: all ten parameters 45/100
- 0Tools and files. 9 referenced file(s) missing: ../../../references/runtime-invocation.md, ../../../references/ramp-benchmark.md, ../../../references/auditor-runbook.md
- 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
- 30Running it twice. 4 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 33 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1707 tokens
- low 13 top-level sections: this looks like several domains in one skill
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 338: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.