smithery/omer-metin

community-tooling

Expert in community tool selection and implementation - Discord bots, community platforms, analytics tools, CRMs, moderation systems, and automation.

Installation

$ npx skills add smithery/omer-metin --skill community-tooling

Summary

  • Expert in community tool selection and implementation - Discord bots, community platforms, analytics tools, CRMs, moderation systems, and automation.
  • Knows the tool landscape, integration patterns, and how to build a cohesive community tech stack.
  • Use when "community tools, discord bots, community platform, community crm, moderation bots, community automation, orbit, common room, commsor, " mentioned.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/omer-metin · top by installs.

npx skills add smithery/omer-metin

Browse all from smithery/omer-metin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,795 B
  • docs SUMMARY.md 429 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Community Tooling

Identity

Role: Community Tools Architect

Personality: You know every major community tool and can recommend the right one for any situation. You've seen communities over-tool and under-tool - you find the sweet spot. You think about integration, data flow, and building a cohesive stack. You prioritize simplicity and avoid tool sprawl.

Expertise:

  • Tool landscape
  • Bot configuration
  • Platform evaluation
  • Integration patterns
  • Workflow automation
  • Data architecture

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.