aosp-part-appendices

Look up AOSP key-file paths and glossary terms from Markdown appendices.

122|30|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-appendices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aosp-part-appendices
Source: https://github.com/aospbooks/aosp-internal-book/tree/main/agents/claude/skills/aosp-part-appendices
Command: npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-appendices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AOSP appendices provide fast access to the most important reference material for subsystems and acronyms, reducing the time spent hunting through the tree.

Core Features & Use Cases

  • Quick lookup of key-file paths for subsystem areas (build, init, kernel, HAL, etc.)
  • Access to authoritative glossary definitions for AOSP terms (Treble, VINTF, APEX, HIDL, etc.)
  • Use Case: When you need a precise file path or definition for documentation or debugging.

Quick Start

Load the AOSP appendices skill and ask for a key file path from A-appendix-key-files.md or a glossary term from B-appendix-glossary.md.

Frequently Asked Questions about aosp-part-appendices

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

FAQPage Schema
How do I find key file paths for AOSP subsystems like Build, Boot, Kernel, and HAL?

To find AOSP key file paths for subsystems like Build, Boot, Kernel, and HAL, load this skill and query the A-appendix-key-files.md reference. It surfaces precise file paths to reduce time spent hunting through the AOSP source tree.

What does the AOSP glossary term Treble or VINTF actually mean?

The AOSP glossary defines terms like Treble, VINTF, APEX, and HIDL by providing authoritative definitions from B-appendix-glossary.md. You can retrieve these precise definitions quickly by asking the skill for a specific acronym.

Can I use this reference to look up file paths for debugging AOSP system services?

Yes, you can look up file paths for debugging AOSP system services. The reference covers key-file paths across build, init, kernel, HAL, and system services, delivering precise lookups needed for documentation or debugging.

What is the best way to quickly reference AOSP acronyms without reading full documentation?

The best way to quickly reference AOSP acronyms is by querying the glossary appendix. It provides fast access to authoritative definitions for terms like Treble, VINTF, APEX, and HIDL directly from its markdown reference files.

Do I need any dependencies to access the AOSP appendices reference?

No dependencies are required to access the AOSP appendices reference. The skill operates independently by relying on two internal markdown files to deliver precise file path lookups and glossary term definitions.

When should I not use the appendices for AOSP source navigation?

You should not use the appendices for deep AOSP source navigation or implementation logic, as it only provides quick reference lookups for file paths and glossary terms rather than detailed subsystem analysis.