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-claude/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

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.

The body is a well-structured, actionable strategy guide with concrete playbooks, a platform comparison table, and quantified health metrics; its main weaknesses are a duplicated questions section that adds padding and named-but-unprovided templates that slightly reduce actionability.

Suggestions

Remove or merge the 'Task-Specific Questions' section into 'Before You Start' to eliminate the duplicated question list and save tokens.

Either provide the referenced 'DM template', 'outreach template', and welcome-sequence prompts inline or move them to a reference file rather than only naming them.

Drop the 'You are an expert community builder...' opener and the generic 'Always be specific...' closing line, which restate what Claude already does.

DimensionReasoningScore

Conciseness

The body is mostly tight (bullets, tables, minimal preamble), but the 'Task-Specific Questions' section largely duplicates the five 'Before You Start' questions and the opening 'You are an expert community builder...' role-play line adds padding, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Numbered playbooks give concrete, specific guidance ('Recruit 20–50 founding members manually', 'Pre-populate channels with 5–10 posts') and metrics include thresholds (DAU/MAU >20%), but referenced artifacts like 'DM template' and 'outreach template' are named in Output Formats without being provided, leaving minor gaps.

4 / 5

Workflow Clarity

Each playbook is a clearly numbered sequence (e.g., the 5-step launch playbook) and the Before-You-Start → strategy → output flow is coherent; this is a strategy skill with no destructive/batch operations, so the missing-checkpoint cap does not apply, but no explicit validation or feedback loops are present, matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

No bundle files exist and the content is well-organized under clear section headers (When to Use, Principles, Playbooks, Platform Guide, Metrics, Output Formats) with a Related Skills pointer list; at ~160 lines some material (platform guide, metrics) could arguably live in a reference file, leaving minor organization gaps.

4 / 5

Total

15

/

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 is third-person and names a clear domain with outcome-oriented actions, but it lacks any explicit 'Use when...' trigger guidance and relies on somewhat generic verbs, which limits specificity and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to launch or grow a Discord/Slack/Reddit community, build an advocate/ambassador program, or drive community-led growth.'

Replace generic verbs ('Build and leverage') with concrete actions ('Design community strategy, recruit founding members, run rituals, track health metrics').

Include platform and scenario keywords users actually say (Discord, Slack, Circle, subreddit, ambassador program, word-of-mouth) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Quotes 'Build and leverage online communities to drive product growth and brand loyalty' — names the domain plus two actions (build, leverage) and ties them to outcomes, but the verbs are fairly generic rather than concrete, matching the score-3 anchor 'names domain and 1-2 concrete actions, but not comprehensive'.

3 / 5

Completeness

The 'what' is clearly stated ('Build and leverage online communities...') but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like 'online communities' and 'product growth' appear, but common phrasings users actually say (Discord/Slack, 'grow my community', 'brand advocates') are absent, fitting 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

'Online communities' + 'product growth' + 'brand loyalty' carve a fairly distinct niche, but overlap risk exists with closely related skills (the body itself lists referrals, social, churn-prevention), 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.

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.