idea-capture
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.zipInstalls 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.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
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
- Read
IDEAS.mdfirst so existing ideas are preserved. - Derive a short, human-readable
##heading from the idea text. - Use the current date in
YYYY-MM-DDformat. - Use the current user as the author when available; otherwise use
Unknown. - Set
ImplementedtoNofor new ideas. - Insert the new idea immediately after the
# Ideasintroduction, before all existing active ideas and the# Archivesection. - 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:
- Find the matching active
##idea section. - Change
**Implemented:** Noto**Implemented:** Yesin the idea's compact metadata line. - If the current date differs from the idea's
**Date:**, add· **Implemented date:** YYYY-MM-DDto the same metadata line. - Move the complete idea section to the end of a top-level
# Archivesection. Create that section if it does not exist. - Preserve the original date, author, title, and idea text.
- 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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| idea-capture (this skill) | 0 | 18d | No flags | Beginner |
| notion-meeting-intelligence | 6 | 5mo | No flags | Intermediate |
| resume-handoff | 3 | 6mo | No flags | Intermediate |
| meeting-briefing | 2 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by michalmar
View all by michalmar →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.
resume-handoff
parcadei
Resume work from handoff document with context analysis and validation
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.
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.
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.
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.