sl:docs-seeker

Retrieve library and framework documentation from context7.com llms.txt indexes.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-docs-seeker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sl:docs-seeker
Source: https://github.com/HuynhHoangPhuc/solon/tree/main/plugins/solon-core/skills/docs-seeker
Command: npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-docs-seeker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers and researchers often need quick access to library and framework documentation, API references, and usage notes, but manual web searches are slow and error-prone.

Core Features & Use Cases

  • External documentation lookup: query indexed docs from context7 llms.txt to surface API references and usage notes.
  • Topic-aware filtering: rank and present the top sections most relevant to the user's library and topic.
  • Reliable delivery: includes fallback sources and concise summaries for robust results.

Quick Start

Use /sl:docs-seeker <library-name> [topic] to retrieve focused API documentation.

Frequently Asked Questions about sl:docs-seeker

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

FAQPage Schema
How do I find library documentation and API references without manual web searches?

You can find library documentation by querying an external llms.txt index via context7.com, which parses the index and surfaces concise API references and usage notes for software development tasks.

Can I filter framework documentation by a specific topic or API usage?

Yes, you can filter framework documentation by applying topic-aware filtering to rank and present the top sections most relevant to your specified library and topic from the indexed results.

How do I retrieve summarized technical references for a specific library?

You retrieve summarized technical references by executing a query with the library name and topic, which fetches the top results from the index and returns a concise, structured summary.

Does this documentation lookup approach work for external libraries not natively installed?

Yes, this approach works for external libraries by querying indexed docs from context7 llms.txt, allowing you to surface API references and usage notes without requiring local installation.

What happens if the primary documentation lookup fails to find the API references?

If the primary lookup fails, the documentation retrieval includes fallback sources and generates concise summaries to ensure robust delivery of relevant technical references.

What format should I use to query API documentation for a specific framework?

You should use the format specifying the library name followed by an optional topic to retrieve focused API documentation and structured summaries from the indexed llms.txt data.