docs-lookup

Locate relevant entries in .carta/MANIFEST.md and read referenced docs.

1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/saxonthune/carta --skill docs-lookup-saxonthune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-lookup
Source: https://github.com/saxonthune/carta/tree/main/.claude/skills/docs-lookup
Command: npx skills add https://github.com/saxonthune/carta --skill docs-lookup-saxonthune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly find authoritative answers about Carta and its .carta/ workspace docs, without manually browsing or guessing which documentation files to read.

Core Features & Use Cases

  • Manifest-first navigation: Uses .carta/MANIFEST.md to identify the smallest set of relevant doc files before reading anything.
  • Targeted cross-topic lookup: Answers questions about specific doc refs like docXX.YY, .carta/ contents, and higher-level design/architecture principles.
  • Reference-grounded responses: Produces answers that cite the exact doc ref(s) that support the claims, improving traceability and correctness.

Quick Start

Ask an AI question like: What does .carta/ say about doc01.02, and how does it relate to Carta's architecture?

Frequently Asked Questions about docs-lookup

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

FAQPage Schema
How do I look up specific documentation references in a .carta workspace?

To look up .carta documentation, the tool reads the .carta/MANIFEST.md file to locate the smallest set of relevant docs, reads only those referenced files, and answers your question with exact doc citations.

Can I find answers about Carta architecture and design principles without reading every file?

Yes, manifest-first navigation identifies the minimal set of relevant documentation files in .carta/ before reading anything, ensuring targeted answers about Carta architecture and design principles without manual browsing.

What is the best way to answer questions about specific docXX.YY references?

The best way to answer docXX.YY reference questions is using manifest-first lookup, which locates the specific entries in .carta/MANIFEST.md, reads only the targeted documentation, and provides reference-grounded responses with citations.

Does the documentation lookup process modify the original workspace files?

No, the documentation lookup process operates with strict read-only behavior, meaning it locates references in .carta/MANIFEST.md and reads docs without modifying or altering the original documentation files.

Why does my documentation lookup require checking the manifest first?

Checking the manifest first ensures minimal doc reads by identifying the smallest set of relevant files in .carta/MANIFEST.md before accessing content, which improves lookup speed and maintains strict reference grounding.

When do I need to use manifest navigation for documentation grounding?

You need manifest navigation for documentation grounding when querying .carta/ contents, resolving docXX.YY references, or asking higher-level questions about Carta features, architecture, and principles that require traceable citations.