write:insight

Capture a reusable insight from chat and store it as a learning note under docs/learnings.

Updated May 31, 2025
One-click install
npx skills add https://github.com/dEitY719/dotfiles --skill write-insight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write:insight
Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/write-insight
Command: npx skills add https://github.com/dEitY719/dotfiles --skill write-insight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams capture a single, reusable insight from a conversation and persist it as a concise learning note under docs/learnings, ensuring knowledge is discoverable and reusable.

Core Features & Use Cases

  • Capture one concrete insight from the chat and write it to docs/learnings/<slug>.md.
  • Maintain provenance by including sources (PRs, commits, files) and update the index in docs/learnings/README.md.
  • Enforce routing rules to keep content in the appropriate documentation spaces and decline topics that belong in other docs areas (docs/technic/, docs/standards/, claude/skills/).
  • Support hint-driven candidates to anchor the note and avoid re-asking the user for context.

Quick Start

Invoke /write:insight with an optional hint to draft a new learning note from this chat.

Frequently Asked Questions about write:insight

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

FAQPage Schema
How do I capture a reusable learning note from a chat conversation?

To capture a learning note from a chat, you extract a single insight and store it as a markdown file under docs/learnings with a specific slug. This ensures the knowledge remains discoverable and reusable across your team.

How do I maintain provenance when saving chat insights to documentation?

Maintaining provenance when saving chat insights involves recording sources like PRs, commits, and files within the note. The skill then updates the docs/learnings index to ensure full traceability of the discovered pattern.

What is the best way to extract debugging paths into reusable documentation?

Extracting debugging paths into reusable documentation is best achieved by isolating a single review-driven discovery and writing it to docs/learnings with a slug. Providing an optional hint anchors the note and prevents re-asking for context.

Can I use this to write technical standards or skill documentation?

You cannot use this for technical standards or skill documentation because it enforces routing rules that decline topics belonging in other spaces. It specifically restricts content meant for docs/technic/, docs/standards/, or claude/skills/ directories.

Why was my learning note rejected when I tried to save it from the chat?

Your learning note was likely rejected because the skill enforces routing rules to keep content in appropriate documentation spaces. It actively prevents saving topics that belong in docs/technic/, docs/standards/, or claude/skills/ directories.