agentleFS
Sign inStart free
vavalleevavallee/bindery/.claude/skills/discord-reports/SKILL.md

discord-reports

Skill518 starsChanged 57 days agoMITView on GitHub

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

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    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).

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free