version: "1.0.1" name: oss-docs description: 'Scaffold or audit OSS docs.' practices: [code-complete, pragmatic-programmer] skill_api_version: 1 context: window: fork intent: mode: task sections: exclude: [HISTORY] intel_scope: topic license: MIT compatibility: Requires git metadata: author: Gas Town version: "1.0.0" tier: contribute internal: false allowed-tools: Read, Write, Edit, Glob, Grep, Bash output_contract: "CONTRIBUTING.md, CHANGELOG.md, AGENTS.md"

OSS Documentation Skill

Scaffold and audit documentation for open source projects.

Overview

This skill helps prepare repositories for open source release by:

1. Auditing existing documentation completeness
2. Scaffolding missing standard files
3. Generating content tailored to project type

Commands

Phase 0: Project Detection

# Determine project type and language
PROJECT_NAME=$(basename $(pwd))
LANGUAGES=()
 
[[ -f go.mod ]] && LANGUAGES+=("go")
[[ -f pyproject.toml ]] || [[ -f setup.py ]] && LANGUAGES+=("python")
[[ -f package.json ]] && LANGUAGES+=("javascript")
[[ -f Cargo.toml ]] && LANGUAGES+=("rust")
 
# Detect project category
if [[ -f Dockerfile ]] && [[ -d cmd ]]; then
    PROJECT_TYPE="cli"
elif [[ -d config/crd ]]; then
    PROJECT_TYPE="operator"
elif [[ -f Chart.yaml ]]; then
    PROJECT_TYPE="helm"
else
    PROJECT_TYPE="library"
fi

Subcommand: audit

Required Files (Tier 1 - Core)

Recommended Files (Tier 2 - Standard)

Optional Files (Tier 3 - Enhanced)

Subcommand: scaffold

Template Selection

Documentation Organization

project/
├── README.md              # Overview + quick start
├── AGENTS.md              # AI assistant context
├── CONTRIBUTING.md        # Contributor guide
├── CHANGELOG.md           # Keep a Changelog format
├── docs/
│   ├── QUICKSTART.md      # Detailed getting started
│   ├── CLI_REFERENCE.md   # Complete command reference
│   ├── ARCHITECTURE.md    # System design
│   └── CONFIG.md          # Configuration options
└── examples/
    └── README.md          # Examples index

AGENTS.md Pattern

# Agent Instructions
 
This project uses **<tool>** for <purpose>. Run `<onboard-cmd>` to get started.
 
## Quick Reference
 

<cmd1> # Do thing 1 <cmd2> # Do thing 2

 
## Landing the Plane (Session Completion)
 
**MANDATORY WORKFLOW:**
 
1. **Run quality gates** - Tests, linters, builds
2. **Commit changes** - Meaningful commit message
3. **PUSH TO REMOTE** - This is MANDATORY
4. **Verify** - All changes committed AND pushed

Style Guidelines

1. Be direct - Get to the point quickly
2. Be friendly - Welcome contributions
3. Be concise - Avoid boilerplate
4. Use tables - For commands, options, features
5. Show examples - Code blocks over prose
6. Link liberally - Cross-reference related docs

Skill Boundaries

DO:

• Audit existing documentation
• Generate standard OSS files
• Validate documentation quality

DON'T:

• Overwrite existing content without confirmation
• Generate code documentation (use $doc)
• Create CI/CD files (out of scope — configure CI/CD separately)

Examples

OSS Readiness Audit

User says: "Audit this repo for open-source documentation readiness."

What happens:

1. Evaluate presence/quality of core OSS docs.
2. Identify missing or weak sections.
3. Output prioritized documentation actions.

Scaffold Missing Docs

User says: "Generate missing OSS docs for this project."

What happens:

1. Detect project type and documentation gaps.
2. Scaffold standard files with project-aware content.
3. Produce a checklist for final review and landing.

Troubleshooting

Reference Documents

• references/beads-patterns.md
• references/documentation-tiers.md
• references/project-types.md