Agent-Skills/Dev-Skills/creating-skills/SKILL.md
Generates high-quality, predictable, and efficient .agent/skills/ directories based on user requirements. Reference this at any time you are creating any other skill for Antigravity.
npx skillsauth add MaVoid-Team/Capital-Consultancy-Final creating-skillsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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)The SKILL.md must start with YAML frontmatter following these strict rules:
testing-code, managing-databases). Max 64 chars. Lowercase, numbers, and hyphens only. No "claude" or "anthropic" in the name.When writing the body of SKILL.md, adhere to these best practices:
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./ for paths, never \.For complex tasks, include:
--help if they are unsure.When asked to create a skill, output the result in this format:
Path: .agent/skills/[skill-name]/
---
name: [gerund-name]
description: [3rd-person description]
---
development
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
content-media
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.
testing
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
testing
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.