capture-knowledge

Capture reviewed knowledge entries to a markdown knowledge base.

6|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/damianpapadopoulos/auto-claude-skills --skill capture-knowledge-damianpapadopoulos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-knowledge
Source: https://github.com/damianpapadopoulos/auto-claude-skills/tree/main/skills/capture-knowledge
Command: npx skills add https://github.com/damianpapadopoulos/auto-claude-skills --skill capture-knowledge-damianpapadopoulos

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams document and share durable, team-relevant knowledge, ensuring that critical information is not lost and is easily accessible to all team members.

Core Features & Use Cases

  • Knowledge Capture: Record durable learnings, decisions, conventions, and runbooks.
  • Human-Gated: Ensures that knowledge is reviewed and approved before being committed.
  • Deduplication: Prevents the creation of duplicate knowledge entries.
  • Security: Performs a secret/PII scan before committing knowledge to ensure security.
  • Forgetful Sync: Optionally syncs knowledge with the Forgetful system for additional context.

Quick Start

To capture knowledge, write a fact with a slug, type, title, description, tags, source, and timestamp. Present the draft to the human for approval, then commit it to the .claude/knowledge/ base.

Frequently Asked Questions about capture-knowledge

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

FAQPage Schema
How do I capture team knowledge into a shared knowledge base?

To capture team knowledge, write a markdown entry containing a slug, type, title, description, tags, source, and timestamp. Present the draft to a human for approval, then commit it to the .claude/knowledge/ directory.

Does knowledge capture check for sensitive data or PII before committing?

Yes, knowledge capture performs a secret and PII security scan before committing any entries. This ensures sensitive information is detected and prevented from entering the team knowledge base.

How can I prevent duplicate knowledge entries when documenting team decisions?

Preventing duplicate knowledge entries is handled automatically through a deduplication process during capture. The system checks existing entries before committing to avoid redundant records in the knowledge base.

What is the best way to ensure human review of runbooks and conventions before they are saved?

The best way to ensure human review is using a human-gated knowledge capture process. This approach requires a person to explicitly approve drafted learnings or runbooks before they are committed to the knowledge base.

Can I sync captured team knowledge with the Forgetful system for additional context?

Yes, you can optionally sync captured knowledge with the Forgetful system. This integration enhances context by connecting your committed knowledge base entries with the Forgetful framework.

Are there dependencies required to validate knowledge entries before committing?

Yes, markdown and knowledge validation scripts are required to validate entries before committing. These scripts ensure the structure and content meet the required format for the knowledge base.