How do I install the Skill Antigravity skill?

Run npx skillmds@latest add diegosouzapw/skill-antigravity in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skill Antigravity safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skill Antigravity?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skill Antigravity free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Skill Antigravity?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skill Antigravity by diegosouzapw — Agent Skill

Name: Skill Antigravity
Rating: 4.666666666666667 (3 reviews)
Author: diegosouzapw

File contents

Antigravity Skills Master

This skill empowers Antigravity agents to extend their own capabilities through the creation and management of modular skills.

Core Principles

Modularity: Each skill should focus on a single, well-defined task or domain.
Context Efficiency: Keep instructions concise to minimize token usage while maintaining clarity.
Discoverability: Use precise, keyword-rich descriptions in the frontmatter to help the agent identify relevance.
Reliability: Provide checklists and error-handling logic for critical tasks.
Singular Naming: Always use .agent (singular), never .agents (plural), for the root configuration directory to ensure automatic tool detection.

Anatomy of a Skill

A standard Antigravity skill follows this structure:

SKILL.md: (Required) The core instruction set with YAML metadata.
metadata.json: (Recommended) Structured metadata for the skills CLI.
scripts/: (Optional) Automation scripts or helper tools.
examples/: (Optional) Reference implementations.
resources/: (Optional) Static assets, templates, or rulesets.

Guidelines for Creating Skills

Identify the Need: Create a skill when a task is repetitive, complex, or requires specialized domain knowledge.
Setup Folder: Create a directory in .agent/skills/ (local) or your skills repository.
Define Metadata: Ensure the name matches the folder name and the description is actionable.
Draft Instructions:
- Use clear sections (Goal, Requirements, Steps, Verification).
- Include GitHub-style alerts for critical warnings or tips.
- Add Mermaid diagrams for complex workflows.

Managing the Skills Ecosystem

Local Workspace: Store project-specific skills in .agent/skills/.
Global Library: Use npx skills add to import skills from shared repositories.
Versioning: Update the version in frontmatter/metadata when making significant changes.

Verification Checklist

Does the folder name match the name in SKILL.md?
Is the description clear enough for discovery?
Are all external dependencies (scripts) referenced correctly?
Has the skill been tested in a real-world scenario?

---name: skill-antigravitydescription: Provides core knowledge and instructions for creating, documenting, and managing Antigravity Skills. Use this skill when you need to extend your capabilities by creating new modular skills.license: MIT---# Antigravity Skills MasterThis skill empowers Antigravity agents to extend their own capabilities through the creation and management of modular skills.## Core Principles1. **Modularity**: Each skill should focus on a single, well-defined task or domain.2. **Context Efficiency**: Keep instructions concise to minimize token usage while maintaining clarity.3. **Discoverability**: Use precise, keyword-rich descriptions in the frontmatter to help the agent identify relevance.4. **Reliability**: Provide checklists and error-handling logic for critical tasks.5. **Singular Naming**: Always use `.agent` (singular), never `.agents` (plural), for the root configuration directory to ensure automatic tool detection.## Anatomy of a SkillA standard Antigravity skill follows this structure:- `SKILL.md`: (Required) The core instruction set with YAML metadata.- `metadata.json`: (Recommended) Structured metadata for the `skills` CLI.- `scripts/`: (Optional) Automation scripts or helper tools.- `examples/`: (Optional) Reference implementations.- `resources/`: (Optional) Static assets, templates, or rulesets.## Guidelines for Creating Skills1. **Identify the Need**: Create a skill when a task is repetitive, complex, or requires specialized domain knowledge.2. **Setup Folder**: Create a directory in `.agent/skills/` (local) or your skills repository.3. **Define Metadata**: Ensure the `name` matches the folder name and the `description` is actionable.4. **Draft Instructions**: - Use clear sections (Goal, Requirements, Steps, Verification). - Include GitHub-style alerts for critical warnings or tips. - Add Mermaid diagrams for complex workflows.## Managing the Skills Ecosystem- **Local Workspace**: Store project-specific skills in `.agent/skills/`.- **Global Library**: Use `npx skills add` to import skills from shared repositories.- **Versioning**: Update the `version` in frontmatter/metadata when making significant changes.## Verification Checklist- [ ] Does the folder name match the `name` in `SKILL.md`?- [ ] Is the `description` clear enough for discovery?- [ ] Are all external dependencies (scripts) referenced correctly?- [ ] Has the skill been tested in a real-world scenario?

Frequently asked questions

Skill Antigravity