agentleFS
jqaisystemsjqaisystems/jqai-ai-skills/skills/idea-inbox/SKILL.md

idea-inbox

Skill3 starsChanged 6 months agoMITView on GitHub

Capture a raw idea as a dated, tagged markdown file in an ideas folder and keep an index up to date. Cleans filler words from the dump while preserving the substance, so capture stays fast and retrieval stays possible. Use when the user says "idea:", "capture this idea", "save this idea", or "add to my ideas".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Look for an IDEAS_INDEX.md anywhere in the project.

    line 12
  2. Distinctive:

    Never save idea files to the project root.

    line 16
  3. Distinctive:

    Add the new idea under the best-fitting category:

    line 52
  4. Distinctive:

    If an idea clearly fits a category that does not exist yet, add the category rather than forcing it into Misc.

    line 58
  5. Distinctive:

    Never edit or delete existing idea files.

    line 67
  6. Distinctive:

    Keep the index sorted newest first within each category.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Idea Inbox

Capture ideas at the speed they arrive and still find them later. One idea per file, dated and tagged, in a dedicated folder with an index. Dump fast, refine later.

Step 0: Locate the ideas folder (once)

  1. Look for an IDEAS_INDEX.md anywhere in the project; its folder is the ideas folder.
  2. Otherwise look for a folder named ideas/, Ideas/, or similar.
  3. Otherwise ask the user where ideas should live, create the folder, and create an IDEAS_INDEX.md in it.

Never save idea files to the project root. A pile of loose dated files in the root is how ideas get deleted in the next cleanup.

Step 1: Capture

  1. Get today's date from the current-date context (format YYYY-MM-DD).
  2. Distill a 3 to 5 word kebab-case slug from the idea, e.g. etsy-pinterest-autonomous-pins.
  3. Clean up the raw input: remove filler words and false starts, keep every substantive detail. Tighten, do not summarise. If the user wrote three rough sentences, the file should contain three clean sentences, not one.
  4. Pick 1 to 3 tags from the index categories (see Step 2), plus idea.

Create <ideas-folder>/<date>-<slug>.md:

---
tags: [idea, <category-tag>]
date: <date>
---

# <Idea title in plain words>

<cleaned idea text>

Step 2: Update the index

IDEAS_INDEX.md keeps one line per idea under a category heading. Default categories (create on first use, let the user rename them):

# Ideas Index

## Business
## Automation & Tools
## Design & Creative
## Client Work
## Misc

Add the new idea under the best-fitting category:

- [<Idea title>](<date>-<slug>.md) <date>: one-line hook

If an idea clearly fits a category that does not exist yet, add the category rather than forcing it into Misc.

Step 3: Confirm

Report the file path, the category it was filed under, and the one-line hook used in the index.

Rules

  • One idea per file. If the user dumps three ideas in one message, create three files and say so.
  • Never edit or delete existing idea files. The inbox only grows; pruning is the user's call.
  • Preserve the user's meaning exactly. Cleaning filler is fine, replacing their thinking is not.
  • Keep the index sorted newest first within each category.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.