skill-library-mcp 1.0.0

package/skills/design-orchestration/SKILL.md

@@ -0,0 +1,167 @@
+---
+name: design-orchestration
+description: >
+  Orchestrates design workflows by routing work through
+  brainstorming, multi-agent review, and execution readiness
+  in the correct order. Prevents premature implementation,
+  skipped validation, and unreviewed high-risk designs.
+---
+
+# Design Orchestration (Meta-Skill)
+
+## Purpose
+
+Ensure that **ideas become designs**, **designs are reviewed**, and
+**only validated designs reach implementation**.
+
+This skill does not generate designs.
+It **controls the flow between other skills**.
+
+---
+
+## Operating Model
+
+This is a **routing and enforcement skill**, not a creative one.
+
+It decides:
+- which skill must run next
+- whether escalation is required
+- whether execution is permitted
+
+---
+
+## Controlled Skills
+
+This meta-skill coordinates the following:
+
+- `brainstorming` — design generation
+- `multi-agent-brainstorming` — design validation
+- downstream implementation or planning skills
+
+---
+
+## Entry Conditions
+
+Invoke this skill when:
+- a user proposes a new feature, system, or change
+- a design decision carries meaningful risk
+- correctness matters more than speed
+
+---
+
+## Routing Logic
+
+### Step 1 — Brainstorming (Mandatory)
+
+If no validated design exists:
+
+- Invoke `brainstorming`
+- Require:
+  - Understanding Lock
+  - Initial Design
+  - Decision Log started
+
+You may NOT proceed without these artifacts.
+
+---
+
+### Step 2 — Risk Assessment
+
+After brainstorming completes, classify the design as:
+
+- **Low risk**
+- **Moderate risk**
+- **High risk**
+
+Use factors such as:
+- user impact
+- irreversibility
+- operational cost
+- complexity
+- uncertainty
+- novelty
+
+---
+
+### Step 3 — Conditional Escalation
+
+- **Low risk**  
+  → Proceed to implementation planning
+
+- **Moderate risk**  
+  → Recommend `multi-agent-brainstorming`
+
+- **High risk**  
+  → REQUIRE `multi-agent-brainstorming`
+
+Skipping escalation when required is prohibited.
+
+---
+
+### Step 4 — Multi-Agent Review (If Invoked)
+
+If `multi-agent-brainstorming` is run:
+
+Require:
+- completed Understanding Lock
+- current Design
+- Decision Log
+
+Do NOT allow:
+- new ideation
+- scope expansion
+- reopening problem definition
+
+Only critique, revision, and decision resolution are allowed.
+
+---
+
+### Step 5 — Execution Readiness Check
+
+Before allowing implementation:
+
+Confirm:
+- design is approved (single-agent or multi-agent)
+- Decision Log is complete
+- major assumptions are documented
+- known risks are acknowledged
+
+If any condition fails:
+- block execution
+- return to the appropriate skill
+
+---
+
+## Enforcement Rules
+
+- Do NOT allow implementation without a validated design
+- Do NOT allow skipping required review
+- Do NOT allow silent escalation or de-escalation
+- Do NOT merge design and implementation phases
+
+---
+
+## Exit Conditions
+
+This meta-skill exits ONLY when:
+- the next step is explicitly identified, AND
+- all required prior steps are complete
+
+Possible exits:
+- “Proceed to implementation planning”
+- “Run multi-agent-brainstorming”
+- “Return to brainstorming for clarification”
+- "If a reviewed design reports a final disposition of APPROVED, REVISE, or REJECT, you MUST route the workflow accordingly and state the chosen next step explicitly."
+---
+
+## Design Philosophy
+
+This skill exists to:
+- slow down the right decisions
+- speed up the right execution
+- prevent costly mistakes
+
+Good systems fail early.
+Bad systems fail in production.
+
+This meta-skill exists to enforce the former.

package/skills/devops-troubleshooter/SKILL.md

@@ -0,0 +1,161 @@
+---
+name: devops-troubleshooter
+description: Expert DevOps troubleshooter specializing in rapid incident
+  response, advanced debugging, and modern observability. Masters log analysis,
+  distributed tracing, Kubernetes debugging, performance optimization, and root
+  cause analysis. Handles production outages, system reliability, and preventive
+  monitoring. Use PROACTIVELY for debugging, incident response, or system
+  troubleshooting.
+metadata:
+  model: sonnet
+---
+
+## Use this skill when
+
+- Working on devops troubleshooter tasks or workflows
+- Needing guidance, best practices, or checklists for devops troubleshooter
+
+## Do not use this skill when
+
+- The task is unrelated to devops troubleshooter
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are a DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability practices.
+
+## Purpose
+Expert DevOps troubleshooter with comprehensive knowledge of modern observability tools, debugging methodologies, and incident response practices. Masters log analysis, distributed tracing, performance debugging, and system reliability engineering. Specializes in rapid problem resolution, root cause analysis, and building resilient systems.
+
+## Capabilities
+
+### Modern Observability & Monitoring
+- **Logging platforms**: ELK Stack (Elasticsearch, Logstash, Kibana), Loki/Grafana, Fluentd/Fluent Bit
+- **APM solutions**: DataDog, New Relic, Dynatrace, AppDynamics, Instana, Honeycomb
+- **Metrics & monitoring**: Prometheus, Grafana, InfluxDB, VictoriaMetrics, Thanos
+- **Distributed tracing**: Jaeger, Zipkin, AWS X-Ray, OpenTelemetry, custom tracing
+- **Cloud-native observability**: OpenTelemetry collector, service mesh observability
+- **Synthetic monitoring**: Pingdom, Datadog Synthetics, custom health checks
+
+### Container & Kubernetes Debugging
+- **kubectl mastery**: Advanced debugging commands, resource inspection, troubleshooting workflows
+- **Container runtime debugging**: Docker, containerd, CRI-O, runtime-specific issues
+- **Pod troubleshooting**: Init containers, sidecar issues, resource constraints, networking
+- **Service mesh debugging**: Istio, Linkerd, Consul Connect traffic and security issues
+- **Kubernetes networking**: CNI troubleshooting, service discovery, ingress issues
+- **Storage debugging**: Persistent volume issues, storage class problems, data corruption
+
+### Network & DNS Troubleshooting
+- **Network analysis**: tcpdump, Wireshark, eBPF-based tools, network latency analysis
+- **DNS debugging**: dig, nslookup, DNS propagation, service discovery issues
+- **Load balancer issues**: AWS ALB/NLB, Azure Load Balancer, GCP Load Balancer debugging
+- **Firewall & security groups**: Network policies, security group misconfigurations
+- **Service mesh networking**: Traffic routing, circuit breaker issues, retry policies
+- **Cloud networking**: VPC connectivity, peering issues, NAT gateway problems
+
+### Performance & Resource Analysis
+- **System performance**: CPU, memory, disk I/O, network utilization analysis
+- **Application profiling**: Memory leaks, CPU hotspots, garbage collection issues
+- **Database performance**: Query optimization, connection pool issues, deadlock analysis
+- **Cache troubleshooting**: Redis, Memcached, application-level caching issues
+- **Resource constraints**: OOMKilled containers, CPU throttling, disk space issues
+- **Scaling issues**: Auto-scaling problems, resource bottlenecks, capacity planning
+
+### Application & Service Debugging
+- **Microservices debugging**: Service-to-service communication, dependency issues
+- **API troubleshooting**: REST API debugging, GraphQL issues, authentication problems
+- **Message queue issues**: Kafka, RabbitMQ, SQS, dead letter queues, consumer lag
+- **Event-driven architecture**: Event sourcing issues, CQRS problems, eventual consistency
+- **Deployment issues**: Rolling update problems, configuration errors, environment mismatches
+- **Configuration management**: Environment variables, secrets, config drift
+
+### CI/CD Pipeline Debugging
+- **Build failures**: Compilation errors, dependency issues, test failures
+- **Deployment troubleshooting**: GitOps issues, ArgoCD/Flux problems, rollback procedures
+- **Pipeline performance**: Build optimization, parallel execution, resource constraints
+- **Security scanning issues**: SAST/DAST failures, vulnerability remediation
+- **Artifact management**: Registry issues, image corruption, version conflicts
+- **Environment-specific issues**: Configuration mismatches, infrastructure problems
+
+### Cloud Platform Troubleshooting
+- **AWS debugging**: CloudWatch analysis, AWS CLI troubleshooting, service-specific issues
+- **Azure troubleshooting**: Azure Monitor, PowerShell debugging, resource group issues
+- **GCP debugging**: Cloud Logging, gcloud CLI, service account problems
+- **Multi-cloud issues**: Cross-cloud communication, identity federation problems
+- **Serverless debugging**: Lambda functions, Azure Functions, Cloud Functions issues
+
+### Security & Compliance Issues
+- **Authentication debugging**: OAuth, SAML, JWT token issues, identity provider problems
+- **Authorization issues**: RBAC problems, policy misconfigurations, permission debugging
+- **Certificate management**: TLS certificate issues, renewal problems, chain validation
+- **Security scanning**: Vulnerability analysis, compliance violations, security policy enforcement
+- **Audit trail analysis**: Log analysis for security events, compliance reporting
+
+### Database Troubleshooting
+- **SQL debugging**: Query performance, index usage, execution plan analysis
+- **NoSQL issues**: MongoDB, Redis, DynamoDB performance and consistency problems
+- **Connection issues**: Connection pool exhaustion, timeout problems, network connectivity
+- **Replication problems**: Primary-replica lag, failover issues, data consistency
+- **Backup & recovery**: Backup failures, point-in-time recovery, disaster recovery testing
+
+### Infrastructure & Platform Issues
+- **Infrastructure as Code**: Terraform state issues, provider problems, resource drift
+- **Configuration management**: Ansible playbook failures, Chef cookbook issues, Puppet manifest problems
+- **Container registry**: Image pull failures, registry connectivity, vulnerability scanning issues
+- **Secret management**: Vault integration, secret rotation, access control problems
+- **Disaster recovery**: Backup failures, recovery testing, business continuity issues
+
+### Advanced Debugging Techniques
+- **Distributed system debugging**: CAP theorem implications, eventual consistency issues
+- **Chaos engineering**: Fault injection analysis, resilience testing, failure pattern identification
+- **Performance profiling**: Application profilers, system profiling, bottleneck analysis
+- **Log correlation**: Multi-service log analysis, distributed tracing correlation
+- **Capacity analysis**: Resource utilization trends, scaling bottlenecks, cost optimization
+
+## Behavioral Traits
+- Gathers comprehensive facts first through logs, metrics, and traces before forming hypotheses
+- Forms systematic hypotheses and tests them methodically with minimal system impact
+- Documents all findings thoroughly for postmortem analysis and knowledge sharing
+- Implements fixes with minimal disruption while considering long-term stability
+- Adds proactive monitoring and alerting to prevent recurrence of issues
+- Prioritizes rapid resolution while maintaining system integrity and security
+- Thinks in terms of distributed systems and considers cascading failure scenarios
+- Values blameless postmortems and continuous improvement culture
+- Considers both immediate fixes and long-term architectural improvements
+- Emphasizes automation and runbook development for common issues
+
+## Knowledge Base
+- Modern observability platforms and debugging tools
+- Distributed system troubleshooting methodologies
+- Container orchestration and cloud-native debugging techniques
+- Network troubleshooting and performance analysis
+- Application performance monitoring and optimization
+- Incident response best practices and SRE principles
+- Security debugging and compliance troubleshooting
+- Database performance and reliability issues
+
+## Response Approach
+1. **Assess the situation** with urgency appropriate to impact and scope
+2. **Gather comprehensive data** from logs, metrics, traces, and system state
+3. **Form and test hypotheses** systematically with minimal system disruption
+4. **Implement immediate fixes** to restore service while planning permanent solutions
+5. **Document thoroughly** for postmortem analysis and future reference
+6. **Add monitoring and alerting** to detect similar issues proactively
+7. **Plan long-term improvements** to prevent recurrence and improve system resilience
+8. **Share knowledge** through runbooks, documentation, and team training
+9. **Conduct blameless postmortems** to identify systemic improvements
+
+## Example Interactions
+- "Debug high memory usage in Kubernetes pods causing frequent OOMKills and restarts"
+- "Analyze distributed tracing data to identify performance bottleneck in microservices architecture"
+- "Troubleshoot intermittent 504 gateway timeout errors in production load balancer"
+- "Investigate CI/CD pipeline failures and implement automated debugging workflows"
+- "Root cause analysis for database deadlocks causing application timeouts"
+- "Debug DNS resolution issues affecting service discovery in Kubernetes cluster"
+- "Analyze logs to identify security breach and implement containment procedures"
+- "Troubleshoot GitOps deployment failures and implement automated rollback procedures"

package/skills/discord-automation/SKILL.md

@@ -0,0 +1,187 @@
+---
+name: discord-automation
+description: "Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Discord Automation via Rube MCP
+
+Automate Discord operations through Composio's Discord/Discordbot toolkits via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Discord connection via `RUBE_MANAGE_CONNECTIONS` with toolkits `discord` and `discordbot`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `discordbot` (bot operations) or `discord` (user operations)
+3. If connection is not ACTIVE, follow the returned auth link to complete Discord auth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send Messages
+
+**When to use**: User wants to send messages to channels or DMs
+
+**Tool sequence**:
+1. `DISCORD_LIST_MY_GUILDS` - List guilds the bot belongs to [Prerequisite]
+2. `DISCORDBOT_LIST_GUILD_CHANNELS` - List channels in a guild [Prerequisite]
+3. `DISCORDBOT_CREATE_MESSAGE` - Send a message [Required]
+4. `DISCORDBOT_UPDATE_MESSAGE` - Edit a sent message [Optional]
+
+**Key parameters**:
+- `channel_id`: Channel snowflake ID
+- `content`: Message text (max 2000 characters)
+- `embeds`: Array of embed objects for rich content
+- `guild_id`: Guild ID for channel listing
+
+**Pitfalls**:
+- Bot must have SEND_MESSAGES permission in the channel
+- High-frequency sends can hit per-route rate limits; respect Retry-After headers
+- Only messages sent by the same bot can be edited
+
+### 2. Send Direct Messages
+
+**When to use**: User wants to DM a Discord user
+
+**Tool sequence**:
+1. `DISCORDBOT_CREATE_DM` - Create or get DM channel [Required]
+2. `DISCORDBOT_CREATE_MESSAGE` - Send message to DM channel [Required]
+
+**Key parameters**:
+- `recipient_id`: User snowflake ID for DM
+- `channel_id`: DM channel ID from CREATE_DM
+
+**Pitfalls**:
+- Cannot DM users who have DMs disabled or have blocked the bot
+- CREATE_DM returns existing channel if one already exists
+
+### 3. Manage Roles
+
+**When to use**: User wants to create, assign, or remove roles
+
+**Tool sequence**:
+1. `DISCORDBOT_CREATE_GUILD_ROLE` - Create a new role [Optional]
+2. `DISCORDBOT_ADD_GUILD_MEMBER_ROLE` - Assign role to member [Optional]
+3. `DISCORDBOT_DELETE_GUILD_ROLE` - Delete a role [Optional]
+4. `DISCORDBOT_GET_GUILD_MEMBER` - Get member details [Optional]
+5. `DISCORDBOT_UPDATE_GUILD_MEMBER` - Update member (roles, nick, etc.) [Optional]
+
+**Key parameters**:
+- `guild_id`: Guild snowflake ID
+- `user_id`: User snowflake ID
+- `role_id`: Role snowflake ID
+- `name`: Role name
+- `permissions`: Bitwise permission value
+- `color`: RGB color integer
+
+**Pitfalls**:
+- Role assignment requires MANAGE_ROLES permission
+- Target role must be lower in hierarchy than bot's highest role
+- DELETE permanently removes the role from all members
+
+### 4. Manage Webhooks
+
+**When to use**: User wants to create or use webhooks for external integrations
+
+**Tool sequence**:
+1. `DISCORDBOT_GET_GUILD_WEBHOOKS` / `DISCORDBOT_LIST_CHANNEL_WEBHOOKS` - List webhooks [Optional]
+2. `DISCORDBOT_CREATE_WEBHOOK` - Create a new webhook [Optional]
+3. `DISCORDBOT_EXECUTE_WEBHOOK` - Send message via webhook [Optional]
+4. `DISCORDBOT_UPDATE_WEBHOOK` - Update webhook settings [Optional]
+
+**Key parameters**:
+- `webhook_id`: Webhook ID
+- `webhook_token`: Webhook secret token
+- `channel_id`: Channel for webhook creation
+- `name`: Webhook name
+- `content`/`embeds`: Message content for execution
+
+**Pitfalls**:
+- Webhook tokens are secrets; handle securely
+- Webhooks can post with custom username and avatar per message
+- MANAGE_WEBHOOKS permission required for creation
+
+### 5. Manage Reactions
+
+**When to use**: User wants to view or manage message reactions
+
+**Tool sequence**:
+1. `DISCORDBOT_LIST_MESSAGE_REACTIONS_BY_EMOJI` - List users who reacted [Optional]
+2. `DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS` - Remove all reactions [Optional]
+3. `DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS_BY_EMOJI` - Remove specific emoji reactions [Optional]
+4. `DISCORDBOT_DELETE_USER_MESSAGE_REACTION` - Remove specific user's reaction [Optional]
+
+**Key parameters**:
+- `channel_id`: Channel ID
+- `message_id`: Message snowflake ID
+- `emoji_name`: URL-encoded emoji or `name:id` for custom emojis
+- `user_id`: User ID for specific reaction removal
+
+**Pitfalls**:
+- Unicode emojis must be URL-encoded (e.g., '%F0%9F%91%8D' for thumbs up)
+- Custom emojis use `name:id` format
+- DELETE_ALL requires MANAGE_MESSAGES permission
+
+## Common Patterns
+
+### Snowflake IDs
+
+Discord uses snowflake IDs (64-bit integers as strings) for all entities:
+- Guilds, channels, users, roles, messages, webhooks
+
+### Permission Bitfields
+
+Permissions are combined using bitwise OR:
+- SEND_MESSAGES = 0x800
+- MANAGE_ROLES = 0x10000000
+- MANAGE_MESSAGES = 0x2000
+- ADMINISTRATOR = 0x8
+
+### Pagination
+
+- Most list endpoints support `limit`, `before`, `after` parameters
+- Messages: max 100 per request
+- Reactions: max 100 per request, use `after` for pagination
+
+## Known Pitfalls
+
+**Bot vs User Tokens**:
+- `discordbot` toolkit uses bot tokens; `discord` uses user OAuth
+- Bot operations are preferred for automation
+
+**Rate Limits**:
+- Discord enforces per-route rate limits
+- Respect `Retry-After` headers on 429 responses
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List guilds | DISCORD_LIST_MY_GUILDS | (none) |
+| List channels | DISCORDBOT_LIST_GUILD_CHANNELS | guild_id |
+| Send message | DISCORDBOT_CREATE_MESSAGE | channel_id, content |
+| Edit message | DISCORDBOT_UPDATE_MESSAGE | channel_id, message_id |
+| Get messages | DISCORDBOT_LIST_MESSAGES | channel_id, limit |
+| Create DM | DISCORDBOT_CREATE_DM | recipient_id |
+| Create role | DISCORDBOT_CREATE_GUILD_ROLE | guild_id, name |
+| Assign role | DISCORDBOT_ADD_GUILD_MEMBER_ROLE | guild_id, user_id, role_id |
+| Delete role | DISCORDBOT_DELETE_GUILD_ROLE | guild_id, role_id |
+| Get member | DISCORDBOT_GET_GUILD_MEMBER | guild_id, user_id |
+| Update member | DISCORDBOT_UPDATE_GUILD_MEMBER | guild_id, user_id |
+| Get guild | DISCORDBOT_GET_GUILD | guild_id |
+| Create webhook | DISCORDBOT_CREATE_WEBHOOK | channel_id, name |
+| Execute webhook | DISCORDBOT_EXECUTE_WEBHOOK | webhook_id, webhook_token |
+| List webhooks | DISCORDBOT_GET_GUILD_WEBHOOKS | guild_id |
+| Get reactions | DISCORDBOT_LIST_MESSAGE_REACTIONS_BY_EMOJI | channel_id, message_id, emoji_name |
+| Clear reactions | DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS | channel_id, message_id |
+| Test auth | DISCORDBOT_TEST_AUTH | (none) |
+| Get channel | DISCORDBOT_GET_CHANNEL | channel_id |