CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."

Quality

89%

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

78%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 strategy skill: lean playbooks with concrete numbers, a clean platform comparison, measurable health metrics, and exemplary use of a single well-signaled reference file. Main improvement opportunities are deduplicating the repeated intake questions and providing skeleton examples for the templates it promises.

Suggestions

Merge the "Task-Specific Questions" section into "Before You Start" — four of the six questions (platform, stage, goal, ideal member) duplicate it almost verbatim.

Add a brief skeleton or example for at least one promised output template (e.g., the new-member DM or welcome post) so the deliverables are concrete rather than named.

Add a short routing note in "Output Formats" telling the reader to confirm which artifact the user wants before generating a full document.

DimensionReasoningScore

Conciseness

The body is largely efficient — terse numbered playbooks, a compact platform table, and metrics with concrete thresholds ("Above 20% is healthy") — but the "Task-Specific Questions" section repeats four of the five questions from "Before You Start" nearly verbatim, and the flywheel/principles prose could be tightened slightly. This sits between 'mostly efficient but could be tightened' (3) and clearly efficient (4), noticeably above the midpoint.

4 / 5

Actionability

Guidance is concrete with specific numbers and tactics ("Recruit 20–50 founding members", "Pre-populate channels with 5–10 posts", "1% of members generate 90% of value") and defined output formats — actionable for an instruction-only skill. It stops short of fully executable level 5 because promised templates (welcome post, DM template, outreach template) are named as outputs but no example content or skeleton is provided.

4 / 5

Workflow Clarity

Each playbook is a clearly numbered 4–5 step sequence, and the overall arc (context → model selection → platform → playbook → metrics → output format) is coherent with explicit routing to the reference file. No destructive or batch operations apply, so no validation cap; it misses level 5 only because there are no explicit checkpoints (e.g., confirming which output format the user wants before producing it).

4 / 5

Progressive Disclosure

The single bundle file references/community-models.md exists, is referenced one level deep with a clear signal ("See references/community-models.md for:"), summarizes its contents in bullets, and includes routing guidance ("Route here when the user asks what kind of community..."). The split is appropriate — models/benchmark/scaling phases out, tactics inline — matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

17

/

20

Passed

Description

96%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: concrete third-person capabilities, an explicit 'Use when' clause, and a comprehensive natural-language trigger list. The only weakness is mild overlap between some triggers (ambassador/advocates) and adjacent marketing skills.

Suggestions

Differentiate the ambassador-related triggers (e.g., "ambassador program", "brand advocates") from a potential referrals skill by scoping them to community context, such as "community ambassador program".

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "create a community strategy", "grow a Discord or Slack community", "manage a forum or subreddit", "build brand advocates", "engage users post-signup", "turn customers into evangelists" — comprehensively covering the community-marketing domain in third person. It matches the 'lists multiple specific concrete actions; comprehensive coverage' anchor and exceeds the level-4 example, which shows only minor gaps in coverage.

5 / 5

Completeness

It explicitly answers both 'what' ("Build and leverage online communities to drive product growth and brand loyalty" with enumerated capabilities) and 'when' ("Use when the user wants to..." plus a dedicated "Trigger phrases:" list with concrete phrases). This mirrors the level-5 example structure exactly; level 4 would require the 'when' to be less explicit, which is not the case here.

5 / 5

Trigger Term Quality

An explicit trigger list provides comprehensive natural phrases users would actually say: "build a community", "Discord community", "community strategy", "brand advocates", "ambassador program", "grow our community", plus synonyms and platform variants (Slack, forum, subreddit, user community). Coverage including synonyms matches the level-5 anchor; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The community-building niche is mostly distinct with clear triggers, but phrases like "ambassador program" and "brand advocates" overlap with closely related skills the body itself lists (e.g., referrals, social), creating minor conflict risk. It fits 'mostly distinct; minor overlap risk with closely related skills' rather than level 5's 'minimal conflict risk'.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/community-marketing/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.