idea-inbox

Capture Discord #idea-inbox messages into a JSON backlog with timestamps and unique IDs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/DisruptionEngineer/build-useful-skills --skill idea-inbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea-inbox
Source: https://github.com/DisruptionEngineer/build-useful-skills/tree/main/idea-inbox
Command: npx skills add https://github.com/DisruptionEngineer/build-useful-skills --skill idea-inbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture raw unstructured ideas from Discord's #idea-inbox channel into a local JSON backlog with zero friction. Use when receiving new project ideas from authorized users, logging brainstorm output with timestamps and unique IDs, checking for duplicate submissions, or bootstrapping the idea-to-skill pipeline. Communicates downstream with idea-scorer via idea-backlog.json.

Core Features & Use Cases

  • Listen on the Discord #idea-inbox channel for raw, unstructured idea messages from authorized users. Tag each with a raw status, assign a unique ID, store it in ~/.agents/data/idea-backlog.json, and confirm receipt in the channel. This is the zero-friction entry point for the entire skill pipeline.
  • Backlog management: generate unique IDs, timestamp ideas, and maintain a structured backlog with statuses like raw, scored, refining, ready, built.
  • Duplicate detection and downstream handoff: compare new ideas to existing backlog entries, flag potential duplicates, and notify downstream scorer skills.

Quick Start

Post a new idea in the Discord #idea-inbox channel to have it logged with a timestamp and a unique ID.

Frequently Asked Questions about idea-inbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture unstructured Discord messages into a structured JSON backlog?

To capture unstructured Discord messages into a JSON backlog, listen on an authorized channel for raw ideas, tag them with a raw status, assign a unique ID, and store them locally in idea-backlog.json. This provides zero-friction logging for project pipelines.

Can I check for duplicate ideas before adding them to my project backlog?

You can check for duplicate ideas by comparing new message submissions against existing entries in your JSON backlog. The system flags potential duplicates during capture, preventing redundant brainstorm outputs from polluting your downstream idea pipeline.

How does idea deduplication work when capturing brainstorm output from Discord?

Idea deduplication works by comparing incoming unstructured Discord messages against the existing local JSON backlog. When a new idea is received, the system checks for similarities against stored entries and flags potential duplicates before confirming receipt.

Do I need a specific Discord channel setup to log new project ideas automatically?

You need a designated Discord channel, such as #idea-inbox, to log new project ideas automatically. Authorized users post raw unstructured messages in this channel, which are then timestamped, assigned unique IDs, and stored locally.

What is the best way to bootstrap an idea-to-skill automation pipeline?

The best way to bootstrap an idea-to-skill pipeline is to capture raw Discord messages into a structured local JSON file. This backlog acts as the zero-friction entry point, communicating downstream with scoring and refining processes to develop skills.

How do I manage backlog statuses when logging brainstorm output from Discord?

To manage backlog statuses when logging brainstorm output, the system assigns a raw status to new ideas upon capture. It maintains a structured JSON backlog tracking progression through scored, refining, ready, and built statuses for pipeline automation.