skill-creator

Create modular Gemini CLI Skills with standardized frontmatter and resource organization.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mlarkin00/mslarkin --skill skill-creator-mlarkin00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/mlarkin00/mslarkin/tree/main/skills/skill-creator
Command: npx skills add https://github.com/mlarkin00/mslarkin --skill skill-creator-mlarkin00

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Guides users in designing and packaging modular Gemini CLI Skills, enabling rapid creation of consistent, reusable skill units.

Core Features & Use Cases

  • Provides a clear frontmatter template for skill metadata (name + description)
  • Includes a scalable structure for optional resources (scripts, references, assets)
  • Offers practical guidance on naming, organization, and progressive disclosure for reliable Skill development

Quick Start

Create a new skill folder under skills/ and customize SKILL.md along with its resources to begin building a reusable Gemini CLI Skill.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I create a modular Gemini CLI skill with standardized frontmatter?

To create a modular Gemini CLI skill, define standardized frontmatter for metadata, structure the body with optional resources like scripts and assets, and follow progressive disclosure patterns for consistent deployment.

What is progressive disclosure in Gemini skill packaging?

Progressive disclosure in Gemini skill packaging is an organizational pattern that structures resources and validation to ensure safe, reliable deployment across teams by only exposing necessary complexity at each layer.

How do I structure resources like scripts and references for a Gemini CLI skill?

Structure resources for a Gemini CLI skill by placing them in a dedicated skill folder under skills/, organizing scripts, references, and assets alongside a customized SKILL.md file for scalable modular design.

Do I need dependencies to package a Gemini CLI skill for team distribution?

No dependencies are required to package a Gemini CLI skill for team distribution. You can build and deploy standardized, reusable skill units using only the provided frontmatter template and resource organization guidance.

What is the best way to validate modular skills before deployment in a Gemini ecosystem?

The best way to validate modular skills before deployment is to enforce best practices for naming, packaging, and progressive disclosure, ensuring the SKILL.md and resource structure meet the Gemini ecosystem's consistency standards.

Why does my Gemini CLI skill need a standardized naming and body structure?

A standardized naming and body structure is needed to enforce consistency and safety across teams, allowing your modular Gemini CLI skill to be reliably discovered, packaged, and distributed.