ck:docs-seeker

Locate library documentation by detecting topics and fetching llms.txt entries.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-docs-seeker-quanganh208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:docs-seeker
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/docs-seeker
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-docs-seeker-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Quickly locate and retrieve authoritative library and framework documentation without manual URL construction, saving time and minimizing token usage when working with large docs sets.

Core Features & Use Cases

  • Script-first workflow: Orchestrates detect-topic.js, fetch-docs.js, and analyze-llms-txt.js to automate topic detection, URL construction, fetching, and analysis of llms.txt results.
  • Robust fallback handling: Automatically falls back from topic-specific context7 URLs to general URLs, web search, or repository analysis when needed.
  • Agent distribution guidance: Analyzes llms.txt to categorize URLs (critical/important/supplementary) and recommends parallel or phased agent strategies for efficient research.
  • Use Case: Rapidly gather targeted API docs for a specific feature (e.g., "date picker in shadcn/ui") or assemble comprehensive library references for onboarding and migration planning.

Quick Start

Execute the scripts in order: detect the topic with node scripts/detect-topic.js "How do I use date picker in shadcn/ui?", fetch docs with node scripts/fetch-docs.js "How do I use date picker in shadcn/ui?", and analyze the resulting llms.txt with cat llms.txt | node scripts/analyze-llms-txt.js -.

Frequently Asked Questions about ck:docs-seeker

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

FAQPage Schema
How do I fetch library documentation using llms.txt?

Fetch library documentation by running Node.js scripts to detect topics, construct context7.com URLs, retrieve llms.txt entries, and parse results for targeted API references. This automates manual URL construction and minimizes token usage.

What is the best way to find specific feature docs in a large framework?

Finding specific feature docs uses a script-first workflow that detects topics, fetches relevant llms.txt entries, and categorizes URLs by importance. It recommends parallel or phased agent strategies for efficient downstream research.

Do I need an API key to retrieve documentation via context7 URLs?

Retrieving documentation via context7 URLs uses an optional CONTEXT7_API_KEY. You can execute Node.js scripts without it, as the workflow includes automatic fallback to general URLs, web search, or repository analysis.

What happens when a topic-specific documentation search fails?

When a topic-specific documentation search fails, the workflow automatically falls back to general context7 URLs, web search, or repository analysis. This robust fallback handling ensures you still retrieve relevant library references.

How do I analyze llms.txt results for agent distribution?

Analyze llms.txt results by piping the file into the analysis script, which categorizes URLs into critical, important, and supplementary tiers. It outputs recommendations for parallel or phased agent distribution strategies.

Can I use this documentation retrieval workflow for onboarding and migration planning?

Use this documentation retrieval workflow for onboarding and migration planning by assembling comprehensive library references. It detects topics, fetches authoritative docs via llms.txt, and categorizes URLs for efficient research.