跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 find-docs

Find Docs

检索最新文档,API参考,以及任何开发者技术的代码示例. 每当用户询问特定的库,框架,SDK,CLI工具,或云服务——甚至对于React,Next.js,Prisma,Express,Tailwind,Django,或Spring Boot等知名的库,都使用此技能. 您的培训数据可能不反映最近的 API 修改或版本更新 .

7213 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

检索最新文档,API参考,以及任何开发者技术的代码示例. 每当用户询问特定的库,框架,SDK,CLI工具,或云服务——甚至对于React,Next.js,Prisma,Express,Tailwind,Django,或Spring Boot等知名的库,都使用此技能. 您的培训数据可能不反映最近的 API 修改或版本更新 .

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Documentation Lookup、Workflow、Step 1: Resolve library ID、Step 2: Query documentation、Step 1: Resolve a Library、Result fields。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates.

Documentation LookupWorkflowStep 1: Resolve library IDStep 2: Query documentationStep 1: Resolve a LibraryResult fieldsSelection processVersion-specific IDsGeneral (latest indexed)Version-specificStep 2: Query DocumentationWriting good queries

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
find-docs
description
Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「find-docs」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-dd64180c0b5d06a0-%E6%9F%A5%E6%89%BE%E6%96%87%E6%A1%A3.html
请存为 .cursor/skills/find-docs/SKILL.md 或 .claude/skills/find-docs/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/upstash/context7' --list

npx skills add 'https://github.com/upstash/context7' --skill 'find-docs'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: find-docs description: >- Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer — do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details. --- # Documentation Lookup Retrieve current documentation and code examples for any library using the Context7 CLI. Run commands with `npx ctx7@latest` so setup always uses the latest CLI without a global install: ```bash npx ctx7@latest library "" npx ctx7@latest docs "" ``` Optionally install globally if you prefer a bare `ctx7` command: ```bash npm install -g ctx7@latest ``` ## Workflow Two-step process: resolve the library name to an ID, then query docs with that ID. ```bash # Step 1: Resolve library ID npx ctx7@latest library "" # Step 2: Query documentation npx ctx7@latest docs "" ``` You MUST call `library` first to obtain a valid library ID UNLESS the user explicitly provides a library ID in the format `/org/project` or `/org/project/version`. IMPORTANT: Do not run these commands more than 3 times per question. If you cannot find what you need after 3 attempts, use the best result you have. ## Step 1: Resolve a Library Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. ```bash npx ctx7@latest library React "How to clean up useEffect with async operations" npx ctx7@latest library "Next.js" "How to set up app router with middleware" npx ctx7@latest library Prisma "How to define one-to-many relations with cascade delete" ``` Use the official library name with proper punctuation (e.g., "Next.js" not "nextjs", "Customer.io" not "customerio", "Three.js" not "threejs"). If results look wrong, try alternate spellings such as `next.js` before changing the query. Always pass a `query` argument — it is required and directly affects result ranking. Use the user's intent to form the query, which helps disambiguate when multiple libraries share a similar name. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query. ### Result fields Each result includes: - **Library ID** — Context7-compatible identifier (format: `/org/project`) - **Name** — Library or package name - **Description** — Short summary - **Code Snippets** — Number of available code examples - **Source Reputation** — Authority indicator (High, Medium, Low, or Unknown) - **Benchmark Score** — Quality indicator (100 is the highest score) - **Versions** — List of versions if available. Use one of those versions if the user provides a version in their query. The format is `/org/project/version`. ### Selection process 1. Analyze the query to understand what library/package the user is looking for 2. Select the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark score (higher is better, 100 is the maximum) 3. If multiple good matches exist, acknowledge this but proceed with the most relevant one 4. If no good matches exist, clearly state this and suggest query refinements 5. For ambiguous queries, request clarification before proceeding with a best-guess match ### Version-specific IDs If the user mentions a specific version, use a version-specific library ID: ```bash # General (latest indexed) npx ctx7@latest docs /vercel/next.js "How to set up app router" # Version-specific npx ctx7@latest docs /vercel/next.js/v14.3.0-canary.87 "How to set up app router" ``` The available versions are listed in the `library` command output. Use the closest match to what the user specified. ## Step 2: Query Documentation Retrieves up-to-date documentation and code examples for the resolved library. ```bash npx ctx7@latest docs /facebook/react "How to clean up useEffect with async operations" npx ctx7@latest docs /vercel/next.js "How to add authentication middleware to app router" npx ctx7@latest docs /prisma/prisma "How to define one-to-many relations with cascade delete" ``` ### Writing good queries The query directly affects the quality of results. Be specific and include relevant details, but keep each query to one topic — if the question spans multiple distinct concepts, run a separate `docs` command per concept instead of combining them, unless the question is about how the concepts interact. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query. | Quality | Example | |---------|---------| | Good | `"How to set up authentication with JWT in Express.js"` | | Good | `"React useEffect cleanup function with async operations"` | | Bad (too vague) | `"auth"` | | Bad (too vague) | `"hooks"` | | Bad (too broad) | `"routing and auth and caching in Next.js"` | Describe what to look up in the library's documentation, rather than the task to complete — vague one-word queries return generic results, and multi-topic queries dilute ranking and return shallow results for each topic. The output contains two types of content: **code snippets** (titled, with language-tagged blocks) and **info snippets** (prose explanations with breadcrumb context). ## Authentication Works without authentication. For higher rate limits: ```bash # Option A: environment variable export CONTEXT7_API_KEY=your_key # Option B: OAuth login npx ctx7@latest login ``` ## Error Handling If a command fails with a quota error ("Monthly quota reached" or "quota exceeded"): 1. Inform the user their Context7 quota is exhausted 2. Suggest they authenticate for higher limits: `npx ctx7@latest login` 3. If they cannot or choose not to authenticate, answer from training knowledge and clearly note it may be outdated Do not silently fall back to training data — always tell the user why Context7 was not used. ## Common Mistakes - Library IDs require a `/` prefix — `/facebook/react` not `facebook/react` - Always run `npx ctx7@latest library` first — `npx ctx7@latest docs react "hooks"` will fail without a valid ID - Use descriptive queries, not single words — `"React useEffect cleanup function"` not `"hooks"` - One topic per query — split `"routing and auth and caching"` into a separate `docs` command per concept, unless the question is about how they interact - Do not include sensitive information (API keys, passwords, credentials) in queries

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…