save-idea
/save-idea
Save ideas, observations, content topics, projects, and convictions in ~/path/to/ideas. Use when the user asks to capture an idea or insight. Adds to idea backlogs, not reminders or tasks.
- Author
- davidondrej ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Save ideas, observations, content topics, projects, and convictions in ~/path/to/ideas. Use when the user asks to capture an idea or insight. Adds to idea backlogs, not reminders or tasks.
Original author description
Save ideas, observations, content topics, projects, and convictions in ~/path/to/ideas. Use when the user asks to capture an idea or insight. Adds to idea backlogs, not reminders or tasks.
How it works
- 1. Capture and Route
- 2. Read and Number
- 3. Append with Source
- 4. Commit and Push
- 5. Confirm
- Protected Locations
SKILL.md preview
---
name: save-idea
description: Save ideas, observations, content topics, projects, and convictions in ~/path/to/ideas. Use when the user asks to capture an idea or insight. Adds to idea backlogs, not reminders or tasks.
---
# save-idea
Capture the entry in `~/path/to/ideas`, commit, push, and confirm. All paths below are relative to that repo.
## 1. Capture and Route
Everything after `/save-idea` is the entry. Multiple ideas get one entry each. Preserve the user's wording verbatim, except startup ideas and convictions, which may be tightened without changing the user's meaning or voice.
Use and strip an explicit prefix. Otherwise choose by the definitions below; ask one short question only if ambiguous.
- `video:` → `VIDEO-IDEAS.md`: a concept for a full video.
- `topic:` → `TOPICS.md`: podcast/content topics, guests, or discussion questions.
- `observation:` → `OBSERVATIONS.md`: personal insights, hypotheses, or assumptions to test, without requiring content intent.
- `marketing:` → `MARKETING-IDEAS.md`: getting an existing product in front of people.
- `startup:` → `STARTUP-IDEAS.md`: a business/product idea or technical insight that could become a startup.
- `mini:` → `mini-projects.md`: a small technical or cool project, not a startup candidate.
- `article:` → `ARTICLE-IDEAS.md`: a topic for the user's daily public articles.
- No prefix for convictions: use `CONVICTIONS.md` only for beliefs the user states as certain about AI-era building, startups, the AI industry, or agentic coding.
Tentative beliefs belong in observations. An observation is not a topic merely because it could be discussed on a podcast.
## 2. Read and Number
Read the target file. Use its last entry number + 1; never reuse gaps, renumber, reorder, or edit existing entries.
- Video numbering continues from the old Google Doc; do not restart it.
- Startup numbering follows the last idea in the STARTUP IDEAS list. Ignore the separate discarded-ideas numbering.
- Other files start at 1 and have independent numbering.
If missing, create `TOPICS.md` or `MARKETING-IDEAS.md` with a one-line purpose header; `OBSERVATIONS.md` with `# OBSERVATIONS` and `Insights, hypotheses, and assumptions to test.`; or `mini-projects.md` with `# MINI PROJECTS` and `> Just cool shit we wanna build — small projects we think would be cool.` Then append entry 1.
## 3. Append with Source
Source format: `<repo>, <agent and chat/session>, <YYYY-MM-DD>`.
- Repo: where the skill was invoked, from `git rev-parse --show-toplevel`, or cwd outside a repo. Use a `~/...` path.
- Chat/session: agent name plus title or session ID if available; otherwise just the agent name.
- Date: today. Preserve any extra links or notes the user supplied.
**Videos, topics, observations, marketing, and articles:** append verbatim at the bottom, with real tabs before source and context lines:
```text
N. Idea exactly as the user said it
\tsource: <repo>, <agent and chat/session>, <date>
\tany extra links or notes the user gave
```
**Startups, convictions, and mini projects:** indent all source and context lines with four spaces; use `- source:` and a blank line between entries:
```text
N. Title — one-line explanation.
- source: <repo>, <agent and chat/session>, <date>
```
- Startups: read `startup/AGENTS.md`. Tighten the entry while keeping the user's voice. Insert after the last numbered idea, before the trailing `----` separator and discarded-ideas note. Preserve the root `STARTUP-IDEAS.md` symlink to `startup/STARTUP-IDEAS.md`.
- Convictions: append `N. Punchy conviction — one-line why.`, tightened but faithful to the user's wording.
- Mini projects: append `N. Idea exactly as the user said it`; do not rewrite or add an explanation.
## 4. Commit and Push
**The user has pre-authorized and requires commits and pushes for captures in the eight files listed above.** This is an explicit exception to the global no-push-without-asking rule. It covers only those backlogs, including the startup symlink's target, not other repo changes.
Run Git yourself using `git -C`; do not change cwd or delegate this step:
```bash
git -C ~/path/to/ideas pull --rebase --autostash origin main
# Stage only this capture's files; example:
git -C ~/path/to/ideas add OBSERVATIONS.md
git -C ~/path/to/ideas commit -m "Add observation 1 on local agents"
git -C ~/path/to/ideas push origin main
```
- Stage only the captured idea files; never `git add -A`. For the startup symlink, stage `startup/STARTUP-IDEAS.md`. Keep unrelated staged changes or edits out of the commit.
- Commit message: `Add <entry type> <number> on <short description>`. List numbers for multiple entries.
- If any Git step fails, report the exact error and stop. Never force-push.
## 5. Confirm
Report the exact saved entry text, number, file, and successful push.
## Protected Locations
- Never write or push to the old `~/path/to/old-startup` repo. Startup support material belongs in `~/path/to/ideas/startup/`.
- Never write to `startup/review/DISCARDED.md`; only the user moves ideas there.
Versions
The database has no other skills named save-idea.
Database snapshot: 13.11.2026 · package version 2e01aff9a9a8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100idea-vault
Cross-project idea capture and review. A notebook-with-reminders that logs the user's ideas, plans, and checklists across every project, in one plain-markdown file. Use this skill whenever the conversation contains a new idea, plan, or intention the user might want to save for… - 100idea-inbox
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… - 100ext-bw-content-idea-generator
Generate content ideas rooted in positioning. Use when someone needs "content ideas," "what should I post," "blog topics," "LinkedIn ideas," or is stuck on what to create. - 95jidou
记兜(jidou)是聊天中的个人收集箱。用户说“记一下”“帮我记住”“这个留着”、 要补充旧想法、查找过去的记录、整理碎片、管理待办和提醒,或明确要求定时执行时使用。 Capture, recall and organize personal notes, ideas, tasks and reminders. Use for "make a note", "remember this", "save this", "add a task", "remind me", or requests to find old notes, organize… - 100idea-ingest
Ingest links, articles, tweets, and ideas into the brain. Fetch content, save to brain with analysis, credit the author (people page only when they pass the notability gate), and cross-link. Use when the user shares a link or says "read this", "save this", "think about this". - 100idea-sparkbox
Use when the user asks to park ideas or inspiration for later. Not for code, backlog, or divergence-class cards, or remote, credential, publish, deploy, or irreversible changes.