create-documentation

Automates AsciiDoc documentation creation using templates and a decision tree.

Updated Dec 10, 2025
One-click install
npx skills add https://github.com/Creative-Workz-Studio-LLC/bereshit --skill create-documentation-creative-workz-studio-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-documentation
Source: https://github.com/Creative-Workz-Studio-LLC/bereshit/tree/main/word/claude/skills/create-documentation
Command: npx skills add https://github.com/Creative-Workz-Studio-LLC/bereshit --skill create-documentation-creative-workz-studio-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cws.studio/pkg/util/fs/toml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables teams to create PhD-level documentation that is both rigorous and Bible-accessible, reducing ambiguity and ensuring consistent documentation practices across projects.

Core Features & Use Cases

  • Automated document-type guidance via a decision tree to select the appropriate template and structure.
  • 5-block documentation framework (Metadata, Header, Context, Content, Footer) to ensure discoverability and consistency across documents.
  • Template-driven generation with references and scripts to accelerate documentation workflows in technical environments.

Quick Start

Create a new AsciiDoc document using the base template and populate the metadata.

Frequently Asked Questions about create-documentation

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

FAQPage Schema
How do I automate AsciiDoc documentation generation with a consistent metadata structure?

Automate AsciiDoc documentation by applying a metadata-driven 5-block structure (Metadata, Header, Context, Content, Footer) to ensure consistent navigability. Template-based generation accelerates workflows by standardizing research notes, indexes, and community docs.

What is the best way to structure technical documentation for both PhD-level rigor and general accessibility?

Structure technical documentation using a layered reading framework that combines PhD-grade rigor with Bible accessibility. A 5-block documentation framework ensures discoverability while reducing ambiguity across standard guides and research notes.

How does a decision tree help select the right template for different types of documentation?

A decision tree guides automated document-type selection by evaluating requirements and routing to the appropriate template. This ensures consistent structural formatting across diverse outputs like standard guides, indexes, and community docs.

Can I use template-based generation for community docs and research notes in AsciiDoc?

Yes, template-based generation applies to AsciiDoc community docs, research notes, and indexes. The automated framework populates a base template with metadata to accelerate consistent documentation workflows.

Do I need a specific file system utility to manage TOML metadata for documentation templates?

The workflow relies on a TOML file system utility dependency to manage metadata for documentation templates. This integration drives the 5-block structure and ensures proper metadata parsing during AsciiDoc generation.

What are the limitations of using layered reading for technical documentation generation?

Layered reading requires strict adherence to the 5-block structure to function correctly. Documentation not conforming to the metadata-driven framework or lacking AsciiDoc compatibility will fail the automated generation process.