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

84%

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

73%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, highly actionable execution skill: the 8-step workflow is clearly gated with validation checkpoints (manifest-hash binding, verify-current rules, red-line check, receipt-before-status), and the bundle reference is real and well-signaled. The main cost is token efficiency — registry mechanics are stated three times and the channel-matrix's wave/red-line content is restated in the body — and a sample output artifact would make the guidance fully concrete.

Suggestions

State the registry proposal mechanics (authorized `operation: propose` to `registry-events.py`, never write the dossier directly) once — in the Skill Contract's Writes bullet — and have steps 8 and Save Results reference it instead of restating it.

Move the wave-tier timings and the red-line list out of steps 6–7 and into references/channel-matrix.md, keeping only a one-line pointer plus the single most safety-critical red line (no vote solicitation) inline.

Add one worked example of a T-0 submission-status line (the exact ndjson event shape) so the most frequent output is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no padding about concepts Claude already knows, but it repeats itself: the registry-proposal mechanics ('an authorized `operation: propose` request to `registry-events.py`' with 'never write the dossier directly') appear in three places (Skill Contract Writes, step 8, Save Results), the RAMP non-computation rule twice, and steps 6–7 restate the wave tiers and red lines that already live in references/channel-matrix.md. Mostly efficient, but it could be meaningfully tightened by deduplicating.

3 / 5

Actionability

Guidance is concrete and executable throughout — the exact title template 'Show HN: <what it is, stated plainly>', named per-sub table columns (subreddit, self-promotion rule as written, required flair/format, account-history expectations), wave timings, and the exact save path 'memory/launch/community-launch-runner/YYYY-MM-DD-<launch-slug>-submissions.md'. It falls short of fully copy-paste-ready because no worked output example (a sample maker-comment skeleton or a sample T-0 status line) demonstrates the common cases.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints: step 1 hard-gates on the manifest hash and SHIP verdict ('Missing accepted state or a mismatch is Unknown/NEEDS_INPUT; do not submit against it'), step 2 verifies each community's current rules and drops barred channels, step 7 runs the red-line check before execution, and step 8 enforces receipt gating ('Only after receipt evidence exists may the corresponding dated status fact be proposed') with explicit handling of partial/failed/missing receipts — a full feedback loop for a batch-submission workflow.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with a clearly annotated Reference Materials list, and its one bundle reference, references/channel-matrix.md, is real, one level deep, and accurately described. It misses the top anchor because the wave-tier table and red-line list from that reference are duplicated inline in steps 6–7 rather than kept solely in the file.

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.

A strong description: it lists the full inventory of concrete deliverables, opens with explicit natural-language triggers, and closes with four explicit boundary statements that route adjacent intents to sibling skills. The only weakness is that a few natural trigger phrasings (Reddit/subreddit posting, directory submission as a user would phrase it) are implied rather than stated.

DimensionReasoningScore

Specificity

The description enumerates every concrete output — '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' — which is comprehensive coverage of the skill's actions, matching the top anchor rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both questions: a detailed 'what' (all five package types plus the red-line check and T-0 status lines) and an explicit 'Use when the user asks to "launch on Product Hunt / Hacker News"…' clause with concrete trigger phrases, exactly matching the top anchor.

5 / 5

Trigger Term Quality

Triggers like 'launch on Product Hunt / Hacker News', 'prepare community or directory launch submissions', and 'plan the launch submission waves' are phrases a user would naturally say, but a few natural variations (e.g., 'post on Reddit', 'submit to directories' as bare user phrasing) are only implied, so coverage is good rather than exhaustive.

4 / 5

Distinctiveness Conflict Risk

It claims a clear niche (community/directory submission execution) and explicitly disambiguates four sibling 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' — giving minimal conflict risk.

5 / 5

Total

19

/

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.