dream

Lint, consolidate, and reorganize datarim knowledge base documents.

11|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Arcanada-one/datarim --skill dream-arcanada-one
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dream
Source: https://github.com/Arcanada-one/datarim/tree/main/skills/dream
Command: npx skills add https://github.com/Arcanada-one/datarim --skill dream-arcanada-one

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dream eliminates the bookkeeping chaos that accumulates in a growing datarim knowledge base by detecting misplaced, inconsistent, stale, or duplicated documents and fixing the structure through proposals.

Core Features & Use Cases

  • Ingest triage for new items: Finds files in the wrong directories, missing required metadata (like task IDs/frontmatter), broken internal links, and archive/reflection mismatches, then proposes moves, renames, and link repairs.
  • Lint for health checks: Scans for contradictions, stale references, orphan/oversized/empty content, duplicate coverage, broken links, and archive/reflection symmetry issues, producing a severity-grouped report.
  • Consolidation and reorganization: Merges duplicates, updates progress and index coverage, extracts recurring patterns into a catalog, adds bidirectional cross-references, and archives stale content with proper metadata.

Quick Start

Ask Dream to run a full knowledge base maintenance pass by using: /dr-dream

Frequently Asked Questions about dream

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

FAQPage Schema
How do I detect and fix stale references in a documentation knowledge base?

Documentation staleness detection scans your knowledge base to identify stale references, orphaned content, and broken links, then generates actionable proposals to repair and reorganize the structure without silently overwriting files.

What is the best way to consolidate duplicate documents and add cross-references?

Consolidating duplicate documents involves merging overlapping content, extracting recurring patterns into a catalog, and adding bidirectional cross-references to maintain a clean, organized, and consistent knowledge base.

How do I lint project documentation for structural issues and metadata mismatches?

Linting project documentation checks for missing frontmatter, naming inconsistencies, archive-reflection symmetry issues, and broken internal links, producing a severity-grouped health report to guide structural fixes.

Can I enforce naming conventions and metadata requirements across datarim directories?

Yes, you can enforce naming conventions, required metadata like task IDs, and directory placement rules across datarim directories by running an ingest triage that proposes moves and renames for non-compliant files.

Why does my knowledge base maintenance tool report archive-reflection symmetry issues?

Archive-reflection symmetry issues occur when files in the documentation archive do not properly mirror their active counterparts, requiring structural linting to detect mismatches and propose metadata updates.

Do I need a specific directory structure to run knowledge base deduplication and reorganization?

Knowledge base deduplication and reorganization requires project documentation stored in datarim and documentation/archive directories to accurately scan for duplicates, enforce metadata, and apply cross-references.