knowie-capture

Dispatch discussions and ideas into a structured markdown knowledge base by perspective and maturity.

9|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/timcsy/semorphe --skill knowie-capture-timcsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowie-capture
Source: https://github.com/timcsy/semorphe/tree/main/.claude/skills/knowie-capture
Command: npx skills add https://github.com/timcsy/semorphe --skill knowie-capture-timcsy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Decisions, lessons, and ideas from AI-assisted discussions evaporate when the conversation ends, leaving no traceable record of why choices were made. This Skill routes each piece of a discussion into the right place in a markdown knowledge base so the reasoning behind a project stays reconstructable. ## Core Features & Use Cases - Perspective-based dispatch: Splits input into normative (principles), situational (vision), and existential (experience) knowledge, routing each piece to its proper file rather than dumping everything in one place. - Maturity gating: Sends undecided ideas to a draft area and requires human confirmation before writing into long-term memory, keeping captured content separate from committed knowledge. - Procedural capture: Detects repeated operations and consolidates them into reusable skills stored in a knowledge/skills directory, then projects them via symlinks into tool skill folders. - Use Case: After a design discussion where the team rejected option A, chose option B, and learned a testing pitfall, run this Skill to tombstone the rejection in history, park the design in draft, and record the lesson in experience. ## Quick Start Ask the AI to capture the current discussion into the knowie knowledge base, splitting it by perspective and maturity.

Frequently Asked Questions about knowie-capture

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

FAQPage Schema
How do I capture decisions from an AI discussion into a knowledge base?

Invoke the capture skill with the idea or leave the argument empty to capture the current discussion. It splits the content by perspective (principles, vision, experience) and routes each piece by maturity, writing undecided items to draft first.

What is the difference between draft and committed knowledge in knowie?

Draft holds undecided thoughts that decay by default and can be written directly by the AI. Committed knowledge in principles, vision, or experience requires human confirmation, enforcing the rule that captured does not equal committed.

When should a completed task go into history versus experience?

A completion only earns a history entry when it revealed a pivot where a prior decision changed. Shipping notes belong in commits or changelogs, while verified lessons reflow into experience and recall-worthy scenes go to episodes.

Can repeated manual operations be turned into reusable skills?

Yes. When the same operation is performed repeatedly, it is recorded as a draft candidate, and after human confirmation it consolidates into knowledge/skills as a SKILL.md folder, then symlinks into tool skill directories like .claude/skills.

What are the limitations of automated knowledge capture?

The AI only performs reversible mechanical work like moving, indexing, and drafting. It never writes into long-term tiers or root principles on its own, so a human must confirm commits, principle amendments, and skill consolidation.