schema

Maps knowledge base file paths, naming conventions, and update triggers for project documentation.

Updated Aug 19, 2025
One-click install
npx skills add https://github.com/loganmancuso-scout/dotfiles --skill schema-loganmancuso-scout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema
Source: https://github.com/loganmancuso-scout/dotfiles/tree/main/dot_pi/agent/skills/schema
Command: npx skills add https://github.com/loganmancuso-scout/dotfiles --skill schema-loganmancuso-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working across multiple projects, it is hard to remember where context files, decision records, session logs, and investigation notes should live in a personal knowledge base. This Skill provides a quick-lookup reference so an AI agent always writes documentation to the correct location with the correct naming convention. ## Core Features & Use Cases - Path Reference: Defines exact file paths for context.md, runbook.md, gotchas.md, decisions, sessions, and investigations under ~/Documents/Notes/knowledge-base/projects/<project-slug>/. - Project Slug Resolution: Resolves the project slug from the nearest .git root or falls back to the current directory basename. - Update Triggers: Maps events like discovered gotchas, significant decisions, and completed work to the specific KB file that must be created or updated. - Scratch Workspace: Defines a SCRATCH-YYYY-MM-DD-topic.md convention for temporary planning files that are later distilled into permanent records. - Use Case: After finishing a debugging session, the agent consults this reference to create a session log in sessions/, link it from context.md, and record any new gotcha in gotchas.md without guessing paths. ## Quick Start Ask the agent to record today's completed work and any new gotchas in the knowledge base using the schema path reference.

Frequently Asked Questions about schema

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

FAQPage Schema
How do I organize project documentation in a personal knowledge base?

Use a per-project directory under knowledge-base/projects/<slug>/ containing context.md for institutional memory, decisions/ for ADRs, sessions/ for work logs, and investigations/ for multi-session debugging. The schema reference defines each exact path and naming convention.

How is the project slug determined for knowledge base paths?

The slug is the basename of the nearest .git root found by walking up from the current directory. If no git repository exists, it falls back to the basename of the current working directory.

When should I create an architecture decision record versus a session log?

Create an ADR in decisions/ when a significant decision is made, and index it in context.md under Past Decisions. Create a session log in sessions/ when work is completed, and link it under Recent Sessions in context.md.

What is a SCRATCH file and when should I use one?

A SCRATCH-YYYY-MM-DD-topic.md file in the sessions directory is a temporary workspace for planning, parking analysis, or exploring options. After the work is done, extract key findings into permanent session, decision, or context files and delete the scratch file.

Does this skill create the knowledge base files itself?

No, it is a path and trigger reference only, not a workflow executor. For full file schemas and creation workflows, load the scribe skill or read the templates in ~/Documents/Notes/templates/ before creating new files.