CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

participation-warmup-planner

Use when the user asks to "plan the participation ramp before we promote", "how much account history or karma do we need in this community", or "design entry incentives and member lifecycle for our own Discord"; produces the per-community pre-promotion warming plan — account-history/tenure expectations (Estimated, named sources), a give-before-ask ledger spec, a per-community etiquette + rule digest with last-verified dates, and the warming → active graduation criteria that channel-registry requires as state-transition evidence — plus the owned-community variant (entry paths + member lifecycle for your own Discord/Slack/forum/企业微信私域). Not for launch-day submissions or T-0 threads — use community-launch-runner. 社区预热/先给后取/账号养成/毕业标准

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

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 disciplined, information-dense planning skill: the 8-step workflow, labeling system (Measured/User-provided/Estimated), and explicit read/write/promote boundaries leave little ambiguity about what to do. The main costs are heavy repetition of the registry-writer guardrail across five sections and an unbundled reference set — every detail reference lives outside the skill directory and none ship with it.

Suggestions

State the 'channel-registry is the sole writer / operation: propose via registry-events.py' guardrail once in Skill Contract → Writes and refer back to it, instead of restating the full sentence in Scope guard, Done when, Save Results, and Reference Materials (~5 repetitions).

Include one concrete registry-events.py invocation example (command line with a sample propose payload for a graduation criterion) so step 8 is copy-paste executable rather than described.

Bundle the most load-bearing reference (e.g., the handoff-summary and save-results templates from skill-contract.md) inside the skill directory, or trim reliance on ../../../ paths that break when the skill is used outside the parent repo.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific configuration Claude cannot know (no filler concept explanations), but key guardrails are repeated many times: "[channel-registry] is the sole writer of memory/channels/" with the "authorized operation: propose request to registry-events.py" phrasing appears in the Scope guard, Writes, Done when, Save Results, and Reference Materials sections, and the anti-automation warning appears three times. This lands on 'mostly efficient but could be tightened' rather than anchor 4's 'minor instances that could be trimmed'.

3 / 5

Actionability

Guidance is largely concrete and executable: ledger columns are specified ("date, community, give/ask, link, note"), example graduation criteria are testable ("≥N weeks tenure … zero rule strikes, and a first non-promotional post accepted without moderator action"), connectors and file paths are named, and input routing (NEEDS_INPUT → channel-portfolio-planner) is explicit. It falls short of anchor 5 because the central write mechanism — the registry-events.py "operation: propose" request invoked four times — is never shown as an actual command or payload the agent could copy.

4 / 5

Workflow Clarity

Eight numbered steps in clear dependency order with an explicit input-stop checkpoint (step 1), labeling discipline, and a testable "Done when" checklist; the handoff and next-skill routing are unambiguous. It misses anchor 5 because there are no feedback/error-recovery loops (e.g., what to do when a propose request is rejected or a rules digest conflicts with an existing dossier), though as a non-destructive planning skill the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

Good structure with a dedicated, purpose-annotated Reference Materials section and one-level-deep, clearly signaled references (echo-benchmark.md, owned-community-loop.md, skill-contract.md, CONNECTORS.md, SECURITY.md). However, the bundle contains no reference files at all — every referenced path (and all sibling skill links) points outside the skill directory via ../../../ and none are present or verifiable here, so content split relies entirely on external repo structure rather than this skill's own bundle.

4 / 5

Total

15

/

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 exceptionally well-constructed description: verbatim trigger phrases in two languages, an explicit 'what' enumerating every deliverable, and an explicit negative boundary against the closest sibling skill. The only cost is length — at ~140 dense words it pushes against the verbosity guideline, though every clause carries information rather than fluff.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete deliverables — "account-history/tenure expectations (Estimated, named sources), a give-before-ask ledger spec, a per-community etiquette + rule digest with last-verified dates, and the warming → active graduation criteria" plus "the owned-community variant (entry paths + member lifecycle…)" — comprehensively covering the skill's outputs. This matches the anchor for multiple specific concrete actions with comprehensive coverage; the anchor below (4) would require minor gaps in coverage, but every output in the skill contract is named.

5 / 5

Completeness

Both halves are explicit: "Use when the user asks to …" gives concrete trigger phrases, and "produces the per-community pre-promotion warming plan — …" plus the enumerated deliverables answer 'what' in full. This mirrors the anchor-5 example (explicit what AND when with concrete trigger phrases); anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

It quotes three full natural user utterances verbatim ("plan the participation ramp before we promote", "how much account history or karma do we need in this community", "design entry incentives and member lifecycle for our own Discord") and adds bilingual synonyms (Discord/Slack/forum/企业微信私域, 社区预热/先给后取/账号养成/毕业标准). Trigger coverage is comprehensive with synonyms in two languages; nothing common is obviously missing.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (pre-promotion participation warming) and explicitly fences off the nearest sibling: "Not for launch-day submissions or T-0 threads — use community-launch-runner." Distinct triggers (participation ramp, warming, give-before-ask) and an explicit negative boundary give minimal conflict risk, matching the anchor-5 example's pattern.

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

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

social/explore/participation-warmup-planner/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.