cyberarian

Automate Claude Code project documentation lifecycle with indexing and archiving.

5|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/slamb2k/mad-skills --skill cyberarian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cyberarian
Source: https://github.com/slamb2k/mad-skills/tree/main/cyberarian
Command: npx skills add https://github.com/slamb2k/mad-skills --skill cyberarian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Manually managing project documentation (organization, indexing, archiving) is time-consuming, inconsistent, and leads to cluttered context windows for AI. This skill automates the entire documentation lifecycle, ensuring consistency, discoverability, and automatic maintenance.

Core Features & Use Cases

  • Structured Organization: Enforces a consistent docs/ directory structure with semantic categories (specs, analysis, plans, ai_docs).
  • Automatic Indexing: Maintains an auto-generated INDEX.md for easy discoverability of all documents.
  • Lifecycle Management: Uses metadata (status, dates) to automatically archive old or completed documents, preventing clutter and keeping active documentation relevant.
  • Use Case: When starting a new project, use this skill to initialize a professional docs/ structure. As you create specifications or analysis documents, the skill ensures they are properly categorized, indexed, and eventually archived when complete, keeping your project documentation tidy and discoverable without manual effort.

Quick Start

Initialize the documentation structure for your project. Then, create a new specification document in docs/specs/my-new-spec.md and fill its frontmatter. Finally, update the index by running the indexing script.

Frequently Asked Questions about cyberarian

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

FAQPage Schema
How do I automate project documentation organization and indexing?

Automate documentation organization by initializing a structured docs/ directory with semantic categories (specs, analysis, plans, ai_docs), then use automatic indexing to maintain a discoverable INDEX.md that tracks all documents without manual updates.

What's the best way to keep project documentation from cluttering my context window?

Implement automatic archiving based on document metadata and status to move completed or outdated files out of active circulation, preserving context efficiency while maintaining a searchable archive for historical reference.

How do I set up a consistent documentation lifecycle for a new project?

Initialize a standardized docs/ directory structure with YAML frontmatter metadata on each document, configure category-specific archiving rules, and run indexing scripts to establish automated organization and maintenance from project start.

Can I use documentation automation with Git-based project workflows?

Yes, this approach integrates with Git workflows by organizing and indexing documentation in version-controlled directories, automating lifecycle tasks like archiving while preserving full Git history of all document changes.

What metadata do I need to add to documentation files for automatic management?

Add YAML frontmatter to each document containing status, creation date, and category fields; the automation uses these metadata fields to automatically index documents and trigger archiving according to defined lifecycle rules.

How does delegating verbose outputs to subagents help with documentation management?

Delegation templates route detailed analysis and lengthy outputs to subagents, keeping main documentation concise and focused; this preserves context window space while maintaining full documentation trails in designated subagent output locations.