knowledge-capture

Capture conversation insights into Basic Memory knowledge graph notes.

1|Updated Dec 25, 2017
One-click install
npx skills add https://github.com/mattniedelman/dotfiles --skill knowledge-capture-mattniedelman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-capture
Source: https://github.com/mattniedelman/dotfiles/tree/main/dot_augment/skills/knowledge-capture
Command: npx skills add https://github.com/mattniedelman/dotfiles --skill knowledge-capture-mattniedelman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you convert valuable conversations and decisions into structured notes that live in Basic Memory's knowledge graph, ensuring insights and rationale are preserved for future reference.

Core Features & Use Cases

  • Structured capture: record decisions, insights, patterns, trade-offs, and learnings with explicit observations and relations.
  • Knowledge graph integration: automatically link notes to related concepts and sources within Basic Memory.
  • Template-driven notes: create notes that follow a consistent schema (title, type, tags, context, content, observations, relations) for reliable discovery.

Quick Start

Capture the latest discussion's key decisions and insights into Basic Memory as a note titled 'Discussion Summary'.

Frequently Asked Questions about knowledge-capture

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

FAQPage Schema
How do I capture decisions and technical insights from conversations into structured notes?

You capture decisions and technical insights by generating structured notes with explicit observations and relations that adhere to a consistent schema, including title, type, tags, context, and content, preserving rationale for future reference.

What is the best way to record debugging learnings and architecture choices in a knowledge graph?

Recording debugging learnings and architecture choices in a knowledge graph involves creating template-driven notes that link related concepts and sources through structured observations and relations for reliable discovery.

Can I document design trade-offs without needing external software or dependencies?

Documenting design trade-offs requires no external software or dependencies, using a self-contained note schema to capture context, content, and structured relations within your existing knowledge graph.

Does capturing knowledge into a knowledge graph support tagging and linking related concepts?

Capturing knowledge into a knowledge graph supports tagging and linking by applying a structured schema that automatically connects notes to related concepts and sources through defined observations and relations.

What schema structure do I need to follow when capturing observations and relations?

The schema structure requires capturing a title, type, tags, context, content, observations, and relations, ensuring notes follow a consistent template for reliable discovery within the knowledge graph.