docs-config-authoring

Write and edit Markdown, YAML, JSON, TOML, and INI documentation files.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/nholder88/ai-agent-workflows --skill docs-config-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-config-authoring
Source: https://github.com/nholder88/ai-agent-workflows/tree/main/skills/docs-config-authoring
Command: npx skills add https://github.com/nholder88/ai-agent-workflows --skill docs-config-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write or edit non-code documentation and configuration files: Markdown, YAML, JSON, TOML, INI, agent files, README, CONTRIBUTING, workflow docs, config schemas, .env templates. USE FOR: README, CONTRIBUTING, workflow docs, config files, agent definitions, non-code documentation. DO NOT USE FOR: in-code documentation like JSDoc/docstrings (use code-documentation), code review (use code-review), implementation (use impl-* skills).

Core Features & Use Cases

  • Provide consistent non-code doc generation and editing across formats.
  • Support editing of Markdown, YAML, JSON, TOML, INI, and agent files.
  • Use case: Prepare a README and CONTRIBUTING file for a new project in minutes.

Quick Start

Provide a concise, clear non-code document for your project, such as a README or CONTRIBUTING file.

Frequently Asked Questions about docs-config-authoring

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

FAQPage Schema
How do I generate a README and CONTRIBUTING file for a new project?

To generate a README and CONTRIBUTING file, you provide project details and this Skill organizes and writes the non-code documentation consistently across Markdown formats. It prepares project onboarding and contributor guides in minutes.

Can I use this to write configuration files in YAML and JSON?

Yes, you can use this to write configuration files in YAML and JSON. This Skill supports editing and organizing config schemas, TOML, INI, and agent definition files, ensuring consistent configuration artifacts across repositories.

What is the best way to create workflow documents and agent definitions?

The best way to create workflow documents and agent definitions is using a dedicated non-code documentation generator. This Skill structures project guidance and agent files consistently, avoiding in-code implementation tasks.

Does this work for writing in-code documentation like JSDoc or docstrings?

No, this does not work for writing in-code documentation like JSDoc or docstrings. It specifically handles non-code artifacts like Markdown and YAML, avoiding code review and implementation tasks entirely.

How do I create a .env template for my project configuration?

To create a .env template, you specify your required environment variables and this Skill writes the non-code configuration file. It handles .env templates alongside TOML and INI formats for project setup.