Discord Community Feedback Skill
Monitor the GenLayer Discord community feedback channel for user-reported bugs, issues, and problems.
Prerequisites
- Discord MCP server configured and running (discordmcp)
- Bot added to the GenLayer Discord server with read permissions
Channel Information
| Field |
Value |
| Server ID |
1237055789441487021 |
| Channel ID |
1237114454877929482 |
Quick Commands
Use the Discord MCP read-messages tool to fetch recent messages:
Tool: read-messages
Channel: 1237114454877929482
Limit: 100 (max allowed)
Identifying User Problems
When reviewing messages, look for these indicators of issues:
Problem Keywords
- Errors: error, bug, broken, crash, fail, exception
- Functionality: not working, doesn't work, can't, unable, stuck
- Help requests: help, issue, problem, wrong, weird
- Performance: slow, timeout, hang, freeze, unresponsive
Common User-Reported 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 |
Workflow
- Fetch recent messages from the feedback channel (up to 100)
- Scan for problem indicators using keywords above
- Categorize issues by component (frontend, backend, consensus, etc.)
- Cross-reference with logs using the
hosted-studio-debug skill if needed
- Summarize findings for the team
Triage Priority
| 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 |
Integration with Hosted Studio Debug
If a user reports an issue that might be related to the hosted environment:
- Note the approximate time of the user's report
- Use
hosted-studio-debug skill to check logs around that time
- Look for correlating errors in consensus-worker or jsonrpc logs
# 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)"
Response Template
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]
1---2name: discord-community-feedback3description: Monitor Discord community channel for user-reported bugs and issues4---56# Discord Community Feedback Skill78Monitor the GenLayer Discord community feedback channel for user-reported bugs, issues, and problems.910## Prerequisites1112- Discord MCP server configured and running ([discordmcp](https://github.com/v-3/discordmcp))13- Bot added to the GenLayer Discord server with read permissions1415## Channel Information1617| Field | Value |18|-------|-------|19| Server ID | 1237055789441487021 |20| Channel ID | 1237114454877929482 |2122## Quick Commands2324Use the Discord MCP `read-messages` tool to fetch recent messages:2526```27Tool: read-messages28Channel: 123711445487792948229Limit: 100 (max allowed)30```3132## Identifying User Problems3334When reviewing messages, look for these indicators of issues:3536### Problem Keywords37- **Errors**: error, bug, broken, crash, fail, exception38- **Functionality**: not working, doesn't work, can't, unable, stuck39- **Help requests**: help, issue, problem, wrong, weird40- **Performance**: slow, timeout, hang, freeze, unresponsive4142### Common User-Reported Issues4344| Category | Example Patterns | Related Component |45|----------|------------------|-------------------|46| Transaction failures | "tx failed", "transaction stuck" | consensus-worker |47| Contract errors | "contract not deploying", "execution error" | genvm, consensus-worker |48| UI issues | "page not loading", "button doesn't work" | frontend |49| API errors | "RPC error", "connection failed" | jsonrpc |50| Wallet issues | "can't connect wallet", "balance wrong" | frontend, jsonrpc |5152## Workflow53541. **Fetch recent messages** from the feedback channel (up to 100)552. **Scan for problem indicators** using keywords above563. **Categorize issues** by component (frontend, backend, consensus, etc.)574. **Cross-reference with logs** using the `hosted-studio-debug` skill if needed585. **Summarize findings** for the team5960## Triage Priority6162| Priority | Indicators |63|----------|------------|64| High | Multiple users reporting same issue, "everything broken", data loss |65| Medium | Single user with reproducible issue, feature not working |66| Low | Questions, minor UI glitches, feature requests |6768## Integration with Hosted Studio Debug6970If a user reports an issue that might be related to the hosted environment:71721. Note the approximate time of the user's report732. Use `hosted-studio-debug` skill to check logs around that time743. Look for correlating errors in consensus-worker or jsonrpc logs7576```bash77# Example: Check for errors around the time of a user report78argocd app logs studio-prd-workload --name studio-consensus-worker --tail 500 2>&1 | grep -iE "(error|exception|timeout)"79```8081## Response Template8283When summarizing community feedback:8485```86## Community Feedback Summary8788**Period**: [time range of messages reviewed]89**Total Messages**: [count]90**Issues Identified**: [count]9192### High Priority93- [Issue description] - Reported by [count] users9495### Medium Priority96- [Issue description]9798### Low Priority / Questions99- [Description]100101### No Issues102[If no problems found, note this]103```
genlayerlabs