oracle

Name: oracle
Availability: InStock
Author: drusifer

Maintain centralized project documentation and decisions across docs/ with *ora commands.

1|Updated Jan 10, 2026

Search Tags:#documentation #governance #archiving #knowledge-management #tldr #decision-recording

Ready to run

npx skills add https://github.com/drusifer/via --skill oracle-drusifer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oracle
Source: https://github.com/drusifer/via/tree/main/agents/oracle.docs
Command: npx skills add https://github.com/drusifer/via --skill oracle-drusifer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Knowledge governance and documentation consistency are hard when knowledge is scattered across files, teams, and tools. Oracle acts as the Chief Knowledge Officer to maintain a single source of truth and ensure cohesive, organized documentation.

Core Features & Use Cases

Centralized documentation governance across docs/, MINDMAP.md, ARCH.md, DECISIONS.md, LESSONS.md, and agent folders.
Knowledge distillation and TLDR generation to convert dense specs into atomic docs for quick loading.
Query and record capabilities via *ora groom, *ora ask, *ora record, *ora distill to keep information fresh and connected.

Quick Start

In a typical session, ask Ora to groom the repository, distill a long document, or log a decision by issuing the relevant *ora commands.

Frequently Asked Questions about oracle

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

FAQPage Schema

How do I maintain a single source of truth for project documentation?▼

Knowledge governance centralizes scattered project files into a single source of truth across docs/, DECISIONS.md, and LESSONS.md. This prevents documentation fragmentation and ensures cohesive knowledge architecture across teams and tools.

Can I generate a TLDR from dense specification documents?▼

Knowledge distillation converts dense specification documents into atomic TLDR docs for quick loading. This process distills lengthy project specs into concise, organized files that preserve core information without the overhead.

What's the best way to record project decisions and lessons learned?▼

Recording project decisions and lessons is best handled by logging them into dedicated files like DECISIONS.md and LESSONS.md. This builds a centralized knowledge base that keeps historical context fresh, organized, and connected across the repository.

How do I groom my repository for better file organization?▼

Grooming your repository involves applying documentation governance across agent folders and the docs/ directory. This governance process organizes scattered files into a cohesive architecture, ensuring information stays fresh and accessible.

Do I need specific frontmatter to set up documentation governance?▼

Documentation governance requires SKILL.md frontmatter to define its identity. It also supports optional resources like scripts/, references/, and assets/ directories to control the skill's capabilities and resources.