knowledge-capture

Capture durable project knowledge as categorized Markdown notes with index maintenance.

Updated May 28, 2026
One-click install
npx skills add https://github.com/haryelramalho/skills --skill knowledge-capture-haryelramalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-capture
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/knowledge-capture
Command: npx skills add https://github.com/haryelramalho/skills --skill knowledge-capture-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill turns important project knowledge into durable, human-readable documentation so teams do not lose decisions, concepts, gotchas, or research after a conversation ends.

Core Features & Use Cases

  • It classifies capture requests into a single canonical note type, including concept, decision, gotcha, research, or convention.
  • It writes topic-focused Markdown under the right docs folder and keeps entries easy for future readers to find.
  • It maintains a compact docs index so new notes stay discoverable.
  • Use it to record why a design choice was made, document a recurring failure mode, preserve investigation results, or codify a team rule.

Quick Start

Ask the assistant to save your durable project knowledge as the appropriate docs note and update the project index.

Frequently Asked Questions about knowledge-capture

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

FAQPage Schema
How do I capture project decisions and gotchas in markdown docs so they survive beyond a single chat?

You can capture durable project knowledge by routing details into a canonical note type like decision, concept, or gotcha, then writing topic-focused Markdown under the correct docs folder to ensure long-term discoverability.

What is the best way to maintain a documentation index when recording new project conventions?

Maintaining a documentation index involves updating a compact docs directory whenever new Markdown notes are added, ensuring that team rules and conventions remain easy for future readers to find.

How do I organize research findings and design choices into a readable project memory format?

You organize research findings by classifying the capture request into a single canonical note type, then writing the details into human-readable Markdown notes that codify why specific design choices were made.

Does this knowledge-capture approach work without external dependencies or complex environment setup?

This knowledge-capture approach works without external dependencies, relying entirely on standard Markdown files and your existing project documentation rules to validate and store notes.

When should I not use a dedicated documentation note for preserving investigation results?

You should not use a dedicated documentation note for transient information that only applies to a single chat or session, as this process is specifically designed for durable knowledge that must survive long-term.

Can I use this to document recurring failure modes and team rules in my project docs?

You can use this to document recurring failure modes by creating gotcha notes, and to codify team rules by generating convention notes, both of which are validated against your project documentation rules.