discord-reports

SkillCommunication

Pull user bug reports from the bindery Discord and convert them to GitHub issues

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the discord-reports skill

What this skill tells your AI

The instructions your AI receives, as published by vavallee/bindery in .claude/skills/discord-reports/SKILL.md and read by ahel’s review.

Collect and process Discord bug reports. Access details (bot token location, guild/channel IDs) are in CLAUDE.local.md — never print the token.

  1. Fetch recent messages from the report channels: GET /channels/{id}/messages?limit=50, header Authorization: Bot <token>, Discord API v10. Use curl — Discord's Cloudflare blocks Python urllib. Default lookback: since the last run noted in memory, else 7 days; $ARGUMENTS overrides.
  2. Filter to actual reports: errors, unexpected behavior, version/setup problems. Skip chatter and feature musings unless substantial.
  3. Dedupe against existing issues (gh issue list --search). If a report matches an open issue, note the +1 instead of filing a duplicate.
  4. For each new report, draft a GitHub issue: title, what the user saw, version if stated, link to the Discord message. Show me all drafts before creating anything.
  5. After I approve: gh issue create, then draft a short reply for the Discord thread pointing to the issue (tone rules in CLAUDE.local.md). Post replies only after I approve them.
  6. Record the sweep timestamp in memory so the next run picks up where this left off.

Signals

GitHub stars
456
Forks
57
Last commit
Sep 2026

ahel review

  • S4info
    community integration — published by vavallee, not discord

Automated review, not a security audit. Ruleset v1+k2.

Advanced
Catalog kind
skill
Gateway key
discord-reports
Source
github.com/vavallee/bindery