knowledge

Store validated discoveries as cited facts in a persistent knowledge base.

Updated Mar 12, 2019
One-click install
npx skills add https://github.com/gustavofsantos/dot-files --skill knowledge-gustavofsantos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge
Source: https://github.com/gustavofsantos/dot-files/tree/main/skills/knowledge
Command: npx skills add https://github.com/gustavofsantos/dot-files --skill knowledge-gustavofsantos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Keeps validated discoveries and narratives available beyond a single session, enabling long-term memory, consistent indexing, and rapid knowledge reuse across projects.

Core Features & Use Cases

  • Central, persistent knowledge base that stores facts and spike narratives so they survive issue closure and session resets.
  • Query-before-work: retrieve prior knowledge at session start to inform decisions and reduce duplication.
  • Promote dead-reckoning outputs to permanent, cited facts with evidence, ensuring traceability and reuse.
  • qmd integration: maintain the qmd index to provide cross-project knowledge accessibility.

Quick Start

Tell me to save this discovery as a fact so it becomes part of the knowledge library.

Frequently Asked Questions about knowledge

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

FAQPage Schema
How do I preserve validated discoveries as durable facts across sessions?

To preserve validated discoveries as durable facts across sessions, you process and store them in a centralized knowledge base with time-stamped, cited evidence. This ensures your findings survive session resets and remain accessible for rapid reuse.

What is the best way to query prior knowledge before starting new work?

The best way to query prior knowledge before starting work is to retrieve facts and spike narratives from a persistent knowledge base at session start. This query-before-work approach informs decisions and reduces duplicated effort across projects.

How does promoting dead-reckoning outputs to permanent facts with evidence work?

Promoting dead-reckoning outputs to permanent facts with evidence works by validating your temporary findings and storing them with time-stamped citations. This traceability ensures provisional discoveries become durable, reusable knowledge entries in the index.

Can I maintain a cross-project knowledge index for rapid retrieval?

Yes, you can maintain a cross-project knowledge index for rapid retrieval by integrating qmd indexing. This keeps your centralized knowledge base accessible across different projects, ensuring consistent indexing and rapid knowledge reuse.

Do I need a centralized knowledge base to store spike narratives and facts?

Yes, you need a centralized knowledge base to store spike narratives and facts so they survive issue closure and session resets. This persistent storage mechanism enables long-term memory and consistent indexing for future queries.

What are the limitations of relying on session memory for software engineering discoveries?

Relying on session memory limits discoveries to a single session, causing knowledge loss after resets or issue closure. Without a persistent knowledge base, you cannot retrieve prior facts or promote dead-reckoning outputs to permanent, cited evidence.