knowledge-management

Materialize knowledge artifacts into structured knowledge graphs with revision logs.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/rd162/skills --skill knowledge-management-rd162
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-management
Source: https://github.com/rd162/skills/tree/main/knowledge-management
Command: npx skills add https://github.com/rd162/skills --skill knowledge-management-rd162

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Knowledge Management (KM) skill helps you create, revise, and materialize structured knowledge artifacts (Fact, Concept, Procedure, Narrative, Ontology) with revision tracking, observation tagging, provenance, and knowledge-graph relations, enabling consistent capture and evolution of knowledge across projects.

Core Features & Use Cases

  • Create, revise, and materialize artifacts using standardized templates to ensure consistency and traceability.
  • Track revisions, observations, and verification trails to support provenance and quality.
  • Build and manage knowledge graphs with typed relations, future-forward gaps, and scalable organization across domains.
  • Adapt to various storage backends (Markdown files, Obsidian, or other KM systems) through a unified materialization workflow.

Quick Start

Start by narrating a recent event and then materialize a fact and a procedure to capture the outcomes.

Frequently Asked Questions about knowledge-management

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

FAQPage Schema
How do I turn unstructured context into a structured knowledge graph?

You turn context into a knowledge graph by applying a narrative-first materialization workflow to extract structured knowledge artifacts. This process organizes facts, concepts, and procedures into interconnected nodes with revision logs and cross-artifact relations.

What is the best way to track provenance and revisions for knowledge artifacts?

Tracking provenance for knowledge artifacts requires applying verification paths and observation tagging during materialization. This generates revision logs and verification trails to ensure quality and traceability across your projects.

How do I materialize facts and procedures from a recent event narrative?

You materialize facts and procedures by narrating the event first, then extracting outcomes into standardized templates. This enforces a narrative-first workflow ensuring contextual inputs become structured artifacts with proper provenance.

Does this knowledge management approach work with Obsidian and Markdown files?

Yes, the knowledge management workflow adapts to various storage backends including Obsidian, Markdown files, and other KM systems. It uses a unified materialization process to ensure interoperability across these file-based platforms.

What types of knowledge artifacts can I organize and cross-reference?

You can organize Fact, Concept, Procedure, Narrative, and Ontology artifacts. The system stitches scalable cross-artifact relations between these types, enabling future-forward gap analysis and domain-spanning knowledge graphs.

When should I use a narrative-first materialization workflow for knowledge capture?

Use narrative-first materialization when you need consistent capture and evolution of contextual knowledge with traceable provenance. It ensures structured artifacts are properly verified and cross-referenced before entering your knowledge graph backend.