Records user ideas into a centralized IDEAS.md file with automated metadata and status tracking.

Install

mkdir -p .claude/skills/idea-capture-michalmar && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18443" && unzip -o skill.zip -d .claude/skills/idea-capture-michalmar && rm skill.zip

Installs to .claude/skills/idea-capture-michalmar

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Capture IDEA messages into the project IDEAS.md file with readable metadata.
76 charsno explicit “when” trigger
Beginner

Key capabilities

  • Capture text after 'IDEA:' marker
  • Store ideas in `IDEAS.md`
  • Format ideas with date, author, and implemented status
  • Create `IDEAS.md` if it does not exist
  • Move implemented ideas to an Archive section
  • Derive short, human-readable headings for ideas

How it works

The skill extracts idea text from user messages, formats it with metadata, and inserts it into the `IDEAS.md` file, managing active and archived sections.

Inputs & outputs

You give it
A user message containing 'IDEA: <idea text>'
You get back
An updated `IDEAS.md` file with the new idea or an updated status for an existing idea

When to use idea-capture

  • Document feature requests during development
  • Track workshop brainstorming ideas
  • Archive implemented project ideas
  • Maintain a changelog of project suggestions

About this skill

Idea Capture Skill

Purpose

Use this skill when the user writes IDEA: ... and wants the idea saved in this repository.

The goal is to keep a simple idea log in the root IDEAS.md file. Active ideas and implemented ideas are kept in distinct sections so the list remains easy to scan.

Trigger

Use this skill when a user message starts with or clearly contains:

IDEA: <idea text>

Capture the text after the first IDEA: marker as the idea body. Preserve the user's meaning and wording; lightly clean only obvious extra whitespace.

File format

Store ideas in the repository root file:

IDEAS.md

If the file does not exist, create it with this heading:

# Ideas

Use this file to collect workshop and project ideas. Active ideas stay here; implemented ideas are moved to the Archive section. New ideas are added first.

Each idea must be a separate ## section. Put its description first and its compact metadata on one line after the description:

## Short idea title

Idea text goes here.

<sub>**Date:** YYYY-MM-DD · **Author:** @username · **Implemented:** No</sub>

Capture procedure

  1. Read IDEAS.md first so existing ideas are preserved.
  2. Derive a short, human-readable ## heading from the idea text.
  3. Use the current date in YYYY-MM-DD format.
  4. Use the current user as the author when available; otherwise use Unknown.
  5. Set Implemented to No for new ideas.
  6. Insert the new idea immediately after the # Ideas introduction, before all existing active ideas and the # Archive section.
  7. Keep the idea text concise and readable. Use plain paragraphs unless the user provides a list.

Marking ideas implemented

When the user asks to mark an idea as done or implemented:

  1. Find the matching active ## idea section.
  2. Change **Implemented:** No to **Implemented:** Yes in the idea's compact metadata line.
  3. If the current date differs from the idea's **Date:**, add · **Implemented date:** YYYY-MM-DD to the same metadata line.
  4. Move the complete idea section to the end of a top-level # Archive section. Create that section if it does not exist.
  5. Preserve the original date, author, title, and idea text.
  6. If multiple ideas could match, ask which one to update.

Example prompt

IDEA: Add a short facilitator checklist for choosing the right Copilot mode during demos.

When not to use it

  • When the user message does not contain 'IDEA:'
  • When the user does not want the idea saved in the repository

Limitations

  • The skill only captures text after an 'IDEA:' marker
  • The skill stores ideas in a single `IDEAS.md` file
  • The skill requires a short, human-readable heading for each idea

How it compares

This automates the structured logging of ideas with consistent formatting and lifecycle management, unlike manually adding notes to a file.

Compared to similar skills

idea-capture side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
idea-capture (this skill)018dNo flagsBeginner
notion-meeting-intelligence65moNo flagsIntermediate
resume-handoff36moNo flagsIntermediate
meeting-briefing25moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

notion-meeting-intelligence

openai

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

656

resume-handoff

parcadei

Resume work from handoff document with context analysis and validation

333

meeting-briefing

anthropics

Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.

213

personal-assistant

ailabs-393

This skill should be used whenever users request personal assistance tasks such as schedule management, task tracking, reminder setting, habit monitoring, productivity advice, time management, or any query requiring personalized responses based on user preferences and context. On first use, collects comprehensive user information including schedule, working habits, preferences, goals, and routines. Maintains an intelligent database that automatically organizes and prioritizes information, keeping relevant data and discarding outdated context.

36

digital-brain

muratcankoylan

This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.

15

meeting-sync

amanaiproduct

Sync new Granola meetings to local Knowledge folder. Use during morning planning, when user asks "what should I do today", or asks to review/sync meetings.

13

Search skills

Search the agent skills registry