CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

community-launch-runner

Use when the user asks to "launch on Product Hunt / Hacker News", "prepare community or directory launch submissions", or "plan the launch submission waves"; produces per-platform submission packages — a Product Hunt tagline / gallery / first-comment skeleton, a factual Show HN title and text, per-subreddit posts with a self-promotion rules table, tiered directory waves, and a regional channel matrix including Chinese communities — plus a platform red-line check (never solicit votes or organize voting rings) and T-0 submission-status lines for the launch registry. Not for paid amplification — use content-amplifier; not for creator channels — use campaign-planner; not for launch telemetry readouts — use launch-monitor; not for ongoing community presence or pre-launch karma-building outside the launch window — use participation-warmup-planner. 社区发布/PH提交包/Show HN/目录波次/平台红线/中文渠道

Quality

89%

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

81%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 execution skill: a clear 8-step sequence with genuine validation gates (manifest binding, rules verification, receipt evidence), concrete output specs, and proper delegation of the channel matrix to a real reference file. The main deductions are repeated registry-protocol and red-line text within the body, no worked example of a submission package or registry propose call, and cross-skill links that do not resolve inside this bundle.

Suggestions

State the registry propose protocol once (e.g., in step 8 or the Skill Contract) and reference it from the other sections instead of restating it four times; the same applies to the red lines, which are duplicated verbatim from channel-matrix.md.

Add one compact worked example — a filled-in mini submission package (PH tagline + first-comment skeleton) or a sample `registry-events.py` `operation: propose` request — so the output shape is copy-paste derivable rather than assembled from prose.

Fix or qualify the cross-bundle links (skill-contract.md, CONNECTORS.md, SECURITY.md, ramp-benchmark.md, action-control.md, sibling skill SKILL.md paths) since none of them resolve from this skill's directory, or move the essential content into references/.

DimensionReasoningScore

Conciseness

The body is dense and substantive — it never explains concepts Claude already knows and each step carries real instruction — but it repeats the registry-proposal protocol four times (Scope guard, Writes, step 8, Save Results) and restates the red lines that also live in channel-matrix.md. This is 'efficient with minor instances that could be trimmed' (4), not the every-token-earns-its-place leanness of the 5 anchor; it is clearly above 3 since there is no padded or unnecessary explanation.

4 / 5

Actionability

Guidance is concrete for an instruction-only skill: exact artifacts per platform, exact file paths (memory/launch/community-launch-runner/..., memory/events/launches.ndjson), an exact title format ("Show HN: <what it is, stated plainly>"), and a specified per-sub table schema. It falls short of fully copy-paste-ready (5) because there is no worked example of a submission package or a sample registry-events.py propose invocation — the reader must assemble the shape from prose. It is well above the 3 anchor's pseudocode-level incompleteness.

4 / 5

Workflow Clarity

Eight explicitly sequenced steps with validation checkpoints and error feedback loops: step 1 gates on a manifest-matching SHIP verdict ("Missing accepted state or a mismatch is Unknown/NEED_INPUT; do not submit against it"), step 2 drops channels whose rules bar self-promotion and says to ask moderators when ambiguous, and step 8 enforces receipt evidence before any status fact is proposed ("partial, failed, missing, or unknown receipts remain open"). This matches the 5 anchor — explicit validation, error-recovery behavior, and a 'Done when' checklist; the destructive/batch cap does not apply because validation is present.

5 / 5

Progressive Disclosure

The body is a well-signaled overview that delegates the channel detail to a real one-level-deep file ([channel-matrix.md](references/channel-matrix.md), verified present in the bundle) listed in a Reference Materials section. It misses 5 because many cross-links (skill-contract.md, CONNECTORS.md, SECURITY.md, ramp-benchmark.md, launch-registry, action-control.md) point outside this bundle and do not resolve from it, leaving navigation partly dangling; structure is still clearly better than the 3 anchor's buried or inline-heavy organization.

4 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: concrete output inventory, quoted natural trigger phrases in both English and Chinese, explicit use-when boundaries, and explicit disambiguation against four neighboring skills. It is long, but the length is dense specification rather than fluff, so no verbosity penalty applies.

DimensionReasoningScore

Specificity

The description enumerates comprehensive concrete outputs: "a Product Hunt tagline / gallery / first-comment skeleton, a factual Show HN title and text, per-subreddit posts with a self-promotion rules table, tiered directory waves, and a regional channel matrix including Chinese communities — plus a platform red-line check... and T-0 submission-status lines". This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); it is well above the 4 anchor because there are no meaningful coverage gaps in the skill's output surface.

5 / 5

Completeness

It explicitly answers both questions: what ("produces per-platform submission packages... a platform red-line check... T-0 submission-status lines") and when ("Use when the user asks to..." with three concrete quoted trigger phrases), plus explicit non-goals. This matches the 5 anchor exactly; the 4 anchor ('when could be more explicit') clearly undersells the quoted trigger phrasing present.

5 / 5

Trigger Term Quality

It quotes natural user phrasings directly ("launch on Product Hunt / Hacker News", "prepare community or directory launch submissions", "plan the launch submission waves") and covers synonyms including Show HN, subreddits, directories, and Chinese keywords (社区发布/PH提交包/Show HN/目录波次/平台红线/中文渠道). This is comprehensive natural-term coverage per the 5 anchor, not merely 'good coverage with a few missing' (4).

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (community/directory submission execution) and actively disambiguates four adjacent skills ("Not for paid amplification — use content-amplifier; not for creator channels — use campaign-planner; not for launch telemetry readouts — use launch-monitor; not for ongoing community presence... use participation-warmup-planner"). Minimal conflict risk, matching the 5 anchor.

5 / 5

Total

20

/

20

Passed

Validation

75%

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

Validation — 12 / 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: 20 suspicious

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 3 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/mobilize/community-launch-runner/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.