Find Docs logo

Find Docs

CommunityPopular
ryan4yin
find-docs

Look up current documentation and code examples for a library, framework, SDK, CLI tool, or cloud service with the Context7 CLI. Use whenever a question names a specific technology — API syntax, configuration options, version migrations, library-specific debugging, setup, CLI usage — including well-known ones: training data goes stale on these details.

Overview

Publisherryan4yin
Repositorynix-config
Skill namefind-docs
Stars
2.1K
Forks
104
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ryan4yin on GitHub. Read the source before you install it.

Installation

Install the Find Docs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/ryan4yin/nix-config/tree/main/agents/skills/find-docs
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ryan4yin/nix-config.git /tmp/nix-config
mkdir -p .claude/skills
cp -r /tmp/nix-config/agents/skills/find-docs .claude/skills/find-docs
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Find Docs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Find Docs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Find Docs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Documentation lookup

ctx7 is on PATH (Home Manager, from nixpkgs). Run it as it is; the package is Nix-managed, so skip the setup and upgrade commands its --help advertises.

Two steps: resolve the library ID, then query with it.

bash
ctx7 library <name> "<query>"
ctx7 docs <libraryId> "<query>"

Skip step 1 only when the user supplies an ID as /org/project or /org/project/version. Add --json to either step when you will parse the output rather than read it.

A query leaves the machine: keep internal identifiers, private-repository paths, and credentials out of it.

Step 1: resolve the ID

Pass a query every time — it ranks the matches, so it also separates libraries that share a name. Use the official spelling ("Next.js", not "nextjs"); when results look wrong, retry the name before rewriting the query.

bash
ctx7 library "Next.js" "how to set up app router middleware"

Each match carries id, title, description, totalSnippets, trustScore, benchmarkScore, and versions. Prefer an exact name match with a high trustScore and more totalSnippets. When the user names a version, take the closest entry in versions and use /org/project/version as the ID.

Stop after three attempts and use the best match you have. When none is usable, say so and suggest a sharper name instead of guessing.

Step 2: query the docs

One topic per docs call: split unrelated concepts into separate calls, unless the question is about how they interact. Describe what to look up in the documentation rather than the task to complete — "React useEffect cleanup function with async operations" ranks, "hooks" returns generic results.

bash
ctx7 docs /vercel/next.js "how to add middleware"

The output is markdown: titled code snippets and prose snippets, each with the source URL it came from. Cite that URL when the answer rests on it.

When it fails

Lookups work without a login, at a lower rate limit. On a quota error, tell the user to run ctx7 login themselves; never ask them to paste a token into chat. If they do not authenticate, answer from training knowledge and say it may be outdated — do not fall back silently.

Frequently asked questions

What does the Find Docs AI skill do?

Look up current documentation and code examples for a library, framework, SDK, CLI tool, or cloud service with the Context7 CLI. Use whenever a question names a specific technology — API syntax, configuration options, version migrations, library-specific debugging, setup, CLI usage — including well-known ones: training data goes stale on these details.

Why use Find Docs on TypingMind?

Because you install it once and use it with any model. Find Docs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Find Docs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ryan4yin/nix-config/tree/main/agents/skills/find-docs. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Find Docs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Find Docs?

As many as you like. As long as a model supports skills, you can use Find Docs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Find Docs AI skill free?

Yes. It is published on GitHub by ryan4yin under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇