skill-creator

Design and package Gemini CLI skill files with SKILL.md metadata.

2|2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/patronus-ai/skill-inject --skill skill-creator-patronus-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/patronus-ai/skill-inject/tree/main/data/skills/skill-creator
Command: npx skills add https://github.com/patronus-ai/skill-inject --skill skill-creator-patronus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Skill-creator helps users design high-quality Gemini CLI skill files by providing a clear, token-efficient framework for writing SKILL.md, structuring optional resources, and packaging skills correctly.

Core Features & Use Cases

  • Concise, trigger-focused design guidance: Reduce context bloat by keeping SKILL.md lean and ensuring frontmatter metadata is accurate.
  • Resource-structuring best practices: Decide what belongs in SKILL.md versus scripts/, references/, and assets/ to support scalable, maintainable skills.
  • Progressive disclosure patterns: Use metadata-first loading and conditional references so Gemini CLI reads only what is necessary.
  • End-to-end creation workflow: Walk through the full process from understanding the skill to initializing, editing, packaging, and iterating.

Quick Start

Use the skill-creator guidance to structure a new skill directory by writing a correct SKILL.md frontmatter with a single-line name and description, then implementing the minimum procedural instructions in the Markdown body while moving detailed material into references or scripts as needed.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Gemini CLI skill file to avoid context bloat?

To structure a Gemini CLI skill file and avoid context bloat, keep SKILL.md lean with accurate YAML frontmatter and move detailed material into references or scripts for token-efficient progressive disclosure.

What is the best way to organize scripts and references when authoring agent instructions?

Organizing scripts and references involves deciding what belongs in SKILL.md versus scripts/ and references/ directories, ensuring scalable and maintainable agent instructions through metadata-first loading and conditional references.

How does progressive disclosure work in Gemini CLI skill packaging?

Progressive disclosure in Gemini CLI skill packaging works by using metadata-first loading and conditional references, ensuring the agent reads only necessary files to maintain token efficiency.

Do I need YAML frontmatter to create a valid SKILL.md file?

Yes, you need YAML frontmatter to create a valid SKILL.md file, specifically requiring a name and a single-line description to pass repository initialization and packaging validation.

What should go directly in SKILL.md versus optional assets for a Gemini CLI skill?

SKILL.md should contain concise, trigger-focused design guidance and minimum procedural instructions, while optional assets, detailed references, and scripts should hold the heavier material to reduce context bloat.