capture
Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss. Use this skill whenever the user says 'capture this', 'brain dump', 'let me dump some ideas', 'I've got a bunch of thoughts', 'here's everything on my mind', 'idea dump', 'let me get this out of my head', 'I need to organize my thoughts', 'here's what I'm thinking', or any variation where someone is unloading a messy stream of ideas, tasks, thoughts, and plans wanting them turned into something coherent. Also trigger when the user pastes or dictates a long, unstructured block of mixed ideas — even without the exact phrase — the intent is the same. Fast-to-action by design: no upfront intake. Output is four sections (Projects/Ideas, Tasks, Connections, How I Can Help) ending with a directive question. Asks at most one mid-organization clarifying question when a single item is genuinely ambiguous between task and project.
- License 许可
- MIT
- 最近更新
- 2026-06-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- capture
- license
- MIT
- metadata
- { "version": "1.0.0", "source_spec": "megaprompts/05-capture-megaprompt.md", "build_pattern": "Path B (direct conversion)" }
- description
- Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss. Use this skill whenever the user says 'capture this', 'brain dump', 'let me dump some ideas', 'I've got a bunch of thoughts', 'here's everything on my mind', 'idea dump', 'let me get this out of my head', 'I need to organize my thoughts', 'here's what I'm thinking', or any variation where someone is unloading a messy stream of ideas, tasks, thoughts, and plans wanting them turned into something coherent. Also trigger when the user pastes or dictates a long, unstructured block of mixed ideas — even without the exact phrase — the intent is the same. Fast-to-action by design: no upfront intake. Output is four sections (Projects/Ideas, Tasks, Connections, How I Can Help) ending with a directive question. Asks at most one mid-organization clarifying question when a single item is genuinely ambiguous between task and project.
02 资源文件 6
- 参考文档references/complexity_matching.md7.5 KB
- 参考文档references/voice_preservation.md4.4 KB
- 参考文档references/workspace_detection.md4.8 KB
- 脚本scripts/complexity_estimator.py7.0 KB
- 脚本scripts/dump_classifier.py5.6 KB
- 脚本scripts/workspace_inventory.py7.6 KB
03 SKILL.md 正文
Capture — Brain-Dump Organizer
A fast-to-action skill for transforming unstructured streams of mixed thoughts, tasks, and ideas into a clean four-section actionable system with zero information loss.
Invocation Triggers
Explicit phrases (any of):
- "brain dump"
- "capture this"
- "let me dump some ideas"
- "I've got a bunch of thoughts"
- "here's everything on my mind"
- "idea dump"
- "let me just get this out of my head"
- "I need to organize my thoughts"
- "here's what I'm thinking"
Implicit signals (no phrase, but the intent is unmistakable):
- User pastes or dictates a long unstructured block of mixed ideas, tasks, plans
- Multiple unrelated thoughts in one message without organizing framing
- A wall of bullet-y text covering 3+ unrelated topics
When you detect an implicit trigger, run the skill. Do NOT ask "do you want me to organize this?" first — the dump itself IS the request.
Operating Principles (All Five Apply Always)
- Capture everything. Zero loss. Trivial items go in; the user prunes later. Never silently drop something because it "seemed unimportant".
- Preserve voice. If the user said "build something crazy with AI", do NOT restate as "Explore innovative AI-driven solutions." Keep the energy and the casual register. See
references/voice_preservation.mdfor concrete anti-patterns. - Match output complexity to input. A 5-task dump does NOT get forced into 4 elaborate sections. See
references/complexity_matching.mdand the Compressed Output Pattern below. - Be honest about ambiguity. If you're unsure what something means, flag it. Don't guess silently.
- No action without approval. The ONLY immediate action is the organization itself. Every offer in Section 4 waits for the user's explicit pick.
Grill-Me Mid-Organization Clarifier
Capture is fast-to-action by design. No upfront intake. The dump is enough — start organizing immediately.
The grill-me discipline applies as a single mid-organization clarifying question, asked only when one item in the dump is genuinely ambiguous between task and project, AND the misclassification would meaningfully change the output:
Quick clarification — one item in your dump could go either way. Is [X] a one-shot task or a multi-step project?
Why I'm asking: If I guess wrong on a borderline item I either bury a project as a task or inflate a task into a project that doesn't need the structure. One question per dump prevents that.
Stop condition: Max 1 clarifying question per dump. After the answer (or if no clarification was needed), deliver the four (or compressed) sections.
If the dump is unambiguous, skip the clarifier entirely.
Anti-pattern (do not do this): asking 3 clarifying questions up front. That breaks the dump-and-organize flow that makes capture useful.
Section 1: Projects & Ideas
Cluster related items into themed projects when natural clustering exists. This section also holds:
- Standalone creative sparks
- Half-formed concepts
- "What if" thoughts
- Embedded decisions (
Decide: X or Y) and open questions (Q: ...) — kept WITHIN the relevant project, NOT extracted into a separate top-level category
Format per project:
### {Project name in user's voice}
- {component / sub-idea}
- {component}
- Q: {open question this project needs answered}
- Decide: {decision this project requires}
Use the user's words for the project name. If the user wrote "ai dating app for ferrets", do NOT rename it to "AI-Powered Pet Companion Platform".
Section 2: Tasks
Flat, scannable, action-oriented. Includes:
- Explicit todos
- Decisions framed as
Decide: ... - Open questions framed as
Resolve: ...
If a task belongs to a project from Section 1, append [Project: X] to link it — but don't repeat the project's context.
Format:
- {task in imperative voice} [Project: X if related]
- Decide: {decision} [Project: X if related]
- Resolve: {open question}
- ...
Section 3: Connections
This is where the skill earns its keep — and where fabrication is forbidden.
Workflow:
- Inventory the workspace — Glob for filename patterns matching dump keywords, Grep for content matches, read the top-level directory structure. Use
scripts/workspace_inventory.pyto do this deterministically. - Match dump items to existing content — files / folders relating to dumped items, prior thinking in documents, in-progress projects with overlap.
- Surface dependencies within the dump — items that affect each other, themes, ordering implications.
- Be honest about inaccessibility — if you can't inspect the workspace (no filesystem available, MCP not connected), say so explicitly. Do NOT make up plausible-sounding connections.
Hard rule: NEVER fabricate connections. Only surface ones actually found by Glob/Grep/Read. If no real connections exist:
Connections: No connections found — workspace inventory clean.
If the workspace is inaccessible:
Connections: No workspace accessible from here. If you're running this from Claude Code or have a project with files attached, I can fill this in. Want to share where this work lives?
See references/workspace_detection.md for the per-context detection-tactic catalog.
Section 4: How I Can Help
Concrete offers, not abstract possibilities. Every offer specifies what would be produced AND where it would go.
| ✅ Right pattern | ❌ Anti-pattern |
|---|---|
"I can research Consensus MCP integration patterns and give you 3 options. Output: docs/consensus-options.md." |
"You might want to look into integration approaches." |
"I can draft the Q3 launch plan as a 1-pager. Output: chat reply, then docs/q3-launch.md if you want it filed." |
"Maybe think about Q3 planning." |
"I can scaffold the new auth module with the existing pattern from src/users/. Output: 4 files in src/auth/." |
"We could explore auth options." |
End with the directive question:
Which of these should I tackle?
Compressed Output Pattern
When the dump has 5 or fewer items and items are unrelated (no natural clustering), drop the 4-section format and use compressed:
## What I heard
- {item}
- {item}
- {item}
- ...
## How I can help
- {concrete offer with what + where}
- {concrete offer with what + where}
Which should I tackle?
The trigger is the complexity_estimator.py recommendation OR your judgment when no clusters exist. See references/complexity_matching.md for worked examples of when each format applies.
Workspace Detection Strategy
| Context | Detection method |
|---|---|
| Claude Code CLI | Glob for files matching dump keywords; Grep for content matches; read top-level structure. Use scripts/workspace_inventory.py. |
| Claude.ai with project | Check project knowledge files for thematic overlap. List file titles; surface matches by keyword. |
| Connected tools (Notion, Drive, etc.) | Search via MCP if available. |
| No accessible workspace | State the limitation explicitly; ask user about their setup; do NOT fabricate. |
Approval Gate
After the four (or compressed) sections are delivered:
- Wait for the user's explicit pick before doing anything else.
- If the user says "go" without picking a specific offer: honor it, but explicitly note any items you weren't 100% sure about so they can correct.
- The organization itself is the only auto-action. Every Section 4 offer requires green light.
Error Handling
| Situation | Behavior |
|---|---|
| Workspace inaccessible | State this; skip Section 3 or surface "no workspace accessible" + ask about setup |
| Dump is very short (3-5 items) | Use compressed output; don't force 4 sections |
| Items are highly ambiguous | Flag in output, ask up to 1 clarifier (or skip clarifier and surface ambiguity in delivery) |
| Dump contains sensitive info | Acknowledge but don't echo verbatim if user asks for organization without quoting |
| Conflicting items in the dump | Surface the conflict in Section 1 or 3 explicitly (Conflict: X says A, Y says B) |
| User says "go" before approval | Honor it, but explicitly note items you weren't sure about |
Tooling
| Script | Role |
|---|---|
scripts/workspace_inventory.py |
Glob+Grep helper for Section 3. python workspace_inventory.py --root . --keywords "k1,k2" returns matches by keyword + folder structure. |
scripts/dump_classifier.py |
Regex-classifies each dump line into task / decision / question / idea / project-component. Heuristic — override with judgment. |
scripts/complexity_estimator.py |
Counts items, detects clustering signal, recommends format=full or format=compressed. |
References
references/workspace_detection.md— context-specific detection tactics (CLI / web / MCP / inaccessible)references/voice_preservation.md— corporate-speak anti-patterns with concrete examplesreferences/complexity_matching.md— compressed vs full output, worked examples
Anti-Patterns To Reject
- Fabricating workspace connections that weren't actually Glob/Grep-verified
- Dropping items deemed "trivial" — capture everything, let the user prune
- Corporate-ifying the user's casual language
- Forcing 4-section structure when input is small (5 simple tasks doesn't need it)
- Acting on Section-4 offers immediately without approval
- Splitting decisions/questions into a separate top-level category instead of embedding them in the relevant project
- Vague Section-4 offers ("you might want to consider…")
- Asking 3+ clarifying questions up front (breaks fast-to-action)
Version: 1.0.0
Source spec: megaprompts/05-capture-megaprompt.md
Build pattern: Path B (direct conversion). Re-grill with /cs:grill-with-docs if drift between spec and implementation surfaces.
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.