CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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分阶段评估/发布前放行

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a disciplined, terse procedural contract with concrete commands, explicit item/veto IDs, worked examples, and a validation checklist — genuinely actionable for an instruction-only skill. Its main weakness is the reference layer: most cited files are not shipped in this bundle, paths mix two different roots, and several references are duplicated, leaving standalone navigation confused despite the well-designed fail-closed fallback file.

Suggestions

Ship or inline the minimum content of the missing runtime references (especially runtime-invocation.md and the typed conversation header from auditor-runbook.md) so the scoring path is executable in a standalone install, or state plainly in each section which content is repo-install-only.

Consolidate the duplicated reference listings (auditor-runbook.md, scoring-semantics.md, ramp-benchmark.md appear in both Runtime Reads and Reference Materials) into a single clearly-signaled reference section, and clarify the two path bases (`../../../references/` vs `references/`).

Add a compact example of the `<run.json>` structure the scorer command expects (or point to the exact section of auditor-runtime.md that defines it), since that is the one concrete input format the body never shows.

DimensionReasoningScore

Conciseness

The body is dense and policy-specific with no explanation of concepts Claude already knows, but run-on generated blocks ("Require the scorer, validator and typed catalogs. If unavailable, collect the selected profile's typed observations and Unknowns...") and mild redundancy across Skill Contract, Instructions, and Validation Checkpoints could be tightened.

4 / 5

Actionability

Concrete, executable elements are present — `python3 "$AARON_SKILLS_ROOT/scripts/rubric-score.py" score <run.json>`, `validate-audit-artifact.py`, explicit item ranges (R1–R10, A1–A10, M1–M10, P1–P10), veto IDs (RAMP-R1/A1/M1/P1), a worked example with raw scores ("raw 76, one verified A1 failure ... final 59"), and an exact persistence path pattern. The gap is that the `<run.json>` input format and the "exact typed conversation header" are only defined in non-bundled references, so a standalone reader cannot fully execute the scoring path.

4 / 5

Workflow Clarity

The lifecycle sequence is clear — declare profile and evidence window, read runtime sources, collect observations with source/date/type/confidence, run the scorer, verify vetoes, report with typed header — and there is an explicit Validation Checkpoints checklist plus a NOT_SCORED fallback. However, the end-to-end order must be assembled from separate sections rather than one explicit procedure, and error-recovery loops (beyond the scorer-unavailable fallback) are thin, keeping it below the top anchor.

4 / 5

Progressive Disclosure

The body is a genuine overview that delegates detail to reference files, but of the eight referenced paths only `references/auditor-runtime.md` exists in the bundle; the five `../../../references/*.md` files and three cross-skill links are absent here, and three of them (auditor-runbook, scoring-semantics, ramp-benchmark) are listed twice (Runtime Reads and Reference Materials). Mixed path bases and duplicate listings make navigation in this bundle ambiguous rather than clearly signaled.

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong example: explicit use-when triggers with quoted natural phrases, a clear one-profile-per-run capability statement, and explicit boundary disambiguation against sibling skills. Its only weaknesses are slightly jargon-lean capability wording ("typed RAMP profile") and a few missing English trigger synonyms.

DimensionReasoningScore

Specificity

Concrete actions are named — "runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons" — plus explicit negative actions ("not for recording launch state", "not for running launch day"), but the deliverable of the audit (verdict/score/gate) is not stated, leaving minor gaps versus comprehensive coverage.

4 / 5

Completeness

Both what ("runs one typed RAMP preflight, execution, or outcome profile") and when ("Use when the user asks to 'audit our launch plan', 'are we ready to launch', or evaluate launch execution/outcomes") are explicitly answered with concrete trigger phrases, matching the top anchor's structure.

5 / 5

Trigger Term Quality

Quoted natural phrases like "audit our launch plan" and "are we ready to launch" are exactly what a user would say, mirrored in Chinese, but common synonyms such as "go/no-go", "pre-launch check", or "launch readiness" (in English) are missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche and actively disambiguates adjacent skills: "Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor", minimizing wrong-skill triggering.

5 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 8 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/mobilize/launch-readiness-auditor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.