docs-sources

Detect documentation frameworks and generate JSON registry entries for fetch strategies.

8|1|Updated Jul 11, 2025
One-click install
npx skills add https://github.com/Consiliency/treesitter-chunker --skill docs-sources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-sources
Source: https://github.com/Consiliency/treesitter-chunker/tree/main/.ai-dev-kit/skills/docs-sources
Command: npx skills add https://github.com/Consiliency/treesitter-chunker --skill docs-sources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify and configure optimal fetch strategies for documentation sources.

Core Features & Use Cases

  • Detects documentation frameworks from common config files (Fern, Docusaurus, MkDocs, Mintlify, Sphinx, Nextra, Astro Starlight, Antora, GitBook, VuePress, ReadTheDocs) and guides on discovery.
  • Recommends appropriate fetch strategies (llms.txt, GitHub raw, OpenAPI, sitemap, or browser-based) and generates registry entries.
  • Supports end-to-end workflows from framework detection to registry configuration across 20+ platforms.

Quick Start

Prompt: Determine the best fetching strategy for the given documentation site and return a complete registry entry in JSON format.

Frequently Asked Questions about docs-sources

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

FAQPage Schema
How do I determine the best fetch strategy for a documentation site?

Fetch strategies depend on your documentation platform. This Skill detects frameworks like MkDocs, Docusaurus, Mintlify, and Sphinx, then recommends the optimal approach—llms.txt, GitHub raw, OpenAPI, sitemap, or browser-based—and generates a complete registry entry in JSON format.

What documentation frameworks does this support?

Support covers 20+ platforms including Fern, Docusaurus, MkDocs, Mintlify, Sphinx, Nextra, Astro Starlight, Antora, GitBook, VuePress, and ReadTheDocs. The Skill detects framework config files automatically and recommends fetch strategies specific to each.

Can I automate documentation registry entry generation?

Yes. This Skill performs end-to-end automation from framework detection through registry configuration. It analyzes documentation sources, applies frontmatter-based metadata and framework-detection patterns, then outputs ready-to-use JSON registry entries.

What output formats does this produce?

The Skill generates structured JSON registry entries. These entries capture fetch strategy configuration, framework metadata, and platform details needed to integrate documentation sources into downstream systems.

Does this work with GitHub repositories and OpenAPI specs?

Yes. Supported source types include GitHub repos with GitHub raw fetch strategy, OpenAPI specifications, llms.txt sites, and sitemap-based documentation. The Skill recommends the appropriate strategy per source type.

What preparation do I need before using this?

Identify your documentation site and its framework. The Skill handles framework detection from common config files, so you provide the source URL or repository path; no prior setup required.