Menu
Monitor Discord community channel for user-reported bugs and issues
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create, list, deactivate, and reactivate API keys for rate limiting
Create, list, update, and delete API rate limiting tiers
Fetch the most urgent Linear issue with tag "studio" and size XS, then fix it
Fetch, analyze, fix Sentry issues, run tests, and create PRs
Setup Python virtual environment and run integration tests with gltest
Debug GenLayer Studio deployments via ArgoCD CLI
| name | discord-community-feedback |
| description | Monitor Discord community channel for user-reported bugs and issues |
Monitor the GenLayer Discord community feedback channel for user-reported bugs, issues, and problems.
| Field | Value |
|---|---|
| Server ID | 1237055789441487021 |
| Channel ID | 1237114454877929482 |
Use the Discord MCP read-messages tool to fetch recent messages:
Tool: read-messages
Channel: 1237114454877929482
Limit: 100 (max allowed)
When reviewing messages, look for these indicators of issues:
| Category | Example Patterns | Related Component |
|---|---|---|
| Transaction failures | "tx failed", "transaction stuck" | consensus-worker |
| Contract errors | "contract not deploying", "execution error" | genvm, consensus-worker |
| UI issues | "page not loading", "button doesn't work" | frontend |
| API errors | "RPC error", "connection failed" | jsonrpc |
| Wallet issues | "can't connect wallet", "balance wrong" | frontend, jsonrpc |
hosted-studio-debug skill if needed| Priority | Indicators |
|---|---|
| High | Multiple users reporting same issue, "everything broken", data loss |
| Medium | Single user with reproducible issue, feature not working |
| Low | Questions, minor UI glitches, feature requests |
If a user reports an issue that might be related to the hosted environment:
hosted-studio-debug skill to check logs around that time# Example: Check for errors around the time of a user report
argocd app logs studio-prd-workload --name studio-consensus-worker --tail 500 2>&1 | grep -iE "(error|exception|timeout)"
When summarizing community feedback:
## Community Feedback Summary
**Period**: [time range of messages reviewed]
**Total Messages**: [count]
**Issues Identified**: [count]
### High Priority
- [Issue description] - Reported by [count] users
### Medium Priority
- [Issue description]
### Low Priority / Questions
- [Description]
### No Issues
[If no problems found, note this]