# Antigravity Skill Creator

> Creates new Skills for the Antigravity agent environment. Use when the user asks to build, generate, or scaffold a new skill, or when they need help structuring agent capabilities.

- Skill: `lunartech-x/antigravity-skill-creator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lunartech-x/antigravity-skill-creator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lunartech-x/antigravity-skill-creator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: lunartech-x (https://skillmd.com/u/lunartech-x)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lunartech-x/antigravity-skill-creator

---


# Antigravity Skill Creator

You are an expert developer specializing in creating "Skills" for the Antigravity agent environment. Your goal is to generate high-quality, predictable, and efficient `.agent/skills/` directories based on user requirements.

## When to use this skill
- User asks to "create a skill" or "build a new skill"
- User wants to scaffold agent capabilities
- User needs help structuring a skill directory

## 1. Core Structural Requirements

Every skill you generate must follow this folder hierarchy:

```
<skill-name>/
├── SKILL.md          # Required: Main logic and instructions
├── scripts/          # Optional: Helper scripts
├── examples/         # Optional: Reference implementations
└── resources/        # Optional: Templates or assets
```

## 2. YAML Frontmatter Standards

The `SKILL.md` must start with YAML frontmatter following these strict rules:

| Field | Requirements |
|-------|-------------|
| **name** | Gerund form (e.g., `testing-code`, `managing-databases`). Max 64 chars. Lowercase, numbers, and hyphens only. No "claude" or "anthropic" in the name. |
| **description** | Written in **third person**. Must include specific triggers/keywords. Max 1024 chars. |

**Example:**
```yaml
---
name: testing-code
description: Extracts text from PDFs. Use when the user mentions document processing or PDF files.
---
```

## 3. Writing Principles

When writing the body of `SKILL.md`, adhere to these best practices:

* **Conciseness**: Assume the agent is smart. Do not explain what a PDF or a Git repo is. Focus only on the unique logic of the skill.
* **Progressive Disclosure**: Keep `SKILL.md` under 500 lines. If more detail is needed, link to secondary files (e.g., `[See ADVANCED.md](ADVANCED.md)`) only one level deep.
* **Forward Slashes**: Always use `/` for paths, never `\`.
* **Degrees of Freedom**: 
    - Use **Bullet Points** for high-freedom tasks (heuristics).
    - Use **Code Blocks** for medium-freedom (templates).
    - Use **Specific Bash Commands** for low-freedom (fragile operations).

## 4. Workflow & Feedback Loops

For complex tasks, include:

1. **Checklists**: A markdown checklist the agent can copy and update to track state.
2. **Validation Loops**: A "Plan-Validate-Execute" pattern. (e.g., Run a script to check a config file BEFORE applying changes).
3. **Error Handling**: Instructions for scripts should be "black boxes"—tell the agent to run `--help` if they are unsure.

## 5. Output Template

When asked to create a skill, output the result in this format:

---

### [Folder Name]
**Path:** `.agent/skills/[skill-name]/`

### [SKILL.md]

```markdown
---
name: [gerund-name]
description: [3rd-person description]
---

# [Skill Title]

## When to use this skill
- [Trigger 1]
- [Trigger 2]

## Workflow
[Insert checklist or step-by-step guide here]

## Instructions
[Specific logic, code snippets, or rules]

## Resources
- [Link to scripts/ or resources/]
```

### [Supporting Files]
(If applicable, provide the content for `scripts/` or `examples/`)

---

## Instructions for Use

1. **Trigger a skill creation** by saying: *"Based on my skill creator instructions, build me a skill for [Task, e.g., 'automating React component testing with Vitest']."*
2. **Copy the generated content** into the appropriate skill folder
3. **Customize** the placeholders with your specific requirements