Agent skill

Docs Seeker

by einverne in einverne/dotfiles

Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration.

GPL-3.0Auto-check passedMarketing & SEO

Install Docs Seeker

skills CLI
$ npx skills add einverne/dotfiles --skill docs-seeker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install einverne/dotfiles docs-seeker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/einverne/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/docs-seeker .claude/skills/docs-seeker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
docs-seeker
GitHub stars
121
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
443 words
Files
8 (incl. references)
Skills in repo
39
Repo updated
First seen
Licence
GPL-3.0

At a glance

Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration.

  • Works in 4 steps: Initial Discovery → llms.txt Processing → Repository Analysis → …
  • Latest documentation for libraries/frameworks
  • SKILL.md covers Overview, Core Workflow, Agent Distribution Guidelines and Version Handling, plus 5 more sections
  • Calls npm and git

What it does

Docs Seeker is an agent skill from einverne/dotfiles. Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `WORKFLOWS.md`, `references/best-practices.md` and `references/documentation-sources.md`).

It sits in Marketing & SEO, covering AI search optimization, Codebase knowledge for agents and Technical documentation. It works with GitHub. The repository describes itself as: my personal dotfiles managed by dotbot, zinit. The licence is GPL-3.0.

When your agent uses it

  • Latest documentation for libraries/frameworks
  • Documentation in llms.txt format
  • GitHub repository analysis
  • Documentation without direct llms.txt support

Example prompts

  • “/docs-seeker”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Initial Discovery
  2. llms.txt Processing
  3. Repository Analysis
  4. Fallback Research

What it can do on your machine

Read from SKILL.md and the folder at commit c6c0686. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.astro.build
    • nextjs.org
    • remix.run
    • kit.svelte.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Docs Seeker loads about 1.4k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 443 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~96
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from einverne/dotfiles at commit c6c0686, republished under its GPL-3.0 licence (© einverne). 443 words, ~1,362 tokens.

Download SKILL.mdSave it as .claude/skills/docs-seeker/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
docs-seeker
description
Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel
version
1.0.0

Documentation Discovery & Analysis

Overview

Intelligent discovery and analysis of technical documentation through multiple strategies:

  1. llms.txt-first: Search for standardized AI-friendly documentation
  2. Repository analysis: Use Repomix to analyze GitHub repositories
  3. Parallel exploration: Deploy multiple Explorer agents for comprehensive coverage
  4. Fallback research: Use Researcher agents when other methods unavailable

Core Workflow

Phase 1: Initial Discovery
  1. Identify target

    • Extract library/framework name from user request
    • Note version requirements (default: latest)
    • Clarify scope if ambiguous
  2. Search for llms.txt

    WebSearch: "[library name] llms.txt site:[docs domain]"

    Common patterns:

    • https://docs.[library].com/llms.txt
    • https://[library].dev/llms.txt
    • https://[library].io/llms.txt

    → Found? Proceed to Phase 2 → Not found? Proceed to Phase 3

Phase 2: llms.txt Processing

Single URL:

  • WebFetch to retrieve content
  • Extract and present information

Multiple URLs (3+):

  • CRITICAL: Launch multiple Explorer agents in parallel
  • One agent per major documentation section (max 5 in first batch)
  • Each agent reads assigned URLs
  • Aggregate findings into consolidated report

Example:

Launch 3 Explorer agents simultaneously:
- Agent 1: getting-started.md, installation.md
- Agent 2: api-reference.md, core-concepts.md
- Agent 3: examples.md, best-practices.md
Phase 3: Repository Analysis

When llms.txt not found:

  1. Find GitHub repository via WebSearch
  2. Use Repomix to pack repository:
    bash
    npm install -g repomix  # if needed
    git clone [repo-url] /tmp/docs-analysis
    cd /tmp/docs-analysis
    repomix --output repomix-output.xml
  3. Read repomix-output.xml and extract documentation

Repomix benefits:

  • Entire repository in single AI-friendly file
  • Preserves directory structure
  • Optimized for AI consumption
Phase 4: Fallback Research

When no GitHub repository exists:

  • Launch multiple Researcher agents in parallel
  • Focus areas: official docs, tutorials, API references, community guides
  • Aggregate findings into consolidated report

Agent Distribution Guidelines

  • 1-3 URLs: Single Explorer agent
  • 4-10 URLs: 3-5 Explorer agents (2-3 URLs each)
  • 11+ URLs: 5-7 Explorer agents (prioritize most relevant)

Version Handling

Latest (default):

  • Search without version specifier
  • Use current documentation paths

Specific version:

  • Include version in search: [library] v[version] llms.txt
  • Check versioned paths: /v[version]/llms.txt
  • For repositories: checkout specific tag/branch
Show full SKILL.md (179 more words)Show less

Output Format

markdown
# Documentation for [Library] [Version]

## Source
- Method: [llms.txt / Repository / Research]
- URLs: [list of sources]
- Date accessed: [current date]

## Key Information
[Extracted relevant information organized by topic]

## Additional Resources
[Related links, examples, references]

## Notes
[Any limitations, missing information, or caveats]

Quick Reference

Tool selection:

  • WebSearch → Find llms.txt URLs, GitHub repositories
  • WebFetch → Read single documentation pages
  • Task (Explore) → Multiple URLs, parallel exploration
  • Task (Researcher) → Scattered documentation, diverse sources
  • Repomix → Complete codebase analysis

Popular llms.txt locations:

Error Handling

  • llms.txt not accessible → Try alternative domains → Repository analysis
  • Repository not found → Search official website → Use Researcher agents
  • Repomix fails → Try /docs directory only → Manual exploration
  • Multiple conflicting sources → Prioritize official → Note versions

Key Principles

  1. Always start with llms.txt — Most efficient method
  2. Use parallel agents aggressively — Faster results, better coverage
  3. Verify official sources — Avoid outdated documentation
  4. Report methodology — Tell user which approach was used
  5. Handle versions explicitly — Don't assume latest

Detailed Documentation

For comprehensive guides, examples, and best practices:

Workflows:

  • WORKFLOWS.md — Detailed workflow examples and strategies

Reference guides:

© einverne, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in claude/skills/docs-seeker of einverne/dotfiles.

  • SKILL.md
  • WORKFLOWS.md
  • references/best-practices.md
  • references/documentation-sources.md
  • references/error-handling.md
  • references/limitations.md
  • references/performance.md
  • references/tool-selection.md

Open the folder on GitHubat commit c6c0686

Used in 1 other repository

We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in einverne/dotfiles, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Docs Seeker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Docs Seeker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Docs Seeker this skilleinverne/dotfiles1211 repos~1.4kAutomated safety check: PassGPL-3.0
GitHubkostja94/marketing-skills1k—~4.5kAutomated safety check: PassMIT
GitHub Readmethatrebeccarae/claude-marketing162—~2.9kAutomated safety check: PassMIT
LLM Docs OptimizerSidiora-Labs/centra-llm-agents115—~5.4kAutomated safety check: PassCustom licence
Founder Led ContentAIDevGTM/gtm-cofounder311—~998Automated safety check: PassMIT
PR Inline Commentssesori-ai/sesori_apps_monorepo126—~2.3kAutomated safety check: PassCustom licence

Similar skills

  • GitHub

    kostja94/marketing-skills

    When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists.

    1k GitHub stars~4.5k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed
  • GitHub Readme

    thatrebeccarae/claude-marketing

    Generate, audit, or update GitHub READMEs with project-type-aware structure, voice calibration, and SEO/AEO discoverability guidance.

    162 GitHub stars~2.9k tokensUpdated 4 mo ago
    Marketing & SEOAuto-check passed
  • LLM Docs Optimizer

    Sidiora-Labs/centra-llm-agents

    Optimize documentation for AI coding assistants and LLMs. An agent skill from Sidiora-Labs/centra-llm-agents.

    115 GitHub stars~5.4k tokensUpdated 20 days ago
    Marketing & SEOAuto-check passed
  • Founder Led Content

    AIDevGTM/gtm-cofounder

    Build authority by teaching the problem space, not announcing features.

    311 GitHub stars~998 tokensUpdated 3 days ago
    Marketing & SEOAuto-check passed
  • PR Inline Comments

    sesori-ai/sesori_apps_monorepo

    Fetch inline (code) review comments on a GitHub pull request, grouped into threads, with optional filtering by datetime.

    126 GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Skill Personalizer

    hqhq1025/skill-optimizer

    A skill your agent uses when auditing or adapting newly created, downloaded, forked, installed, or community Agent Skills to the user's tools, habits, directories, session history, and preferred…

    180 GitHub stars~630 tokensUpdated 4 mo ago
    Marketing & SEOAuto-check passed

More from einverne/dotfiles

All 39 skills in this repo
  • Chrome Devtools

    einverne/dotfiles

    Browser automation, debugging, and performance analysis using Puppeteer CLI scripts.

    121 GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check: notes
  • DOCX

    einverne/dotfiles

    Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction.

    121 GitHub starsUsed in 35 repos~2.5k tokens
    Auto-check: notes
  • PDF

    einverne/dotfiles

    Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms.

    121 GitHub starsUsed in 47 repos~1.8k tokens
    Auto-check passed
  • Gemini Audio

    einverne/dotfiles

    Guide for implementing Google Gemini API audio capabilities - analyze audio with transcription, summarization, and understanding (up to 9.5 hours), plus generate speech with controllable TTS.

    121 GitHub starsUsed in 1 repo~2k tokens
    Auto-check: notes
  • Gemini Image Gen

    einverne/dotfiles

    Guide for implementing Google Gemini API image generation - create high-quality images from text prompts using gemini-2.5-flash-image model.

    121 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check: notes
  • Gemini Vision

    einverne/dotfiles

    Guide for implementing Google Gemini API image understanding - analyze images with captioning, classification, visual QA, object detection, segmentation, and multi-image comparison.

    121 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check: notes

Works with

Questions about Docs Seeker

What does Docs Seeker do?

Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Docs Seeker is an agent skill from einverne/dotfiles.txt standard, GitHub repositories via Repomix, and parallel exploration.

When should I use Docs Seeker?

Docs Seeker fits situations like: latest documentation for libraries/frameworks; documentation in llms.txt format; GitHub repository analysis; documentation without direct llms.txt support.

How do I install Docs Seeker in Claude Code?

Run `npx skills add einverne/dotfiles --skill docs-seeker -a claude-code`. Or copy the skill folder (claude/skills/docs-seeker in einverne/dotfiles) into .claude/skills/docs-seeker in your project. Claude Code loads it when a task matches its description.

How do I install Docs Seeker in Codex?

Run `npx skills add einverne/dotfiles --skill docs-seeker -a codex`. Or copy the skill folder (claude/skills/docs-seeker in einverne/dotfiles) into .agents/skills/docs-seeker in your project. Codex loads it when a task matches its description.

Can I use Docs Seeker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add einverne/dotfiles --skill docs-seeker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-seeker, .gemini/skills/docs-seeker, .github/skills/docs-seeker and .opencode/skills/docs-seeker in your project.

What does Docs Seeker need to run?

Going by SKILL.md and its folder, Docs Seeker needs the command-line tools its instructions call (npm and git). Our summary lists: Node.js.

Does Docs Seeker access the network?

SKILL.md names 4 domains. As links in the text: docs.astro.build, nextjs.org, remix.run and kit.svelte.dev. This is read from the text; nothing was executed.

Is Docs Seeker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Docs Seeker use?

Docs Seeker is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Docs Seeker use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.

What are the alternatives to Docs Seeker?

Skills that share tags, products or a category with Docs Seeker: GitHub (kostja94/marketing-skills, 1k stars), GitHub Readme (thatrebeccarae/claude-marketing, 162 stars), LLM Docs Optimizer (Sidiora-Labs/centra-llm-agents, 115 stars) and Founder Led Content (AIDevGTM/gtm-cofounder, 311 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Seeker?

einverne (a GitHub user) maintains it in einverne/dotfiles, which has 121 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 9, 2026.

Source: einverne/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.