antigravity-skills-manager
Skill1 starsChanged 25 days agoMITView on GitHub
Searches, installs, updates, and lists skills from the Antigravity Skill Vault. Use when choosing or managing workspace or global skills through the npm CLI.
In this repository31 other files it gives its agents.
- skills/react-best-practices/AGENTS.mdAGENTS.md
- antigravity-skills-managerSkill
- api-design-principlesSkill
- auth-implementation-patternsSkill
- claude-apiSkill
- code-simplificationSkill
- context-optimizationSkill
- debugging-and-error-recoverySkill
- deployment-engineerSkill
- docxSkill
- doubt-driven-developmentSkill
- excalidraw-studioSkill
- frontend-designSkill
- gh-fix-ciSkill
- git-workflowSkill
- interview-meSkill
- mcp-builderSkill
- not-your-babysitterSkill
- pdfSkill
- pptxSkill
- react-best-practicesSkill
- security-auditSkill
- shadcnSkill
- source-driven-developmentSkill
- tactical-dddSkill
- the-foolSkill
- token-optimizerSkill
- unit-testing-test-generateSkill
- webapp-testingSkill
- web-artifacts-builderSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Use the npm CLI commands below.
- Distinctive: line 25
Search when the user has described a need without selecting a skill.
- Very specific: line 26
Check the resolved destination with doctor and list existing skills before replacing them.
- Distinctive: line 72
Keep the destination separate from the package's source skills.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Antigravity Skills Manager
Manage selected skills from @rmyndharis/antigravity-skills using Node.js and npm. This skill can be invoked as /antigravity-skills-manager, followed by a request such as search flutter.
Use this skill when
- Finding skills for a specific language, framework, or workflow.
- Installing a requested skill or curated bundle into a workspace or global directory.
- Listing installed skills or updating an existing installation.
Do not use this skill when
- Performing the development task described by another skill.
- Configuring unrelated plugins, model providers, or user credentials.
Instructions
- Identify the requested operation and installation scope. Run workspace commands from the intended project directory, not from this plugin's directory.
- Use the npm CLI commands below. Node.js and npm must be available;
npxmay download the package when it is not cached. - Search when the user has described a need without selecting a skill. Show relevant IDs and descriptions so the user can choose. An explicitly requested skill or bundle already establishes the selection.
- Check the resolved destination with
doctorand list existing skills before replacing them. ApplyAG_SKILLS_DIRconsistently to discovery of installed skills, installation, and updates. - Report the command's actual installed, updated, skipped, and failed counts and the destination path. Do not report success after a nonzero exit status.
Commands
List or search the catalog:
npx @rmyndharis/antigravity-skills list
npx @rmyndharis/antigravity-skills search flutterInstall a selected skill or bundle into the current workspace:
npx @rmyndharis/antigravity-skills install flutter-expert
npx @rmyndharis/antigravity-skills install --bundle core-devInspect or update installed skills:
npx @rmyndharis/antigravity-skills doctor
npx @rmyndharis/antigravity-skills installed
npx @rmyndharis/antigravity-skills update flutter-expertinstall skips an existing directory. install --force and update replace the entire selected skill directory, including local edits and files removed upstream. update without a skill name updates all recognized installed skills. Use replacement only when the user has authorized it.
Installation scope
- The default workspace destination is
<current-directory>/.agent/skills/. Antigravity also supports.agents/skills/; setAG_SKILLS_DIRto select it explicitly. --globalselects~/.gemini/antigravity/skills/, the legacy global location supported by the standalone Antigravity IDE. Use the same flag withinstalledandupdatefor that scope.AG_SKILLS_DIRoverrides both workspace and global destinations. A leading~is expanded. Antigravity CLI uses~/.gemini/antigravity-cli/skills/; the app and current IDE use~/.gemini/config/skills/.
For example, install and inspect a global skill for Antigravity CLI:
AG_SKILLS_DIR="$HOME/.gemini/antigravity-cli/skills" npx @rmyndharis/antigravity-skills install flutter-expert
AG_SKILLS_DIR="$HOME/.gemini/antigravity-cli/skills" npx @rmyndharis/antigravity-skills installedSafety
- Install only skills or bundles requested by the user. Prefer a small relevant selection;
install --allloads unnecessary metadata and can cause unrelated activation. - Explain that replacement discards local edits before proceeding unless the user has already authorized that replacement. An ordinary install preserves existing directories by skipping them.
- Keep the destination separate from the package's source skills. File or symlink destinations and source overlap are rejected.
- Failed copies leave the previous installation intact. If activation or restoration fails, follow the reported recovery path and preserve any backup. Remove a stale installation lock only after verifying that no installer is running.
- The plugin contains this skill's instructions only. Use the npm commands above; do not assume that
skills_cli.pyor another executable is beside this file.
See the official skill locations and plugin documentation when selecting the host-specific scope.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

