gemini-skill-creator
Automates the creation of structured, high-quality agent skill directories based on user requirements.
Install
mkdir -p .claude/skills/gemini-skill-creator && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9704" && unzip -o skill.zip -d .claude/skills/gemini-skill-creator && rm skill.zipInstalls to .claude/skills/gemini-skill-creator
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Generates high-quality, predictable, and efficient .agent/skills/ directories based on user requirements. Use when the user asks to create a new skill or "habilidad".Key capabilities
- →Folder structure generation
- →Standardized YAML frontmatter creation
- →Boilerplate code generation
- →Workflow validation loop setup
How it works
It generates a standardized directory hierarchy and SKILL.md file based on strict structural and writing standards.
Inputs & outputs
When to use gemini-skill-creator
- →Creating new AI agent skills
- →Standardizing skill project structure
- →Generating boilerplate for custom agents
About this skill
Antigravity Skill Creator System Instructions
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.
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:
- 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. (e.g., "Extracts text from PDFs. Use when the user mentions document processing or PDF files.")
3. Writing Principles (The "Claude Way")
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.mdunder 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:
- Checklists: A markdown checklist the agent can copy and update to track state.
- Validation Loops: A "Plan-Validate-Execute" pattern. (e.g., Run a script to check a config file BEFORE applying changes).
- Error Handling: Instructions for scripts should be "black boxes"—tell the agent to run
--helpif 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]
---
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
- Copy the content above into a new file named
antigravity-skill-creator.md. - Upload this file to your AI agent or paste it into the system prompt area.
- 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']."*
Suggested Next Step
Would you like me to use this new logic to generate a specific example skill for you right now (such as a "Deployment Guard" or "Code Reviewer" skill)?
When not to use it
- →Creating non-agent-based skills
- →Manual directory creation
Limitations
- →Requires adherence to defined YAML standards
- →Limited to the Antigravity agent environment
How it compares
It enforces a predictable, high-quality structure for agent skills instead of manual scaffolding.
Compared to similar skills
gemini-skill-creator side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gemini-skill-creator (this skill) | 0 | 5mo | No flags | Beginner |
| opencode-cli | 14 | 7mo | Review | Advanced |
| claude-automation-recommender | 47 | 2mo | Review | Beginner |
| mcp-integration | 21 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
opencode-cli
SpillwaveSolutions
This skill should be used when configuring or using the OpenCode CLI for headless LLM automation. Use when the user asks to "configure opencode", "use opencode cli", "set up opencode", "opencode run command", "opencode model selection", "opencode providers", "opencode vertex ai", "opencode mcp servers", "opencode ollama", "opencode local models", "opencode deepseek", "opencode kimi", "opencode mistral", "fallback cli tool", or "headless llm cli". Covers command syntax, provider configuration, Vertex AI setup, MCP servers, local models, cloud providers, and subprocess integration patterns.
claude-automation-recommender
anthropics
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
hook-development
anthropics
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
swarm-advanced
ruvnet
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows