android / android/skills

Antigravity 2.0.x Unable to Reference Android CLI Skills

Open
#47 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
7.3k
Forks
476
Avg merge
8h 59m
Merged PRs (30d)
7

Description

### Affected Skill

All Android CLI Skills

### Description

After updating to Antigravity 2.0.x, I am no longer able to reference Android CLI skills in prompts, even after running `android skills add --all` or `android init`.

This was working correctly in previous versions.

### Expected Behavior

After running `android skills add --all` or `android init`, the installed Android CLI skills should be available and referenceable within Antigravity prompts.

### Actual Behavior

Even after successfully running `android init` and `android skills add --all`, none of the Android CLI skills can be referenced or detected in Antigravity 2.0.x prompts.

### Steps to Reproduce

1. Install or update Antigravity to version 2.0.x (tested on 2.0.3).
2. Install Android CLI (if not already installed).
3. Run:

```bash
android init
```

or

```bash
android skills add --all
```
4. Try referencing any Android CLI skill in an Antigravity prompt.
5. Observe that the skills are not recognized or available.

### Suggested Fix

Possibly related to a regression in skill registration, indexing, or prompt integration introduced in Antigravity 2.0.x.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with Antigravity 2.0.3 using `android init` and `android skills add --all`, then trace the Android CLI skill registration, indexing, and prompt integration entry points. Done means installed Android CLI skills are detected and referenceable in Antigravity prompts after either command.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.