SkillsAdd

smithery.ai

discord-community-feedback

Monitor Discord community channel for user-reported bugs and issues

First seen Mar 25, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Similar popular skills

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

huggingface-community-evals Similar name
huggingface/skills

Run evaluations for Hugging Face Hub models using inspect-ai and lighteval on local hardware.

1.5K installs
community-marketing Similar name
coreyhaines31/marketingskills

Build and leverage online communities to drive product growth and brand loyalty. Use when the u…

69K installs
community-publish Similar name
starchild-ai-agent/official-skills

Publish previews to a public URL, open-source projects to community GitHub, and list services (…

4K installs
find-community Similar name
slavingia/skills

Help identify and evaluate communities to build a minimalist business around. Use when someone …

2.3K installs
community-building Similar name
refoundai/lenny-skills

Help users build and grow product communities. Use when someone is starting a community, scalin…

1.7K installs
community-forum Similar name
kostja94/marketing-skills

When the user wants to promote via forums, communities, or invite users to join a community. Al…

967 installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

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 3,141 B
  • docs SUMMARY.md 101 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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

  1. Fetch recent messages from the feedback channel (up to 100)
  2. Scan for problem indicators using keywords above
  3. Categorize issues by component (frontend, backend, consensus, etc.)
  4. Cross-reference with logs using the hosted-studio-debug skill if needed
  5. 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:

  1. Note the approximate time of the user's report
  2. Use hosted-studio-debug skill to check logs around that time
  3. 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]