CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch-registry

Use when the user asks to "log this launch", query a launch date/embargo, record a stage transition, or update submissions/outcomes; curates launch facts through the append-only launches event stream with optimistic revisions and derived dossier/calendar views. Not for RAMP scoring — use launch-readiness-auditor; not for planning tier/window — use launch-tier-planner. 发布台账/发布日历/阶段与禁运期记录

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A tight, jargon-dense protocol skill with a clear contract, well-sequenced procedure, and explicit validation checkpoints around an append-only event stream. Its main weaknesses are the triple-listed runtime references, the unshown script invocation, and reference paths that do not resolve within the provided bundle.

Suggestions

Consolidate the three duplicate listings of registry-event-protocol.md and runtime-invocation.md (Runtime Reads, Procedure step 1, and Reference Materials) into a single clearly-signaled references section.

Ship the referenced files with the skill bundle or fix the paths — ../../references/registry-event-protocol.md, runtime-invocation.md, ramp-benchmark.md, state-model.md, and ../../SECURITY.md do not exist in the bundle, yet Procedure step 1 mandates reading two of them before any action.

Add an explicit verification-failure loop, e.g. "if `verify launches` reports an offset/revision mismatch, re-query the projection, re-check expected_revision, and only then consider further appends."

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows, but "registry-event-protocol.md" and "runtime-invocation.md" are each listed three times (Runtime Reads, Procedure step 1, Reference Materials), a small redundancy that could be trimmed.

4 / 5

Actionability

Concrete details abound — the AARON_SKILLS_ROOT shell snippet, `memory/events/launches.ndjson`, the `draft → concept → alpha → beta → general-availability → archived` state path, and `verify launches` — but the actual `registry-events.py` invocation is never shown in the body, deferring execution to an external reference file.

4 / 5

Workflow Clarity

The 8-step procedure is clearly sequenced with upfront validation ("verify the registry script, event schema, and system catalog before invoking it"), a pre-write revision check, and a closing `verify launches` step, but there is no explicit fix-and-retry loop when verification fails (e.g., offset/revision mismatch handling), leaving a minor checkpoint gap rather than the full feedback-loop anchor.

4 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep links under Reference Materials and a Next Best Skill routing table, but the referenced targets (`../../references/registry-event-protocol.md`, `runtime-invocation.md`, `ramp-benchmark.md`, `state-model.md`, `../../SECURITY.md`) are absent from the provided bundle (no references/, scripts/, or assets/ directories exist), so the mandated step-1 reads cannot be resolved from the skill itself; the duplicate reference listings are a further minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

92%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 strong: concrete third-person actions, an explicit 'Use when' clause with quoted trigger phrases, and explicit negative boundaries that disambiguate it from sibling skills. The only minor gap is synonym coverage of natural trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "log this launch", "query a launch date/embargo", "record a stage transition", "update submissions/outcomes", and "curates launch facts through the append-only launches event stream" — covering the skill's full read/write/review surface, matching the comprehensive anchor. Score 4 would imply minor coverage gaps, but the main operations are all explicitly named.

5 / 5

Completeness

It explicitly answers both questions: what the skill does ("curates launch facts through the append-only launches event stream with optimistic revisions and derived dossier/calendar views", third person) and when to use it ("Use when the user asks to 'log this launch', query a launch date/embargo, record a stage transition, or update submissions/outcomes") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrases are quoted directly ("log this launch", "query a launch date/embargo", "record a stage transition") plus the Chinese terms 发布台账/发布日历, giving good coverage; a few natural variants like "release calendar", "GA date", or "embargo lift" are only partially covered, so it falls just short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

Explicit negative boundaries — "Not for RAMP scoring — use launch-readiness-auditor; not for planning tier/window — use launch-tier-planner" — plus a clearly scoped niche (launch record authority) give minimal conflict risk with sibling skills.

5 / 5

Total

19

/

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: 10 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

protocol/launch-registry/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.