CtrlK
BlogDocsLog inGet started
Tessl Logo

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. 社区预热/先给后取/账号养成/毕业标准

72

Quality

92%

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

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable instruction skill with a clear sequenced workflow and proper progressive disclosure. Its main weakness is conciseness — repeated guardrail statements and protocol framing inflate the token budget without adding guidance value.

Suggestions

Collapse the repeated "channel-registry is the sole writer of memory/channels/" statements into a single scope-guard note and reference it, removing the ~4 duplicate occurrences.

Trim the repeated ECHO sub-item mapping across the intro, Skill Contract, and Reference Materials to a single concise statement.

Consolidate the duplicated registry-proposal language ("authorized operation: propose request to registry-events.py to memory/events/channels.ndjson") into one canonical instruction referenced where needed.

DimensionReasoningScore

Conciseness

The body is mostly efficient but padded: phrases like "channel-registry is the sole writer of memory/channels/" recur roughly five times, and ECHO/protocol framing is repeated across sections, so it could be tightened without losing information. It avoids explaining concepts Claude already knows, keeping it above the score-1 anchor.

2 / 3

Actionability

Gives concrete, executable guidance — explicit ledger columns ("date, community, give/ask, link, note"), named connectors (discourse.py, hn.py, bluesky.py), exact file paths, and sample graduation criteria — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

An explicit 8-step numbered sequence with a NEEDS_INPUT stop, a "Done when" checklist, and validation gates (propose-only registry writes, "ask before writing", third-party-checkable criteria) provides clear checkpoints and feedback loops.

3 / 3

Progressive Disclosure

Content is split into a concise overview with a well-signaled, one-level-deep Reference Materials list pointing to sibling skills and reference files, with no nested reference chains; no bundle files are present locally to contradict the structure.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 comprehensive, trigger-rich, and well-differentiated with explicit when/what/when-not guidance, scoring the top anchor on every dimension. Its only weakness is verbosity — it is far longer than necessary and could be tightened without losing any of the score-driving elements.

DimensionReasoningScore

Specificity

Lists multiple concrete artifacts the skill produces — "account-history/tenure expectations", "a give-before-ask ledger spec", "an etiquette + rule digest with last-verified dates", and "warming → active graduation criteria" — matching the score-3 anchor.

3 / 3

Completeness

Opens with an explicit "Use when the user asks to..." clause and then states what the skill produces, clearly answering both what and when.

3 / 3

Trigger Term Quality

Quotes natural user phrasings ("plan the participation ramp before we promote", "how much account history or karma do we need", "design entry incentives and member lifecycle") alongside platform names, giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche plus an explicit negative-scope clause ("Not for launch-day submissions or T-0 threads — use community-launch-runner") that sharply reduces conflict with sibling skills.

3 / 3

Total

12

/

12

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.

Validation12 / 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
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.