CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

early-access-designer

Use when the user asks to "design an early access program", "set up a waitlist and beta stages", or "define beta graduation criteria"; produces a waitlist→concept→alpha→beta→GA stage ladder with per-stage purpose and opt-in semantics, quantified graduation criteria per stage (labeled Estimated), a cohort-gating and invite-throttling plan, tester recruitment with launch-day social-proof prep, a feedback-loop spec where every status change notifies its subscribers, and a referral-loop mechanism spec (invite codes, anti-abuse). Not for waitlist acquisition strategy or the capture-flow spec — use list-growth-designer; not for the canonical stage record — use launch-registry. waitlist/内测阶梯/抢先体验/毕业标准/反馈闭环

Quality

82%

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

67%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 well-structured, genuinely actionable design workflow with clear sequencing, data-provenance labeling, and write guardrails. Its main weaknesses are token-efficiency — the same delegation and registry-proposal boilerplate is repeated across many sections — and minor validation/organization gaps (no post-proposal checkpoint, protocol details inlined rather than referenced out).

Suggestions

State the registry proposal protocol ("authorized `operation: propose` request to `registry-events.py` → `memory/events/launches.ndjson`") once in a single section and reference it elsewhere; it is currently spelled out in four separate places (Skill Contract, Instructions 7 and 8, Save Results).

Consolidate the sibling-skill delegations: the intro Scope guard paragraph, the Reference Materials list, and Next Best Skill largely repeat the same handoff targets (list-growth-designer, launch-registry, launch-feedback-synthesizer) with the same rationale.

Trim the repetitions of the GA opt-out-inclusion decision — it is restated in the intro, Skill Contract, Done-when, Instructions 2 and 8, Save Results, and Next Best Skill; stating it once as a required ladder field would suffice.

DimensionReasoningScore

Conciseness

The body mostly earns its tokens (no explanations of concepts Claude already knows), but delegation boilerplate repeats far beyond 'minor instances that could be trimmed': "via an authorized `operation: propose` request to `registry-events.py`" appears in four places, the GA opt-out-inclusion decision is restated roughly five times, and the intro scope-guard paragraph, Reference Materials, and Next Best Skill sections re-list the same sibling-skill handoffs. This matches the level-3 anchor ('could be tightened') better than level 4, and is well above level 2 since there is no padding or basic-concept exposition.

3 / 5

Actionability

Concrete, executable guidance throughout for an instruction-only skill: named criteria types ("core-flow completion rate, count of structured feedback items reviewed, and error tolerance versus the product's own trailing rate"), two fully specified cohort patterns ("staged invite batches of roughly 5-10% of the waitlist per wave with an observation window"), a status taxonomy example ("open → planned → shipped / declined"), enumerated anti-abuse guards, and exact memory paths and registry commands. It stops short of level 5 only because no example output artifact or criteria template is provided to cover the common case.

4 / 5

Workflow Clarity

Eight numbered steps in a coherent sequence with an explicit 'Done when' checklist, input validation up front ("pull the existing stage record ... the program design must extend it, not contradict it"; "do not invent a baseline"), and guardrails on every write ("ask before writing", "this skill never writes the canonical record"). Not level 5: there is no checkpoint for what happens after the registry proposal (e.g., handling a rejected or conflicting proposal), so one validation gap remains.

4 / 5

Progressive Disclosure

Scored against the actual bundle: no references/, scripts/, or assets/ exist, so the SKILL.md is self-contained at ~76 lines with clean sections (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) and a clearly annotated, one-level-deep reference list. It falls short of level 5 because shared protocol content (the registry proposal procedure, repeated inline) belongs in a referenced file, and the references point to ../../../ paths outside the skill directory that cannot be verified as real files.

4 / 5

Total

15

/

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.

A strong description: explicit 'Use when' triggers with quoted natural phrases, a comprehensive and concrete enumeration of what the skill produces, and explicit disambiguating boundaries against sibling skills. The only weakness is a handful of missing natural English trigger variations, partially compensated by appended bilingual keywords.

DimensionReasoningScore

Specificity

The description enumerates the full concrete output surface: "produces a waitlist→concept→alpha→beta→GA stage ladder with per-stage purpose and opt-in semantics, quantified graduation criteria per stage (labeled Estimated), a cohort-gating and invite-throttling plan, tester recruitment with launch-day social-proof prep, a feedback-loop spec where every status change notifies its subscribers, and a referral-loop mechanism spec (invite codes, anti-abuse)" — multiple specific actions with comprehensive coverage, matching the level-5 anchor rather than the level-4 anchor (which allows minor coverage gaps).

5 / 5

Completeness

Both halves are explicit: "Use when the user asks to 'design an early access program', ..." answers when with concrete trigger phrases, and "produces a waitlist→concept→alpha→beta→GA stage ladder ... referral-loop mechanism spec" answers what, exactly matching the level-5 anchor.

5 / 5

Trigger Term Quality

It quotes natural user phrasings ("design an early access program", "set up a waitlist and beta stages", "define beta graduation criteria") and appends bilingual keywords ("waitlist/内测阶梯/抢先体验/毕业标准/反馈闭环"), giving good synonym coverage. It falls short of the level-5 'comprehensive' anchor because common English variations a user would naturally say — "private beta", "beta testers", "invite-only launch" — are absent, and the trailing keyword tail reads as stuffing rather than natural triggers.

4 / 5

Distinctiveness Conflict Risk

Beyond a clear niche (early-access stage-ladder design), it carries explicit negative boundaries — "Not for waitlist acquisition strategy or the capture-flow spec — use list-growth-designer; not for the canonical stage record — use launch-registry" — which is stronger than the level-4 anchor's 'minor overlap risk with closely related skills'; conflict risk is minimal.

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

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/research/early-access-designer/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.