DeepWiki Index

DeepWiki indexing for Claude Code and Grok — autonomously index public GitHub repos so the Ask DeepWiki badge resolves, using the verified API trigger and a trusted browser for silent reCAPTCHA.

Install

Claude Code

/plugin marketplace add 88plug/claude-code-plugins
/plugin install deepwiki-index@88plug

Grok Build

grok plugin marketplace add 88plug/claude-code-plugins
grok plugin install deepwiki-index@88plug --trust

Once installed, the skill is available to the agent. No extra config file is required. Manual/batch runs of the helper need Playwright (see Manual / batch use).

Quickstart

1. Install the plugin (above).
2. Publish a public GitHub repo, or add the DeepWiki badge to an existing one.
3. Ask the agent, or let it auto-trigger:

Index the DeepWiki for this repo.

1. Wait for the status poll. Indexing usually finishes in 2–10 minutes.
2. Open https://deepwiki.com/<owner>/<repo> — the wiki should load, and the badge should resolve.

Tip

Prefer a trusted local browser (your real Chrome profile, or screen-mcp driving the desktop). Silent reCAPTCHA minting depends on that context.

Features

Capability	Detail
Autonomous indexing	Agent runs without asking after publish, badge add, or "index the wiki"
Verified trigger	Encodes api.devin.ai DeepWiki endpoints — no re-research each session
Trusted-browser token	screen-mcp desktop path or Playwright + real Chrome profile
Status polling	Public API only; success means completed / indexed, not a button click
Batch processing	One repo, comma-list, or full 88plug marketplace set (REPO=all)
One-time bootstrap	DeepWiki re-crawls after the first index — not a per-commit CI job

When it auto-triggers

The skill description tells the agent to run without asking when any of these apply:

Situation	What the agent does
You publish a new public repo	Checks status, triggers index if needed, polls to completed
You add the "Ask DeepWiki" badge	Same flow so the badge target exists
You say "index the wiki", "make the badge work", or "index the deepwiki repos"	Indexes the current repo, a named list, or a batch
Major changes and you want a refresh	Re-triggers when status is not already complete
Batch of public repos	Runs the helper with REPO=… or REPO=all

It will not treat indexing as a per-commit job. After the first successful index, DeepWiki re-crawls on its own.

Note

Private repos are out of scope. Those need a Devin org account. This plugin only covers public GitHub repos via the public DeepWiki APIs.

What it does

Once installed, the agent:

1. Checks status via the public status API.
2. If not already done, triggers indexing through a trusted browser path.
3. Polls until status is complete (or times out).
4. Reports the real API result — never claims "indexed" from a click alone.

It ships two execution paths (agent picks in order of preference):

Path	When	How
screen-mcp (real desktop)	screen-mcp is connected	Opens https://deepwiki.com/<owner>/<repo>, fills notify email, clicks Index Repository
Bundled Playwright helper	Local Chrome / Chromium available	scripts/index-deepwiki.mjs mints the invisible token in-page and POSTs the trigger

How indexing works (high level)

DeepWiki builds a browsable wiki for a public GitHub repo. The "Ask DeepWiki" badge points at https://deepwiki.com/<owner>/<repo>. That page only becomes useful after the repo has been submitted for indexing once.

The skill encodes the verified public API so the agent never re-researches it:

Step	Endpoint
Trigger	POST https://api.devin.ai/ada/index_public_repo?repo_name=<owner/repo>&email_to_notify=<email>&recaptcha_token=<tok>
Status (open, no auth)	GET https://api.devin.ai/ada/public_repo_indexing_status?repo_name=<owner/repo>

Status values you will see include unknown, indexing, and completed (the helper also treats several synonyms such as indexed / ready as done).

flowchart LR
  A[Check status API] --> B{Already complete?}
  B -->|yes| C[Report done]
  B -->|no| D[Trusted browser mints token]
  D --> E[POST index_public_repo]
  E --> F[Poll status until completed]
  F --> C

reCAPTCHA and the trusted browser

The trigger requires a reCAPTCHA v2 invisible token. Without it the API returns 400 (reCAPTCHA validation failed). The site key is bound to deepwiki.com.

• On a trusted browser (real desktop Chrome, or Chromium launched with your real user-data directory), the invisible widget mints a token with no challenge UI.
• On datacenter, bare headless, or low-reputation contexts, the same widget may present an image challenge. The skill does not solve image challenges. It fails clearly and hands you the command to run on a trusted machine.

So the design is simple: run the trigger where a normal user browser already has a good reputation — either drive that browser via screen-mcp, or point the Playwright helper at your Chrome profile with CHROME_USER_DATA_DIR.

Important

Do not wire this into CI as a required job. CI cannot mint a silent token reliably. Index once from your machine after publish; DeepWiki maintains the wiki afterward.

Manual / batch use

Install Playwright once, then run the helper from a clone of this repo (or from ${CLAUDE_PLUGIN_ROOT} when the plugin is installed):

npm i -D playwright && npx playwright install chromium

# current git remote (origin → owner/repo)
node scripts/index-deepwiki.mjs

# one or more repos
REPO=owner/name node scripts/index-deepwiki.mjs
REPO=a/b,c/d node scripts/index-deepwiki.mjs

# full 88plug marketplace set baked into the script
REPO=all node scripts/index-deepwiki.mjs

Best success rate — reuse your real Chrome profile so the captcha stays silent:

CHROME_USER_DATA_DIR="$HOME/.config/google-chrome" \
  REPO=owner/name node scripts/index-deepwiki.mjs

Environment variables

Variable	Default	Meaning
REPO	current origin	owner/name, comma-list, or all
EMAIL	notify@example.com	Notify email on the trigger (EMAIL=your@domain.com)
CHROME_USER_DATA_DIR	(empty)	Persistent Chrome profile for silent tokens
HEADLESS	off (0)	Set 1 for headless (often fails silent mint)
INDEX_TIMEOUT_MS	720000 (12 min)	Per-repo poll deadline

The helper logs HTTP status from the trigger, polls every ~15s, and exits 0 only if every requested repo reaches a completed status.

Procedure the agent follows

1. Check first. GET …/public_repo_indexing_status. If already complete → report and stop.
2. Trigger on a trusted browser (screen-mcp first, else Playwright helper with CHROME_USER_DATA_DIR when available).
3. Verify. Poll until completed (typically 2–10 min). Success means the status API says so.

If neither path is available (no screen-mcp, no local Chrome), the agent should say so and give you the one-liner — not pretend indexing happened.

Troubleshooting

Symptom	Likely cause	What to do
400 / reCAPTCHA validation failed	Missing or rejected token	Run on a real desktop browser or with CHROME_USER_DATA_DIR set to your Chrome profile
no silent token (untrusted/headless context)	Headless / datacenter / cold Chromium	Unset headless; use your profile; or use screen-mcp on the real desktop
Image challenge appears	Same as above — untrusted context	Do not solve it via the skill; switch to a trusted browser path
Status stuck on indexing / poll timeout	DeepWiki still working, or transient lag	Wait and re-check status; default poll window is 12 minutes (INDEX_TIMEOUT_MS)
Status unknown after trigger	Trigger may not have landed	Confirm POST returned success; retry once from a trusted browser
"No repo" from the helper	Not in a git repo and REPO unset	Set REPO=owner/name or run inside a clone with origin on GitHub
Playwright import error	Playwright not installed	npm i -D playwright && npx playwright install chromium
Private repo	Public API only	Out of scope — needs a Devin org account
Badge still dead after "success"	Claimed success without API verify	Re-check status API; only trust completed / indexed

Check status yourself

curl -sS "https://api.devin.ai/ada/public_repo_indexing_status?repo_name=OWNER/REPO"

Expect JSON with a status field. Re-run the helper only when it is not already complete.

Close Chrome before using the profile

If Playwright opens your user-data dir while Chrome is already running, profile locks can fail the launch. Quit Chrome first, or use a copy of the profile, or prefer the screen-mcp path against the already-open browser.

Development

python3 .ci/validate_plugin.py .
bash tests/smoke.sh
# docs
pip install mkdocs mkdocs-material
mkdocs build --strict

Limits (honest)

• Public repos only.
• One-time bootstrap per repo, not a per-commit pipeline.
• Trusted browser required for the reCAPTCHA token.
• No captcha-solving services and no CI-only path.
• Does not host or replace DeepWiki — it only submits your public repo for indexing and waits until the public status API reports complete.

License

FSL-1.1-ALv2. See the changelog.