agentdocs

Browse Agent Kit documentation from the terminal with keyword search and section jumps.

2|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/lucidlabs-hq/agent-kit --skill agentdocs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentdocs
Source: https://github.com/lucidlabs-hq/agent-kit/tree/main/.claude/skills/agentdocs
Command: npx skills add https://github.com/lucidlabs-hq/agent-kit --skill agentdocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browse Agent Kit documentation directly in the terminal, reducing context switching and speeding up onboarding for developers and operators.

Core Features & Use Cases

  • Terminal-based navigation to sections such as overview, architecture, aidd, piv, and references.
  • In-terminal search across docs to locate topics quickly.
  • Direct section jumps and menu-based overview for fast orientation.

Quick Start

Run the /agentdocs command to display the documentation overview and begin exploring sections.

Frequently Asked Questions about agentdocs

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

FAQPage Schema
How do I browse Agent Kit documentation without leaving the terminal?

You can browse Agent Kit documentation in the terminal by running the /agentdocs command, which displays an overview menu. It relies on YAML frontmatter metadata and ASCII UI rendering to present architecture, workflows, and references.

Can I search for specific keywords across Agent Kit docs in the terminal?

Yes, you can perform in-terminal keyword searches across the documentation to locate topics quickly. This allows developers and operators to find specific information without manually scrolling through sections.

How do I jump directly to specific sections like architecture or references in Agent Kit?

You can jump directly to sections such as overview, architecture, aidd, piv, and references using the menu-based overview. This provides fast orientation and quick access to specific documentation areas.

Does terminal-based documentation navigation require any external dependencies?

No external dependencies are required for terminal-based documentation navigation. The system operates independently by loading content from doc sections and parsing YAML frontmatter metadata directly within your environment.

Why use a terminal documentation browser instead of web-based docs for Agent Kit?

Using a terminal documentation browser reduces context switching and speeds up onboarding for developers and operators. It provides quick access to architecture and workflows without leaving your development environment.