When the user wants to find Slack groups, Discord servers, Reddit communities, forums, or online communities where their target audience hangs out. Also use when the user mentions "where to promote", "find communities", "community marketing", or "distribution channels".
80
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/community-discovery/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with excellent trigger terms and completeness, clearly answering both what the skill does and when to use it. Its main weakness is that the 'what' portion could be more specific about the concrete actions or outputs the skill produces (e.g., does it generate a curated list, provide outreach strategies, analyze community relevance?). The description reads more as a trigger/routing specification than a capability description.
Suggestions
Add specific concrete actions/outputs the skill produces, e.g., 'Researches and compiles a curated list of relevant online communities with audience size, activity level, and promotion guidelines' instead of just 'find'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (finding online communities) and lists specific platforms (Slack, Discord, Reddit, forums), but doesn't describe concrete actions beyond 'find'. It lacks detail on what the skill actually produces or does (e.g., generates a list, provides links, analyzes audience fit). | 2 / 3 |
Completeness | The description clearly answers both 'what' (find online communities where target audience hangs out) and 'when' (explicit 'Also use when...' clause with specific trigger phrases like 'where to promote', 'find communities', 'community marketing'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'find Slack groups', 'Discord servers', 'Reddit communities', 'forums', 'online communities', 'where to promote', 'find communities', 'community marketing', 'distribution channels'. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | The skill has a clear niche focused specifically on finding online communities for audience/marketing purposes. The combination of platform-specific terms (Slack, Discord, Reddit) with marketing context ('target audience', 'promote', 'distribution channels') makes it distinctly identifiable and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid instructional skill with a well-structured workflow and useful output template. Its main weaknesses are moderate verbosity (some sections explain things Claude would know or could infer) and a monolithic structure that could benefit from splitting detailed reference material into separate files. The actionability is good for an instruction-only skill, with specific platform names, search tools, and a concrete engagement calendar template.
Suggestions
Trim the 'Common mistakes' and 'Red flags' sections to bullet points without elaboration — Claude can infer why these are problematic.
Move the platform-specific tactics table and detailed best practices into a separate COMMUNITY-TACTICS.md reference file, keeping only a brief summary and link in the main skill.
Add more specific search queries or techniques for each platform (e.g., exact Google search strings, Slofile filter parameters) to increase actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity — the 'Common mistakes' and 'Red flags' sections, while useful, could be tightened. The platform-specific tactics table is helpful but some entries state things Claude would already know (e.g., 'Never post direct ads' on Reddit). Overall mostly efficient with some bloat. | 2 / 3 |
Actionability | The skill provides concrete guidance on where to search (Slofile, Disboard, specific subreddits) and a clear engagement calendar template, but lacks executable code/commands since this is an instruction-only skill. The guidance is specific but still somewhat high-level — for example, 'search Slofile' without explaining how to use it effectively. The output template is concrete and copy-paste ready, which helps. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with logical progression: map → qualify → categorize → plan → output. Each step has explicit sub-criteria. The engagement calendar provides a built-in validation/feedback loop (observe before posting, contribute before promoting). For a non-destructive research/planning task, this level of workflow clarity is excellent. | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom (cold-outreach, content-strategy, etc.) which is good navigation. However, the content is quite long and monolithic — the platform-specific tactics table, frameworks, red flags, and common mistakes sections could potentially be split into a separate reference file. Everything is inline in one document with no external references for deeper dives. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
4ad31b4
Table of Contents
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.