docs

Audit and generate missing documentation for skills, agents, and hooks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill docs-arthtech-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/skills/docs
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill docs-arthtech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds missing or outdated documentation for skills, agents, and hooks, then generates the smallest useful updates so repository guidance stays accurate and discoverable.

Core Features & Use Cases

  • Documentation Auditing: Scans repository references such as README, getting-started guides, and context-loading notes to identify gaps.
  • Targeted Doc Generation: Writes minimal missing entries for user-facing documentation without duplicating automated reference files.
  • Validation Modes: Supports audit, write, and check workflows for manual review, automation, and CI enforcement.
  • Use Case: A maintainer can run it after adding a new skill to confirm it appears in the right docs and to generate any missing mention.

Quick Start

Ask the skill to audit documentation coverage for the current repository and generate any missing entries for skills, agents, or hooks.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I audit documentation coverage for skills and hooks in my repository?

To audit documentation coverage, scan repository references like READMEs and getting-started guides to identify gaps, then generate minimal missing entries for skills, agents, or hooks to keep guidance accurate and discoverable.

How do I generate missing markdown documentation for newly added agents?

Generate missing markdown documentation by scanning inventory and applying file presence validation across documentation surfaces, then writing minimal user-facing entries without duplicating automated reference files.

Can I enforce documentation checks in CI for installable AI workflow components?

Yes, you can enforce documentation checks in CI by running validation modes that audit, write, and check repository guidance to confirm skills, agents, and hooks appear in the correct docs.

What's the best way to keep frontmatter metadata and onboarding guides current?

The best way to keep frontmatter metadata and onboarding guides current is to run targeted documentation generation that validates file presence and writes the smallest useful updates for missing or outdated entries.

Why does my documentation audit skip automated reference files?

Documentation audits skip automated reference files to prevent duplication, focusing instead on generating minimal missing entries for user-facing documentation like onboarding guides and context-loading notes.