save-research

Summarize conversation research findings into structured markdown documents.

284|10|Updated Dec 6, 2015
One-click install
npx skills add https://github.com/meain/dotfiles --skill save-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-research
Source: https://github.com/meain/dotfiles/tree/main/agents/.agents/skills/save-research
Command: npx skills add https://github.com/meain/dotfiles --skill save-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you systematically capture, organize, and save valuable research findings from conversations into structured markdown documents, preventing knowledge loss and building a personal knowledge base.

Core Features & Use Cases

  • Comprehensive Data Gathering: Reviews entire conversation history to identify insights, code, links, and takeaways.
  • Structured Document Creation: Organizes findings into logical sections (Summary, Findings, Key Takeaways, Code Examples, References, Open Questions) using a predefined markdown template.
  • Flexible Output: Saves research to project-specific directories (.mdocs/) or a general research folder (/Users/meain/dev/docs/research/), prompting the user for clarification when needed.
  • Filename Management: Generates descriptive kebab-case filenames and handles potential file conflicts by asking the user.
  • Use Case: After a long discussion about optimizing a specific algorithm, use this skill to automatically generate a well-formatted markdown document detailing the optimization techniques, code snippets, and performance improvements discussed, saving it to your project's documentation folder.

Quick Start

Use the save research skill to document the findings from our conversation about Go generics.

Frequently Asked Questions about save-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save research findings from a conversation into a structured markdown document?

To save research findings into a structured markdown document, this Skill reviews your conversation history, extracts key insights and code examples, and automatically organizes them into logical sections like Summary, Findings, and References.

What is the best way to document code examples and takeaways from a long discussion?

Documenting code examples and takeaways from a long discussion is handled by summarizing the conversation into a predefined markdown template, ensuring all links, snippets, and open questions are captured accurately without manual formatting.

Can I save research notes to a project-specific directory or do I need a general knowledge base folder?

You can save research notes to either a project-specific directory like `.mdocs/` or a general knowledge base folder, and the Skill will prompt you to clarify the destination if the location is ambiguous.

How does automatic filename generation handle file conflicts when saving research notes?

Automatic filename generation handles file conflicts by creating descriptive kebab-case filenames and prompting the user for a decision if a generated filename already exists in the target directory.

Does the research summarization process capture open questions and references from the entire chat?

Yes, the research summarization process reviews the entire conversation history to ensure all references, open questions, and key takeaways are comprehensively captured and saved into the final knowledge base document.