learnings

Capture solved problems as categorized Markdown documentation with YAML frontmatter.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/hackefeller/ghostwire --skill learnings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learnings
Source: https://github.com/hackefeller/ghostwire/tree/main/.github/skills/learnings
Command: npx skills add https://github.com/hackefeller/ghostwire --skill learnings

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of documenting solved technical problems, transforming conversational solutions into searchable, categorized knowledge base entries.

Core Features & Use Cases

  • Automatic Documentation: Captures problem context, root cause, and solutions from conversations.
  • Structured Knowledge Base: Organizes documented solutions into categorized Markdown files with YAML frontmatter for fast lookup.
  • Use Case: After debugging a complex performance issue in the Brief System, this Skill automatically creates a detailed entry in docs/solutions/performance-issues/ that can be quickly found by other developers facing similar problems.

Quick Start

Manually invoke this skill using the /doc-fix command after a problem has been resolved.

Frequently Asked Questions about learnings

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

FAQPage Schema
How do I document solved debugging problems for a technical knowledge base?

To document solved debugging problems for a technical knowledge base, this Skill extracts context from conversation history and structures confirmed solutions into categorized Markdown files with YAML frontmatter for fast lookup.

What is the best way to build institutional memory for software engineering teams?

Building institutional memory for software engineering teams is achieved by automatically documenting confirmed solutions and categorizing them by problem type within a searchable knowledge base, preventing knowledge loss.

How do I automatically extract problem context from conversation history into documentation?

To automatically extract problem context from conversation history into documentation, you invoke the skill after a problem is resolved, triggering context extraction and strict YAML schema validation to generate structured entries.

Does this knowledge base documentation tool require a specific YAML schema?

Yes, this knowledge base documentation tool requires strict YAML schema validation to ensure captured solutions are properly formatted with frontmatter, enabling reliable categorization and fast lookup of institutional memory.

Can I use Markdown files with YAML frontmatter to categorize technical writing?

Yes, you can use Markdown files with YAML frontmatter to categorize technical writing, as this Skill organizes documented solutions into categorized Markdown files structured for fast lookup and knowledge retrieval.