agentleFS
Sign inStart free
mattpollakmattpollak/relay/skills/idea/SKILL.md

idea

Skill2 starsChanged 8 months agoMITView on GitHub

Captures an idea for future work, or promotes one to a workstream. Displayed by /relay:list. Trigger phrases: "add idea", "jot down", "remember this idea", "idea promote".

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    If $ARGUMENTS starts with promote, extract the idea ID (the number after "promote").

    line 17
  2. Very specific:

    Find the idea: Call manage_idea(action="list").

    line 19
  3. Very specific:

    Remove the idea: Call manage_idea(action="remove", idea_id=<id>).

    line 21
  4. Very specific:

    If $ARGUMENTS does not start with promote, treat it as idea text.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “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

Capture or Promote Ideas

Ideas are things you want to track but haven't started working on yet. They are displayed by /relay:list. When you're ready to work on one, promote it to a full workstream.

Argument: $ARGUMENTS is either idea text to capture, or promote <id> to turn an idea into a workstream.

Subcommand: promote

If $ARGUMENTS starts with promote, extract the idea ID (the number after "promote").

  1. Find the idea. Call manage_idea(action="list"). Find the idea with the matching ID. If not found, list all ideas with their IDs and stop.
  2. Remove the idea. Call manage_idea(action="remove", idea_id=<id>).
  3. Create workstream. Tell the user the idea has been removed, then invoke /relay:new using the idea text as context. Ask the user for a workstream name and description (suggest based on the idea text).

Subcommand: add (default)

If $ARGUMENTS does not start with promote, treat it as idea text.

  1. Get the idea. The idea text is $ARGUMENTS. If empty, ask the user what they want to capture and stop.
  2. Add. Call manage_idea(action="add", text="<idea text>").
  3. Confirm. Tell the user the idea was captured with its ID. Mention /relay:list to see all ideas and /relay:idea promote <id> when ready.

Download now (ZIP)

  • Other versions24 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 24

    1. me2resh/apexyard★ 532same name
    2. serejaris/personal-corp-os★ 236same name
    3. serejaris/ris-claude-code★ 230same name
    4. tance-mang/chinese-webnovel-skills★ 65same name
    5. baekenough/oh-my-customcode★ 42same name
    6. iamneilroberts/claude-skills★ 26same name
    7. tercel/spec-forge★ 8same name
    8. froster02/mini-Brain_skills★ 4same name
    9. merchsage/workflow-skills★ 4same name
    10. ChrisAdkin8/claude-skills★ 2same name

    14 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use decompose, inbox and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • matt-k-wongSkill

      decompose

      Learn to decompose complex problems before building real agents. Better answers today. Ready for orchestration tomorrow. Breaks messy tasks into clear DAG structures with explicit dependencies, parallel branches, and synthesis logic. Improves Claude outputs by enforcing topological order and catching contradictions. Teaches the mental model for LangGraph, CrewAI, n8n, and Sub-Agents. Type "decompose: [goal]" or "decompose preview: [goal]" to start. Zero experience required.

      Also in 3 projects that use this

    • kv0906Skill

      inbox

      Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

      Also in 3 projects that use this

    • MicrosoftSkill

      scaffold

      Also in 3 projects that use this

    • AWSSkill

      retro

      Conduct a retrospective on a coding session.

      Also in 6 projects that use this

    • Hugging FaceSkill

      implement

      Make tests pass. Invoke after /write-tests produces failing tests.

      Also in 5 projects that use this

    • GoogleSkill

      to-issues

      Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

      Also in 3 projects that use this

  • In this repository3 other files it gives its agents.

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.

Check your setup, free