karpathy-wiki-read

Evaluate wiki coverage and cite sources using a 6-step orientation ladder.

98|24|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/toolboxmd/karpathy-wiki --skill karpathy-wiki-read
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karpathy-wiki-read
Source: https://github.com/toolboxmd/karpathy-wiki/tree/main/skills/karpathy-wiki-read
Command: npx skills add https://github.com/toolboxmd/karpathy-wiki --skill karpathy-wiki-read

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines a deterministic 6-step orientation ladder to determine wiki coverage for a question, when to inline-read vs spawn an Explore subagent vs fall through to web search, and the cite contract every wiki-grounded answer must satisfy.

Core Features & Use Cases

  • Deterministic 6-step orientation process for evaluating whether the wiki covers the user question.
  • Branches to inline reading, Explore subagent, or web search based on signal-term matches and index signals.
  • Enforced cite contract to attach verifiable wiki sources to every answer.
  • Load-on-demand protocol used before answering any user question to ensure grounded responses.

Quick Start

Load this protocol and apply the 6-step orientation ladder before answering any user question to ensure wiki coverage and proper citations.

Frequently Asked Questions about karpathy-wiki-read

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a citation contract for wiki-grounded answers?

A citation contract for wiki-grounded answers is enforced by applying a deterministic 6-step orientation ladder that attaches verifiable wiki sources to every response before delivery.

What is the best way to determine if a wiki covers a user question before answering?

The best way to determine wiki coverage is using a deterministic 6-step orientation ladder that evaluates signal-term matches and index signals to decide whether to inline-read, spawn an Explore subagent, or fall through to web search.

How does an orientation ladder decide between inline reading and spawning an Explore subagent?

The orientation ladder decides between inline reading and spawning an Explore subagent by evaluating signal-term matches and index signals. It routes the query through the appropriate read-path to produce a grounded response.

When should I route a wiki query to web search instead of inline reading?

You should route a wiki query to web search when the 6-step orientation ladder identifies gaps in wiki coverage. The ladder evaluates signal-term matches and falls through to web search to fill missing information.

Do I need a load-on-demand protocol to prepare wiki citations?

Yes, you need a load-on-demand protocol to prepare wiki citations. It must be loaded before answering any user question to ensure the 6-step orientation ladder evaluates wiki coverage and produces grounded responses.

Can I use an Explore subagent for information retrieval when wiki coverage is insufficient?

Yes, you can use an Explore subagent for information retrieval when the orientation ladder determines wiki coverage is insufficient. The 6-step process branches to an Explore subagent or web search based on signal-term matches.