Skip to content
cccskills
FreePublished on GitHub

bot-developer

Expert bot developer specializing in Discord, Telegram, Slack automation with deep knowledge of rate limiting, state machines, event sourcing, moderation systems, and conversational AI integration. Activate on 'Discord bot', 'Telegram bot', 'Slack bot', 'chat automation', 'moderation system'. NOT for web APIs (use backend-architect), general automation scripts (use python-pro), or frontend chat widgets (use frontend-developer).

The English summary is being prepared. Showing the original description.

See how to install

Files included (6)

  • SKILL.md5.6 KB
  • CHANGELOG.md1.3 KB
  • references/architecture-patterns.md7.1 KB
  • references/moderation-system.md6.5 KB
  • references/platform-templates.md5.5 KB
  • references/rate-limiting.md4.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Bot Developer

Expert in building production-grade bots with proper architecture, state management, and scalability.

Quick Start

User: "Build a Discord moderation bot with auto-mod"

Bot Developer:
1. Set up event-driven architecture (message broker + service layer)
2. Implement state machine for multi-turn mod flows
3. Add distributed rate limiting (Redis)
4. Create point-based moderation with decay
5. Configure auto-mod rules (spam, caps, links, words)
6. Deploy with proper logging and error handling

Key principle: Production bots need rate limiting, state management, and graceful degradation—not just command handlers.

Core Capabilities

1. Platform Expertise

PlatformConnectionBest For
DiscordGateway (WebSocket)Gaming communities, large servers
TelegramWebhook (production)International, groups/channels
SlackSocket Mode/WebhookWorkplace, integrations

2. Production Architecture

  • Event-driven design with message broker (Redis Streams / RabbitMQ)
  • Service layer separation (User, Moderation, Economy, Integration)
  • PostgreSQL + Redis + S3 data layer
  • Cog-based modular structure

3. State Management

  • Finite state machines for multi-turn conversations
  • Timeout handling (auto-reset after inactivity)
  • Race condition prevention
  • Context preservation across turns

4. Rate Limiting

  • Distributed limiter with Redis backend
  • Adaptive limiter responding to API headers
  • Per-user, per-guild, and global buckets
  • Graceful degradation with retry-after info

5. Moderation System

  • Point-based escalation (configurable thresholds)
  • Automatic decay over time
  • Auto-mod rules (spam, caps, links, banned words)
  • Fuzzy matching to catch bypass attempts (l33t speak)
  • Audit logging for compliance

Escalation Thresholds

PointsAction
0-2No action
3-5Mute
6-9Kick
10-14Temp Ban
15+Permanent Ban

Auto-Mod Rules

RuleDetection Method
SpamMessage frequency per sliding window
CapsCharacter ratio (>70% uppercase)
LinksURL regex + domain whitelist
WordsDictionary + Levenshtein (85% threshold)
Mentions@mention counting with variants
InvitesDiscord invite regex + URL expansion

When to Use

Use for:

  • Discord/Telegram/Slack bot development
  • Moderation and auto-mod systems
  • Multi-turn conversational flows
  • Economy/XP/leveling systems
  • Integration with external APIs

Do NOT use for:

  • Web APIs without chat interface (use backend-architect)
  • General automation scripts (use python-pro)
  • Frontend chat widgets (use frontend-developer)
  • AI/ML model integration alone (use ai-engineer)

Anti-Patterns

Anti-Pattern: Polling in Production

What it looks like: Using bot.polling() or long-polling for Telegram Why wrong: Wastes resources, slower response, can't scale Instead: Use webhooks with proper verification

Anti-Pattern: No Rate Limiting

What it looks like: Sending API requests without throttling Why wrong: Gets bot banned, triggers 429s, poor UX Instead: Implement adaptive rate limiter respecting API headers

Anti-Pattern: In-Memory State Only

What it looks like: Storing conversation state in Python dict Why wrong: Lost on restart, can't scale to multiple instances Instead: Redis for state, PostgreSQL for persistence

Anti-Pattern: Blocking Event Handlers

What it looks like: Long-running operations in on_message Why wrong: Blocks all other events, causes timeouts Instead: Async tasks, message queue for heavy work

Security Checklist

TOKEN SECURITY
├── Never commit tokens to git
├── Use environment variables or secret manager
├── Rotate tokens if exposed
└── Separate tokens for dev/staging/prod

PERMISSION CHECKS
├── Verify user permissions before action
├── Use platform's permission system
├── Check bot's permissions before attempting
└── Fail safely if permissions missing

INPUT VALIDATION
├── Sanitize all user input
├── Validate command arguments
├── Parameterized queries (no SQL injection)
└── Rate limit user-triggered actions

Reference Files

  • references/architecture-patterns.md - Event-driven architecture, state machines
  • references/rate-limiting.md - Distributed and adaptive rate limiting
  • references/moderation-system.md - Point-based moderation, auto-mod
  • references/platform-templates.md - Discord.py, Telegram webhook templates, security

Core insight: Production bots fail from rate limiting and state bugs, not from bad command logic. Build infrastructure first.

Use with: ai-engineer (LLM integration) | backend-architect (API design) | deployment-engineer (hosting)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Expert in 2000s-era music visualization (Milkdrop, AVS, Geiss) and modern WebGL implementations. Specializes in Butterchurn integration, Web Audio API AnalyserNode FFT data, GLSL shaders for audio-reactive visuals, and psychedelic generative art. Activate on "Milkdrop", "music visualization", "WebGL visualizer", "Butterchurn", "audio reactive", "FFT visualization", "spectrum analyzer". NOT for simple bar charts/waveforms (use basic canvas), video editing, or non-audio visuals.

The English summary is being prepared. Showing the original description.

curiositech/windags-skills16Updated Oct 14, 2026

Expert legal research agent for finding and scraping expungement data state by state. Knows authoritative sources, URL patterns, Firecrawl configuration, and 2026 legal landscape.

The English summary is being prepared. Showing the original description.

curiositech/windags-skills16Updated Oct 14, 2026

Expert in 3D computer vision labeling tools, workflows, and AI-assisted annotation for LiDAR, point clouds, and sensor fusion. Covers SAM4D/Point-SAM, human-in-the-loop architectures, and vertical-specific training strategies. Activate on '3D labeling', 'point cloud annotation', 'LiDAR labeling', 'SAM 3D', 'SAM4D', 'sensor fusion annotation', '3D bounding box', 'semantic segmentation point cloud'. NOT for 2D image labeling (use clip-aware-embeddings), general ML training (use ml-engineer), video annotation without 3D (use computer-vision-pipeline), or VLM prompt engineering (use prompt-engineer).

The English summary is being prepared. Showing the original description.

curiositech/windags-skills16Updated Oct 14, 2026

Apply crisis decision-making research to agent routing, uncertainty triage, and coordination failure analysis in time-pressured systems. Use when diagnosing handoff failures, analytical paralysis, or expert judgment under incomplete information. NOT for routine coding, simple CRUD design, or static single-agent tasks with complete information.

The English summary is being prepared. Showing the original description.

curiositech/windags-skills16Updated Oct 14, 2026

Use for insight, reframing, contradiction, impasse, and anomaly-driven problem solving when execution effort no longer helps. NOT for routine optimization, error correction, or well-specified tasks with known solution paths.

The English summary is being prepared. Showing the original description.

curiositech/windags-skills16Updated Oct 14, 2026

Apply normative BDI reasoning to agents that must detect norms, choose which commitments to internalize, and resolve conflicts by comparing consequences. Use when obligations, prohibitions, or policies collide in autonomous systems. NOT for simple fixed-priority rules, pure constraint satisfaction, or domains where no real normative conflict exists.

The English summary is being prepared. Showing the original description.

curiositech/windags-skills16Updated Oct 14, 2026

See all skills by curiositech

Report a problem with this skill