skills.rest
dtannen
dtannenCOMMUNITY
Explore all skills by this author →
GitHub

knowledge-management

Capture debugging solutions and non-obvious insights using upsert_knowledge and get_knowledge functions.

Updated Sep 8, 2025
Search Tags:#best practices#debugging#documentation#knowledge management#lessons learned#gotchas
One-click install
npx skills add https://github.com/dtannen/pm --skill knowledge-management-dtannen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-management
Source: https://github.com/dtannen/pm/tree/main/.claude-plugin/skills/knowledge-management
Command: npx skills add https://github.com/dtannen/pm --skill knowledge-management-dtannen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you capture and organize crucial, non-obvious insights, debugging solutions, and lessons learned that would otherwise be forgotten or require painful re-discovery.

Core Features & Use Cases

  • Capture Trial-and-Error Solutions: Document fixes that took multiple attempts.
  • Record Non-Obvious Gotchas: Save insights about unexpected behaviors or undocumented requirements.
  • Store User Corrections: Note down mistakes to avoid in the future.
  • Use Case: After spending hours debugging a complex API integration issue, you discover a specific header is required that wasn't in the documentation. You use this skill to record the exact header and the problem it solved, preventing future team members from facing the same roadblock.

Quick Start

Use the knowledge-management skill to upsert a new knowledge item about a PostgreSQL FTS GIN index requirement.

Frequently Asked Questions about knowledge-management

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

FAQPage Schema
How do I document debugging solutions and gotchas for non-obvious problems?▼

Capturing debugging solutions involves recording non-obvious gotchas and multi-attempt fixes within a structured knowledge system, ensuring that undocumented requirements and hard-won trial-and-error solutions are stored for future retrieval.

What is the best way to record lessons learned from software engineering trial and error?▼

Recording lessons learned from software engineering trial and error is best handled by storing user corrections and unexpected behaviors within a structured knowledge management system, enabling future retrieval of non-obvious debugging solutions via get functions.

Can I use this knowledge management approach to store undocumented API requirements?▼

Yes, you can use this knowledge management approach to store undocumented API requirements by upserting the specific header details and the exact problem it solved, capturing non-obvious integration issues for future reference.

How do I retrieve previously captured technical insights and user corrections?▼

You retrieve previously captured technical insights and user corrections by utilizing the get_knowledge function, which queries the structured knowledge system to fetch stored gotchas, debugging solutions, and lessons learned.

Does this approach to capturing lessons learned work without external dependencies?▼

Yes, capturing lessons learned works without external dependencies, as the knowledge management system relies solely on its internal structured data management functions to upsert and retrieve non-obvious debugging insights.

Related Skills

Explore More Software Engineering Skills→
realsigridjinrealsigridjin
20

learner

Extract project-specific debugging insights and preserve them as reusable skills.

Community
Intermediate
KaimingWanKaimingWan
103

debug

Reproduce software bugs and analyze root causes with knowledge base integration.

Community
Intermediate
luongnv89luongnv89
40.9k

api-documentation-generator

Generate API documentation from source code into Markdown and OpenAPI-style specs.

Community
Basic
koasis89koasis89

note

Create and manage notes using OMX persistent memory features.

Community
Basic