CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

community-marketing

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

Quality

70%

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-organized, information-dense strategy guide: clear intake workflow, four sequenced playbooks, a practical platform table, concrete metric thresholds, and defined output formats. Its main gaps are the absence of actual message/post templates for the deliverables it names and minor restatements of general community knowledge.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific specifics ('Recruit 20–50 founding members', 'DAU/MAU ratio above 20% is healthy', '1% of members generate 90% of value') and assumes Claude's competence without basic-concept padding, though the flywheel ASCII diagram and identity-principle prose restate general community knowledge Claude partly has. Minor trims possible, matching 'Efficient; minor instances of over-explanation'.

4 / 5

Actionability

Concrete guidance throughout: numbered playbook steps with quantities ('Pre-populate channels with 5–10 posts'), a platform selection table with Best For / Watch Out For columns, metric thresholds, and six defined output formats. Falls short of fully copy-paste-ready because it names deliverables like 'DM template', 'pinned post', and 'outreach template' without providing any actual templates.

4 / 5

Workflow Clarity

Clear intake sequence (Before You Start questions → playbooks by goal → output formats) and numbered steps in all four playbooks, with warning-sign lists acting as diagnostic checkpoints. No destructive or batch operations, so the validation cap does not apply; not 5 because steps lack explicit verify-and-adjust feedback loops (e.g., re-check metrics 30 days post-launch).

4 / 5

Progressive Disclosure

Single-file skill with no bundle directories (references/, scripts/, assets/ absent) and no external file references; all content sits in one well-sectioned document with clear headers and a Related Skills cross-reference section. Good structure and appropriate placement for a ~155-line strategy skill, though platform-specific playbooks could arguably be split into reference files.

4 / 5

Total

16

/

20

Passed

Description

53%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 states a clear domain and intent but reads like marketing copy: it has no 'Use when...' trigger clause and omits natural platform keywords (Discord, Slack, Reddit) and role phrases (community management, ambassadors) that users would actually say. Adding explicit trigger guidance and concrete capability verbs would lift it substantially.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. 'Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a subreddit or forum, or build a brand ambassador program.'

Replace the generic verb 'leverage' with concrete capabilities such as 'launch communities, design channel architecture, define member journeys and rituals, and run ambassador programs'.

Include platform and role synonyms (Discord, Slack, Circle, Reddit, community management, word-of-mouth) to improve trigger-term coverage and distinctiveness against adjacent marketing skills.

DimensionReasoningScore

Specificity

Names the domain ('online communities') with two actions ('Build and leverage') plus outcomes ('product growth', 'brand loyalty'), but the verbs are generic and 'leverage' is buzzword-adjacent — matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the specific multi-action examples at level 4.

3 / 5

Completeness

The 'what' is clear (build and leverage online communities to drive growth and loyalty), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. Not 4 because the 'when' is entirely absent, not merely imprecise.

3 / 5

Trigger Term Quality

'online communities', 'product growth', and 'brand loyalty' are relevant keywords users might say, but common variations and synonyms are missing — no 'Discord', 'Slack', 'community management', 'brand ambassadors', or 'build a community' phrasing.

3 / 5

Distinctiveness Conflict Risk

'Online communities' carves a distinct niche with minimal conflict risk, but 'product growth' and 'brand loyalty' broadly overlap with adjacent marketing skills (referrals, social, product-marketing), matching 'mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

13

/

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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills/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.