Agent skill

skill-doc-generator

Auto-generates standardized README documentation from SKILL.md files, validates consistency (frontmatter, descriptions, terminology), and creates usage examples. Use when documenting individual skills, generating docs for multiple skills in a directory, or validating skill quality standards.

Stars 19
Forks 5

Install this agent skill to your Project

npx add-skill https://github.com/Exploration-labs/Nates-Substack-Skills/tree/main/skill-doc-generator

SKILL.md

Skill Documentation Generator

Auto-generate high-quality README documentation for skills with built-in consistency validation and example generation.

Overview

This skill automates the creation of standardized README files for skills by analyzing SKILL.md files, extracting structure and examples, validating quality standards, and generating comprehensive documentation. It ensures consistency across skill documentation while providing actionable validation feedback.

Workflow

Single Skill Documentation

Generate documentation for one skill:

  1. Analyze the skill:

    bash
    python scripts/analyze_skill.py <skill_directory>
    

    Extracts metadata, sections, code blocks, and resources.

  2. Validate consistency:

    bash
    python scripts/validate_consistency.py <skill_directory> --verbose
    

    Checks frontmatter, description quality, and terminology.

  3. Generate README:

    bash
    python scripts/generate_readme.py <skill_directory> [output_path]
    

    Creates README.md with validation results.

Batch Documentation

Document multiple skills at once:

bash
python scripts/document_directory.py <directory> [options]

Options:

  • --output <dir>: Specify output directory
  • --no-recursive: Don't search subdirectories
  • --no-index: Skip index file generation
  • --no-validate: Skip validation checks

Example:

bash
# Document all user skills with validation
python scripts/document_directory.py /mnt/skills/user --output ./docs

# Quick pass without validation
python scripts/document_directory.py ./my-skills --no-validate

Script Reference

analyze_skill.py

Parses SKILL.md and extracts structured information.

Usage: python scripts/analyze_skill.py <skill_directory>

Returns:

  • Metadata (name, description)
  • Sections and structure
  • Code blocks with language tags
  • Referenced resources (scripts, references, assets)
  • Statistics (line count, section count)

validate_consistency.py

Validates skill quality against standards defined in references/consistency-rules.md.

Usage: python scripts/validate_consistency.py <skill_directory> [--verbose]

Checks:

  • Frontmatter completeness and format
  • Description quality (length, clarity, triggers)
  • Structure appropriateness
  • Terminology consistency
  • Resource references
  • Code example quality

Severity Levels:

  • ERROR: Breaks functionality (missing required fields)
  • WARNING: Quality issues (naming, unreferenced resources)
  • INFO: Suggestions (style, optional improvements)

generate_readme.py

Creates README.md from skill analysis.

Usage: python scripts/generate_readme.py <skill_directory> [output_path]

Generates:

  • Title and description
  • Overview from SKILL.md
  • Trigger scenarios
  • Structure statistics
  • Bundled resource lists with links
  • Key sections overview
  • Usage examples (up to 3)
  • Validation results (optional)

Template: See references/readme-template.md for structure.

document_directory.py

Batch processes multiple skills in a directory.

Usage: python scripts/document_directory.py <directory> [options]

Features:

  • Recursive skill discovery
  • Parallel validation and documentation
  • Index generation with categorization
  • Summary statistics
  • Error handling per skill

Quality Standards

Validation enforces these standards:

Frontmatter

  • name: Lowercase with hyphens (e.g., skill-name)
  • description: 50-500 chars, clear triggers
  • Must start with capital letter
  • Include "when" or "use" phrases

Structure

  • Body: 100+ chars minimum, <500 lines recommended
  • Sections: Overview/workflow recommended
  • Resources: All files referenced in SKILL.md

Terminology

  • Use imperative form: "Use" not "You should use"
  • Capitalize "Claude" consistently
  • Avoid vague terms: "various", "multiple"
  • Active voice preferred

See references/consistency-rules.md and references/terminology-standards.md for complete standards.

Reference Files

readme-template.md

Standard README structure and best practices. Defines:

  • Required sections
  • Optional sections
  • Formatting guidelines
  • Link conventions

consistency-rules.md

Detailed validation criteria. Covers:

  • Frontmatter requirements
  • Description quality metrics
  • Structure guidelines
  • Resource validation
  • Error severity definitions

terminology-standards.md

Standard vocabulary and style guide. Includes:

  • Writing style (imperative form)
  • Common terms and their usage
  • Phrases to avoid
  • Formatting conventions
  • Consistency checklist

Examples

Example 1: Document a Single Skill

bash
# Analyze
python scripts/analyze_skill.py ./my-skill

# Validate
python scripts/validate_consistency.py ./my-skill --verbose

# Generate README
python scripts/generate_readme.py ./my-skill

Example 2: Batch Process with Index

bash
# Document all skills in a directory
python scripts/document_directory.py /mnt/skills/user \
  --output ./documentation \
  --recursive

Example 3: Quick Validation Pass

bash
# Just validate without generating docs
python scripts/validate_consistency.py ./my-skill

Common Use Cases

New skill creation: Generate documentation as part of skill development Quality audits: Validate existing skills against standards Documentation updates: Regenerate READMEs after SKILL.md changes Batch operations: Document entire skill libraries CI/CD integration: Automated validation in deployment pipelines

Tips

  • Run validation before generating documentation to catch issues early
  • Use --verbose flag to see INFO-level suggestions
  • Reference files provide the "why" behind validation rules
  • Generated READMEs include validation results for transparency
  • Index files help navigate large skill collections

Expand your agent's capabilities with these related and highly-rated skills.

Exploration-labs/Nates-Substack-Skills

token-budget-advisor

Proactive token budget assessment and task chunking strategy. Use this skill when queries involve multiple large file uploads, requests for comprehensive multi-document analysis, complex multi-step workflows with heavy research (10+ tool calls), phrases like "complete analysis", "full audit", "thorough review", "deep dive", or tasks combining extensive research with large output artifacts. This skill helps assess token consumption risk early and recommend chunking strategies before beginning work.

19 5
Explore
Exploration-labs/Nates-Substack-Skills

resume-builder

Comprehensive resume creation, review, and optimization with support for multiple formats, ATS optimization, industry-specific guidance, and career stage customization. Use this skill when users request help writing, creating, reviewing, improving, or tailoring resumes for job applications.

19 5
Explore
Exploration-labs/Nates-Substack-Skills

agentic-development

Conversational guidance for building software with AI agents, covering workflows, tool selection, prompt strategies, parallel agent management, and best practices based on real-world high-volume agentic development experience. Use this skill when users ask about setting up agentic workflows, choosing models, optimizing prompts, managing parallel agents, or improving agent output quality.

19 5
Explore
Exploration-labs/Nates-Substack-Skills

prompting-pattern-library

Comprehensive library of proven prompting patterns, frameworks, and examples for different use cases. This skill should be used when creating prompting guides, analyzing prompt effectiveness, teaching prompting techniques, or troubleshooting prompting issues. Use when writing about prompting, explaining prompting concepts to others, or improving existing prompts.

19 5
Explore
Exploration-labs/Nates-Substack-Skills

requirements-elicitation

Systematic framework for analyzing product documents (PRDs, feature specs, user stories, roadmaps, one-pagers) to identify gaps, generate clarifying questions for PMs and engineers, and assess technical risks. This skill should be used when engineers or technical leads need to bridge PM documents and implementation by eliciting missing technical details rather than making assumptions. Use when asked to extract technical requirements, review specs, identify what's missing, or prepare clarifying questions from product documents.

19 5
Explore
Exploration-labs/Nates-Substack-Skills

skill-debugging-assistant

Debug, diagnose, and troubleshoot skill issues including trigger failures, parameter problems, prompt conflicts, and SKILL.md structural issues. Use when skills don't activate as expected, trigger incorrectly, produce unexpected behavior, conflict with system instructions, or fail packaging validation. Analyzes YAML frontmatter, descriptions, progressive disclosure, token budget, absolute statements, and reference file organization. For skill creators reviewing, validating, or fixing skill problems.

19 5
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results