# Choose Reliable Documentation Fetch Strategies

Documentation sites expose content through different platforms and formats. This skill identifies the source type and recommends a practical fetch and registry strategy.

## Install

```bash
npx skillstore add consiliency/docs-sources
```

## Metadata

- Status: approved
- Slug: consiliency-docs-sources
- Skillstore revision: r1
- Version status: missing
- Tree hash: 5e29bc6e0e4f459f9c9801d6845b78e98bd74309875a4190e953badde25f0fb3
- Author: Consiliency
- GitHub username: Consiliency
- License: MIT
- Repository: https://github.com/Consiliency/treesitter-chunker/tree/main/.ai-dev-kit/skills/docs-sources
- Ref: 635f69fb8d2f4e6330ba47a4e5a0fb239c04d110
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/consiliency-docs-sources
- Manifest: https://skillstore.pages.dev/api/skills/consiliency-docs-sources/manifest

## Capabilities

- Detects documentation frameworks from config files, repository structure, and site signals.
- Prioritizes llms.txt, GitHub raw content, API specifications, sitemaps, and browser automation.
- Provides targeted fetch and detection commands for common documentation platforms.
- Drafts registry configurations with source paths, strategies, priorities, and filters.
- Maps common development libraries to likely documentation sources and strategies.

## Use Cases

- Add a documentation source: Detect the source platform, select a fetch strategy, and prepare a registry entry for a development team.
- Migrate documentation ingestion: Compare raw repository content, structured specifications, sitemaps, and browser fetching before changing an ingestion pipeline.
- Complete an AI documentation registry: Match detected project libraries to missing documentation sources and prioritize additions.

## Prompt Templates

### Choose a fetch strategy

```
Analyze documentation at {url}. Check source signals and recommend one fetch strategy with concise evidence.
```

### Configure one source

```
Prepare a registry entry for {library} at {url}. Detect its framework and specify the strategy, source paths, priority, and filters.
```

### Compare source options

```
Compare llms.txt, repository, API specification, sitemap, and browser options for {project}. Rank them by completeness, reliability, and maintenance cost.
```

### Design a resilient rollout

```
Design a documentation ingestion plan for {projects}. Include detection evidence, primary and fallback strategies, validation controls, rate limits, and registry updates.
```

## Limitations

- Does not verify that every example URL remains available.
- Browser fetching requires an existing browser wrapper and Chrome debugging setup.
- Private repositories and protected APIs require credentials that the skill does not manage.
- Remote content can be incomplete, rate-limited, or untrusted.

## Best Practices

- Check AI-native and raw repository sources before crawling rendered pages.
- Validate every remote destination and restrict crawls to approved public origins.
- Record detection evidence and test the selected strategy before updating the registry.

## Anti Patterns

- Do not launch browser automation before testing simpler direct-fetch methods.
- Do not follow sitemap or page links without scheme, host, and network-range validation.
- Do not add registry entries without confirming framework signals and source paths.

## Security Audit

- Audited at: 2026-07-13T16:11:00.459\+00:00
- Summary: The audit confirms two medium risks: nested sitemap fetching and browser link navigation can reach attacker-selected destinations. Other alerts are safe examples, Markdown formatting, fixed URLs, localhost checks, or harmless redirection; no prompt injection was found.

## Stats

- Views: 212
- Downloads: 8
- Favorites: 0
- Popularity score: 0