agentsclimarketplace

Android docs search

Skill tamtom/android-docs-claude-plugin/skills/android-docs-search

Search Android/Kotlin documentation offline using SQLite index for API lookups and Grep for content search. Use when the user asks about Android APIs, Compose components, AndroidX classes, Kotlin extensions, or needs to find documentation for Android development.From its SKILL.md

Install
npx -y skills add tamtom/android-docs-claude-plugin --skill android-docs-search

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.8 KB, 839 tokens by cl100k_base, as published. Nobody here has run it

Android Docs Search

Overview

Search the local Android/Kotlin documentation. The documentation must be installed separately (see plugin README).

Default location: ~/StudioProjects/android-docs-claude-plugin/docs/

Two search methods available:

  • SQLite index - Fast API name lookups (189,506+ indexed entries)
  • Grep/Read - Full-text search in HTML documentation content

When to Use Each Method

MethodUse For
SQLiteFinding classes, functions, properties by name
GrepSearching documentation content, deprecation notices, examples

SQLite Index Search

Database location: ~/StudioProjects/android-docs-claude-plugin/docs/android_api_index.db

Table Schema

CREATE TABLE api_index(id INTEGER PRIMARY KEY, name TEXT, type TEXT, path TEXT);

Entry Types

Class, Constructor, Property, Package, Annotation, Function, Enum, Constant, Object, Interface, Method

Search Examples

# Find by exact name
sqlite3 ~/StudioProjects/android-docs-claude-plugin/docs/android_api_index.db \
  "SELECT name, type, path FROM api_index WHERE name LIKE '%LazyColumn%';"

# Filter by type
sqlite3 ~/StudioProjects/android-docs-claude-plugin/docs/android_api_index.db \
  "SELECT name, type FROM api_index WHERE name LIKE '%Modifier%' AND type='Class';"

# Find all entries in a package
sqlite3 ~/StudioProjects/android-docs-claude-plugin/docs/android_api_index.db \
  "SELECT name, type FROM api_index WHERE name LIKE 'androidx.compose.material3%';"

Content Search (Grep)

Documentation location: ~/StudioProjects/android-docs-claude-plugin/docs/Documents/developer.android.com/

Search Examples

Use the Grep tool to search HTML files:

pattern: "deprecated"
path: ~/StudioProjects/android-docs-claude-plugin/docs/Documents/
glob: "*.html"

Or get context around a match:

pattern: "LocalAutofillTree"
path: <file_path_from_sqlite>
output_mode: "content"
-A: 10
-B: 2

Recommended Workflow

  1. Start with SQLite to find the API and its file path
  2. Use Grep/Read to examine the actual documentation content

Example: Find deprecation info for an API

# Step 1: Find the file
sqlite3 ~/StudioProjects/android-docs-claude-plugin/docs/android_api_index.db \
  "SELECT name, path FROM api_index WHERE name LIKE '%LocalAutofillTree%';"

# Step 2: Read the deprecation notice from the file using Read or Grep tool

Documentation Structure

~/StudioProjects/android-docs-claude-plugin/
├── docs/
│   ├── android_api_index.db      # SQLite index (189,506+ entries)
│   └── Documents/
│       └── developer.android.com/
│           └── reference/
│               ├── android/      # Java Android APIs
│               └── kotlin/       # Kotlin Android APIs
│                   └── androidx/ # AndroidX libraries
├── scripts/
│   ├── bulk_updater.py           # Sync new pages from developer.android.com
│   ├── download_and_process.py   # Download single pages
│   └── update_index.py           # Manage SQLite index
└── skills/
    └── android-docs-search/
        └── SKILL.md

Keeping Docs Updated

Run from the docs/ directory:

# Check for new pages
python3 ../scripts/bulk_updater.py discover
python3 ../scripts/bulk_updater.py diff

# Download new pages
python3 ../scripts/bulk_updater.py sync

# Rebuild search index
python3 ../scripts/update_index.py rebuild

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most docs writing skills give in 839 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07

  • Announce the skill at startin 54 of 1637, across 26 files
  • Convert legacy doc files before editingin 45 of 1637, across 7 files
  • Predict questions readers might askin 42 of 1637, across 4 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test the document with a fresh context-less instancein 42 of 1637, across 3 files
  • Include exact file paths in every taskin 42 of 1637, across 15 files
  • Ask interview questions one at a timein 42 of 1637, across 27 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 2 files

Said here and by no other author read

  • Use SQLite for fast API name lookups
  • Use Grep for full-text documentation searches
  • Start with SQLite to find an API and its path
  • Examine the actual documentation content using Grep or Read
  • Filter SQLite queries by entry type
  • Search SQLite for entries matching a package prefix

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,512. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.