CtrlK
BlogDocsLog inGet started
Tessl Logo

community-marketing

Build and leverage online communities to drive product growth and brand loyalty.

53

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/community-marketing/SKILL.md

The canonical home for this skill is community-marketing in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured, actionable strategy guide with concrete playbooks, a platform comparison, and measurable health signals; it respects the reader's competence and stays mostly lean, with only minor gaps in filled templates and explicit validation loops.

DimensionReasoningScore

Conciseness

The body is well-organized and assumes Claude's competence (it never explains what Discord or communities are), with only minor padding such as the opening persona line; this matches 'efficient; minor instances of over-explanation that could be trimmed' rather than 5 because the persona opener and a few meta-lines could still be cut.

4 / 5

Actionability

Numbered playbooks give concrete, specific guidance with real numbers (20–50 founding members, 5–10 seed posts, 20% DAU/MAU threshold, 1%/90% power-user rule), and as an instruction-only skill absence of code is not penalized; it is not 5 because deliverables like the welcome DM and ambassador outreach template are named but not actually shown.

4 / 5

Workflow Clarity

Playbooks are clearly numbered sequences, and the health-metrics 'Warning signs', the 'Audit where members drop off' step, and 'Measure and iterate' provide diagnostic checkpoints and a feedback loop; the destructive/batch cap does not apply here, and it stops at 4 because explicit if/then recovery loops are not systematic across playbooks.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained, with clear section headers and a Related Skills cross-reference list; structure is good with content appropriately placed and no nested or buried references, matching 'good structure; most content appropriately placed; minor organization gaps', but not 5 because nothing is split into one-level-deep reference files.

4 / 5

Total

16

/

20

Passed

Description

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

The description clearly states the domain and intended business outcomes but lacks concrete actions, natural trigger phrases, and any 'Use when...' guidance, so it reads more as a mission statement than a skill trigger.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases (e.g., 'Use when growing a Discord or Slack community, building a brand ambassador program, or driving word-of-mouth and community-led growth').

Replace generic verbs ('Build and leverage') with concrete actions (e.g., 'design, launch, and grow a community, build an ambassador program, and run community rituals and health audits').

Add platform and scenario keywords users actually say — Discord, Slack, Circle, Reddit, brand advocates, evangelists, retention, word-of-mouth — to improve trigger-term coverage and distinctiveness from adjacent marketing skills.

DimensionReasoningScore

Specificity

Phrases like 'Build and leverage online communities' name the domain and an outcome ('drive product growth and brand loyalty') but the verbs are generic/abstract with no concrete actions, matching the anchor for 'names the domain but actions are minimal or generic'; it does not reach 3 because nothing is as concrete as 'extract text'.

2 / 5

Completeness

The 'what' is clear (build and leverage communities to drive growth/loyalty) but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3 ('has a clear what but when is missing'); not 4 because no explicit when is provided.

3 / 5

Trigger Term Quality

It includes some natural terms ('online communities', 'product growth', 'brand loyalty') but misses common variations and synonyms a user would actually say (Discord, Slack, brand advocates, word-of-mouth, community-led growth), matching 'some relevant keywords but missing common variations'; not 4 because platform/action synonyms are absent.

3 / 5

Distinctiveness Conflict Risk

'online communities' is a distinct niche, but 'product growth and brand loyalty' overlaps with adjacent marketing skills (social, referrals, brand, retention) and the description offers no disambiguating triggers, matching 'somewhat specific but could still overlap with similar skills'; not 4 because the overlap with closely related marketing skills is real.

3 / 5

Total

11

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.