docs-sources

Detect documentation frameworks and configure fetch strategies for registry entries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Knowledge base helps teams identify and configure appropriate documentation sources and fetch strategies for AI-assisted content discovery and maintenance.

Core Features & Use Cases

  • Detect documentation platforms and frameworks from repository configurations.
  • Recommend fetch strategies (llms.txt, GitHub raw, OpenAPI, sitemap) and registry entries for new sites.
  • Provide a structured workflow to validate sources and configure integrations.

Quick Start

Analyze a new documentation site and propose a registry entry with the recommended fetch strategy and homepage.

Frequently Asked Questions about docs-sources

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

FAQPage Schema
How do I configure documentation sources and fetch strategies for AI-assisted content discovery?

To configure documentation sources for AI-assisted discovery, identify the platform framework and select a fetch strategy like llms.txt, GitHub raw, OpenAPI, or sitemap to generate a valid registry entry.

How do I detect documentation frameworks like Docusaurus or MkDocs from a repository?

Detect documentation frameworks by analyzing repository configurations for AI-native signals. This process identifies platforms like Docusaurus, MkDocs, Mintlify, Sphinx, Nextra, and Fern to recommend appropriate fetch strategies.

What is the best way to choose between llms.txt, GitHub raw, OpenAPI, and sitemap fetch strategies?

Choosing the best fetch strategy depends on your detected documentation framework. Evaluate llms.txt, GitHub raw, OpenAPI, and sitemap options based on framework configuration to recommend the most compatible registry entry.

Does this docs source workflow support framework detection for Mintlify and Fern platforms?

Yes, this docs source workflow supports framework detection for Mintlify and Fern platforms. It analyzes repository configurations to identify these frameworks and proposes a structured registry entry with the correct fetch strategy.

How do I validate new documentation sources before configuring a registry entry?

Validate new documentation sources by following a structured workflow that emphasizes AI-native signals and framework detection. This ensures the selected fetch strategy and homepage configuration are correct before integration.

Why do I need to detect AI-native signals when evaluating new documentation platforms?

Detecting AI-native signals is necessary when evaluating documentation platforms because it determines the optimal fetch strategy. This ensures accurate content discovery and proper registry configuration across different frameworks.