learn

Capture conversation learnings as structured Markdown documents in docs/.

4|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/vertexcover-io/tarash --skill learn-vertexcover-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/vertexcover-io/tarash/tree/main/.claude/skills/learn
Command: npx skills add https://github.com/vertexcover-io/tarash --skill learn-vertexcover-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture learnings from conversations as a clean, human-readable doc in docs/.

Core Features & Use Cases

  • Provide a centralized, reusable knowledge capture after solving non-trivial problems, discovering patterns, or architectural decisions.
  • Create a structured markdown document in docs/ that preserves context, rationale, and key takeaways for future reference.
  • Enable teammates to quickly locate design decisions and lessons learned from prior conversations.

Quick Start

Document this learning into docs/ using a concise, structured Markdown format.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I capture learnings from conversations into reusable knowledge management docs?

You capture learnings from conversations by generating a clean, structured Markdown document stored in the docs/ directory. This preserves context, rationale, and key takeaways from non-trivial problems or architectural decisions for future reference.

What is the best way to document architectural decisions and problem-solving context for future teams?

Documenting architectural decisions is best handled by creating a structured Markdown file with standardized frontmatter and context hints. This ensures teammates can quickly locate design decisions and lessons learned from prior conversations.

How do I structure markdown notes to preserve conversation context and rationale?

You structure markdown notes by enforcing a standardized output format that includes a context hint, optional argument context, and standardized frontmatter. This layout makes design decisions and lessons learned discoverable for future teams.

When should I create reusable knowledge documents from my conversations?

You should create reusable knowledge documents after solving non-trivial problems, discovering patterns, or making architectural decisions. This captures the rationale and key takeaways while the context is still fresh for future reference.

Does this knowledge management approach require any specific dependencies or components?

This knowledge management approach requires no external dependencies or components. It operates independently to store clean, human-readable learnings directly into your docs/ directory as structured Markdown files.