rdk-docs-reference

Search official D-Robotics documentation repositories and answer RDK questions with sourced citations.

3|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/D-Robotics/rdk-skills --skill rdk-docs-reference-d-robotics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rdk-docs-reference
Source: https://github.com/D-Robotics/rdk-skills/tree/main/plugins/d-robotics-skills/skills/rdk-docs-reference
Command: npx skills add https://github.com/D-Robotics/rdk-skills --skill rdk-docs-reference-d-robotics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? AI agents often answer RDK hardware and software questions from memory, producing unverifiable or outdated claims. This Skill forces every answer about D-Robotics RDK boards to be grounded in the official documentation repositories (rdk_x_doc, rdk_s_doc, tros_doc) with explicit file-and-line citations. ## Core Features & Use Cases - Full-text documentation search: The search_docs.sh script performs keyword search across the official doc repos with multi-keyword intersection, per-repo scoping (X series, S series, TROS), hit limits, chapter-level summaries, and a table-of-contents mode for capability-based discovery. - Structured search methodology: Built-in protocols for repo scoping, chapter applicability signals, artifact-to-capability keyword fallback, negative-fact dual evidence, and per-board cross-comparison prevent extrapolating one board's docs to another. - Citation-first answers: Every response must quote the original documentation text and include the source path, and must honestly report when the official docs do not cover a topic instead of fabricating values. - Use Case: A user asks "What resolutions does the X5 HDMI support?" or "Why doesn't the can0 approach from the X5 tutorial work on S100?" The Skill searches the scoped doc repo, reads the matching sections, and replies with quoted passages plus paths like rdk_x_doc/docs/03_Basic_Application/01_40pin_user_sample/40pin_define.md. ## Quick Start Ask the agent to look up the official documentation for your RDK question, for example: "Check the official docs for the RDK X5 40-pin GPIO pin definitions and quote the source."

Frequently Asked Questions about rdk-docs-reference

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

FAQPage Schema
How do I search D-Robotics RDK official documentation from an AI agent?▼

Run the search_docs.sh script with one or more --query keywords against the local clones of rdk_x_doc, rdk_s_doc, and tros_doc. It returns file:line:matched-line results, and you then read the top matching files and answer with quoted citations.

How do I find RDK X5 40-pin GPIO pin definitions in the docs?▼

Search with --query 40PIN scoped to the X repo, which leads to 40pin_define.md under 03_Basic_Application. Quote the relevant passage and include the source path in the answer rather than relying on memory.

Can I search only the S100 or S600 documentation instead of all boards?▼

Yes, use --repo s to restrict search to rdk_s_doc, --repo x for the X series, --repo tros for TROS docs, or --repo all for everything. Repo scoping prevents answering one board's question with another board's documentation.

What happens when the official RDK docs do not cover a topic?▼

The Skill reports that the official documentation does not cover the topic and may retry once with broader keywords or --repo all. It explicitly refuses to fabricate values or parameters that are absent from the docs.

Why does the search script report docs-not-found?▼

The script requires local clones of rdk_x_doc, rdk_s_doc, and tros_doc under the .refs directory or the path set by RDK_DOCS_ROOT. If missing, it prints the git clone commands needed to fetch them and exits.

When should I not use documentation search for an RDK question?▼

Do not use it as a substitute for live device measurement. Questions about current device state, such as actual memory usage, should be routed to workflow skills like rdk-diagnostic or rdk-memory-audit instead of quoting documentation theory.