record-knowledge

Records tagged Markdown knowledge entries with YAML frontmatter metadata and see-reference links.

3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/LevNas/ccmemo --skill record-knowledge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-knowledge
Source: https://github.com/LevNas/ccmemo/tree/main/skills/record-knowledge
Command: npx skills add https://github.com/LevNas/ccmemo --skill record-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill addresses the loss of valuable project-specific knowledge that occurs between coding sessions, ensuring that insights, pitfalls, and decisions are not forgotten and can be easily retrieved.

Core Features & Use Cases

  • Knowledge Persistence: Saves important discoveries, quirks, and lessons learned as tagged Markdown entries.
  • Contextual Recall: Allows retrieval of relevant knowledge at the start of new sessions or during progress updates.
  • Mistake Tracking: Records Claude Code's errors and provides a mechanism for future prevention.
  • Use Case: After debugging a complex issue, use this skill to record the root cause, the solution, and any related system behaviors, so the same problem doesn't need to be solved from scratch later.

Quick Start

Use the record-knowledge skill to save the details of a recent Docker port conflict.

Frequently Asked Questions about record-knowledge

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

FAQPage Schema
How do I save debugging lessons learned and project pitfalls between coding sessions?

You can save debugging lessons learned by recording tacit knowledge, such as pitfalls and root causes, as tagged Markdown entries within a specified directory to preserve insights between coding sessions.

Can I track Claude Code mistakes for future prevention?

Yes, you can track Claude Code mistakes for future prevention by recording the errors as Markdown entries, ensuring the same debugging problems are not solved from scratch later.

How do I retrieve project context and decisions at the start of a new session?

You retrieve project context and decisions by utilizing tag-based organization and YAML frontmatter to facilitate knowledge retrieval at the start of new sessions and during progress updates.

What is the best way to document code quirks and dependencies as knowledge entries?

The best way to document code quirks and dependencies is creating tagged Markdown entries with YAML frontmatter for metadata, utilizing 'see' references to link inter-entry relationships.

Does this knowledge management approach work without external dependencies?

Yes, this knowledge management approach works without external dependencies, relying solely on Markdown files and YAML frontmatter to store project-specific knowledge within your local directory.