Wdoc Skill logo

Wdoc Skill

Community
thiswillbeyourgithub
wdoc-skill

Comprehensive reference for wdoc, a RAG CLI and Python library that summarizes, searches, and queries documents across 20+ filetypes (PDF, YouTube, audio, Anki, web, Zotero, Karakeep, and more) through LiteLLM (100+ LLM providers). Use when the user runs or asks about the `wdoc` command, imports `from wdoc import wdoc`, or needs help with wdoc tasks (query, search, summarize, parse), CLI arguments, environment variables, filetypes, or the Python API.

Overview

Publisherthiswillbeyourgithub
Repositorywdoc
Skill namewdoc-skill
Stars
545
Forks
47
Bundled files
2
LicenseAGPL-3.0
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.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Wdoc Skill 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/thiswillbeyourgithub/wdoc/tree/main/wdoc-skill
  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/thiswillbeyourgithub/wdoc.git /tmp/wdoc
mkdir -p .claude/skills
cp -r /tmp/wdoc/wdoc-skill .claude/skills/wdoc-skill
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Wdoc Skill 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 Wdoc Skill 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 Wdoc Skill 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.

wdoc

Written for wdoc v5.1.0. On a different version, some arguments, defaults, or behaviors may differ.

wdoc is a RAG (Retrieval-Augmented Generation) system for summarizing, searching, and querying documents across 20+ file types. It works as a CLI (via Google Fire) and as a Python library (from wdoc import wdoc), routing every LLM call through LiteLLM (100+ providers).

This SKILL.md is the quick orientation. The deep material lives in two companion files:

  • REFERENCE.md: every CLI argument, filetype, loader option, environment variable, and the full Python API.
  • EXAMPLES.md: copy-pasteable shell and Python examples.

Quick start

bash
pip install -U wdoc[full]            # full install: all loaders. Plain `wdoc` ships only PDF + URL.
export ANTHROPIC_API_KEY="your_key"  # or whichever provider you use

wdoc query     paper.pdf "What are the main findings?"   # ask questions (RAG)
wdoc summarize paper.pdf                                  # detailed markdown summary
wdoc parse     paper.pdf                                  # parse to text, no LLM
wdoc web       "latest on quantum computing"             # DuckDuckGo + query

uvx wdoc[full] ... runs it without installing and sidesteps thinking about extras.

The four tasks

TaskWhat it doesPick it when
queryEmbeds docs, retrieves chunks, answers with sourced markdownYou have a question about the content
searchReturns matching docs + metadata, no LLM answerYou only need to locate relevant passages
summarizeDetailed markdown summary (author's reasoning, not vague takeaways)You want the gist of a long document
summarize_then_querySummarize first, then drop into a query promptYou want both, in one run

Core mechanics worth knowing

  • Shortcuts: wdoc query FILE, wdoc summarize FILE, wdoc parse FILE, and wdoc web "q" expand to longer --task=... forms. Positional args work too: wdoc TASK PATH [QUERY].
  • Filetype is auto-detected (--filetype=auto) but can be forced (pdf, youtube, anki, zotero, ...). Recursive filetypes (recursive_paths, zotero, karakeep, ddg, ...) fan one selector out into many documents.
  • Two models per run: a strong --model answers, a cheap --query_eval_model filters chunks. Both take LiteLLM provider/model ids.
  • kebab or snake case: --query-eval-model and --query_eval_model are equivalent.
  • Piped input is auto-detected: cat file.pdf | wdoc parse --filetype=pdf.
  • Privacy: --private (or WDOC_PRIVATE_MODE=true) blocks all outbound traffic and redacts API keys; pair it with local models (Ollama) and --llms_api_bases.
  • Reuse embeddings: --save_embeds_as=idx.pkl once, then --load_embeds_from=idx.pkl to skip re-indexing.
  • Cost guard: --dollar_limit (default 5) stops summaries/embeddings before they get expensive.

Common patterns

bash
# Query every PDF in a tree
wdoc --task=query --path="papers/" --filetype=recursive_paths \
     --pattern="**/*.pdf" --recursed_filetype=pdf --query="..."

# Fully local / private
wdoc --private --model="ollama/qwen3:8b" --query_eval_model="ollama/qwen3:8b" \
     --embed_model="ollama/snowflake-arctic-embed2" --task=query --path=secret.pdf

# Parse for use elsewhere (text, langchain, langchain_dict, xml, split_text)
wdoc parse document.pdf --format=langchain_dict
python
from wdoc import wdoc
instance = wdoc(task="query", path="paper.pdf", model="openai/gpt-4o")
answer = instance.query_task("What are the main contributions?")
print(answer["final_answer"])

For anything beyond this page (exact argument types, defaults, every filetype's loader options, all WDOC_* env vars, the full Python API surface, and more examples), read REFERENCE.md and EXAMPLES.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Wdoc Skill AI skill do?

Comprehensive reference for wdoc, a RAG CLI and Python library that summarizes, searches, and queries documents across 20+ filetypes (PDF, YouTube, audio, Anki, web, Zotero, Karakeep, and more) through LiteLLM (100+ LLM providers). Use when the user runs or asks about the `wdoc` command, imports `from wdoc import wdoc`, or needs help with wdoc tasks (query, search, summarize, parse), CLI arguments, environment variables, filetypes, or the Python API.

Why use Wdoc Skill on TypingMind?

Because you install it once and use it with any model. Wdoc Skill 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 Wdoc Skill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thiswillbeyourgithub/wdoc/tree/main/wdoc-skill. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Wdoc Skill?

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 Wdoc Skill?

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

Is the Wdoc Skill AI skill free?

Yes. It is published on GitHub by thiswillbeyourgithub under the AGPL-3.0 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 👇