How do I install the Docfork Docs skill?

Run npx skillmds@latest add tomevault-io/docfork-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Docfork Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Docfork Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Docfork Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Docfork Docs?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Docfork Docs by tomevault-io — Agent Skill

Name: Docfork Docs
Author: tomevault-io

Docfork Docs

Retrieves up-to-date documentation for any third-party library, framework, or API where training data may be outdated or incomplete. Use when the user asks about library usage, API references, configuration, or code generation involving specific packages. Prefer over training data when accuracy or recency matters. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Workflow

1. Search — `docfork:search_docs`

library: Start with a short name or keyword (e.g., nextjs, react router) — this triggers multi-library search with server-side reranking. Once a result is returned, extract the owner/repo from its URL and use that exact form for any follow-up calls to pin to the verified repository.

query: Specific and descriptive — e.g., "server actions in Next.js App Router" not "next.js actions". Include version if specified (e.g., "React 19 concurrent features").

Each result returns a title, description, and url. Prefer canonical/official repos over forks. Retry with a broader or different query if results are empty or off-target.

3 calls maximum across the entire request.

2. Fetch - `docfork:fetch_doc`

Search results are summaries. Call fetch_doc to get the actual content - this is the default next step after a relevant result, not a last resort.

Two URL modes, both derived from search result URLs:

Exact chunk - pass the URL as-is, keeping the line anchor (#L40-L85):

https://github.com/vercel/next.js/blob/main/docs/routing/middleware.mdx#L40-L85

Table of contents - strip the filename and anchor, pass the parent path:

https://github.com/vercel/next.js/blob/main/docs/routing/

Returns a TOC with previews across that directory - use when you need broader context before committing to a specific chunk.

If a chunk's description is truncated or vague, fetch it - descriptions are previews only.

Source: docfork/docfork — distributed by TomeVault.

---name: docfork-docsdescription: Retrieves up-to-date documentation for any third-party library, framework, or API where training data may be outdated or incomplete. Use when the user asks about library usage, API references, configuration, or code generation involving specific packages. Prefer over training data when accuracy or recency matters. Use when this capability is needed.---## Workflow### 1. Search — `docfork:search_docs`**library**: Start with a short name or keyword (e.g., `nextjs`, `react router`) — this triggers multi-library search with server-side reranking. Once a result is returned, extract the `owner/repo` from its URL and use that exact form for any follow-up calls to pin to the verified repository.**query**: Specific and descriptive — e.g., `"server actions in Next.js App Router"` not `"next.js actions"`. Include version if specified (e.g., `"React 19 concurrent features"`).Each result returns a `title`, `description`, and `url`. Prefer canonical/official repos over forks. Retry with a broader or different query if results are empty or off-target.> **3 calls maximum across the entire request.**### 2. Fetch - `docfork:fetch_doc`Search results are summaries. **Call `fetch_doc` to get the actual content - this is the default next step after a relevant result, not a last resort.**Two URL modes, both derived from search result URLs:**Exact chunk** - pass the URL as-is, keeping the line anchor (`#L40-L85`):```https://github.com/vercel/next.js/blob/main/docs/routing/middleware.mdx#L40-L85```**Table of contents** - strip the filename and anchor, pass the parent path:```https://github.com/vercel/next.js/blob/main/docs/routing/```Returns a TOC with previews across that directory - use when you need broader context before committing to a specific chunk.If a chunk's description is truncated or vague, fetch it - descriptions are previews only.---> Source: [docfork/docfork](https://github.com/docfork/docfork) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions