skill-creator

Create, validate, and package Gemini CLI skills with initialization and packaging scripts.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/bkrsna/gemini-cli --skill skill-creator-bkrsna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/bkrsna/gemini-cli/tree/main/packages/core/src/skills/builtin/skill-creator
Command: npx skills add https://github.com/bkrsna/gemini-cli --skill skill-creator-bkrsna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Building a new Gemini CLI skill from scratch requires knowing the SKILL.md frontmatter format, directory conventions, naming rules, and packaging steps. This Skill guides the entire lifecycle so new skills are valid, discoverable, and distributable without trial and error. ## Core Features & Use Cases - Skill Scaffolding: Run init_skill.cjs to generate a complete skill template with SKILL.md frontmatter and example scripts, references, and assets directories. - Validation and Packaging: Use package_skill.cjs to validate frontmatter, naming, and TODO placeholders, then produce a distributable .skill file. - Design Guidance: Apply progressive disclosure principles, degrees-of-freedom guidance, and workflow/output reference patterns to write concise, effective SKILL.md instructions. - Use Case: A user wants Gemini CLI to handle rotating PDFs repeatedly. This Skill walks through understanding examples, planning a rotate script, initializing the pdf-editor skill, editing SKILL.md, packaging it, and installing it with gemini skills install. ## Quick Start Create a new skill named pdf-editor in my workspace and package it into an installable .skill file.

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 new Gemini CLI skill?

Run node init_skill.cjs <skill-name> --path <output-directory> to scaffold a skill directory with a SKILL.md template and example scripts, references, and assets folders. Then edit SKILL.md with proper frontmatter and instructions, and package it with package_skill.cjs.

What is the required structure of a SKILL.md file?

SKILL.md must contain YAML frontmatter with a hyphen-case name and a single-line description under 1024 characters, followed by Markdown instructions. The description drives triggering, so it must state what the skill does and when to use it.

How do I package and install a skill in Gemini CLI?

Run node package_skill.cjs <path/to/skill-folder> to validate and create a .skill file, which is a zip archive. Then install it with gemini skills install <file.skill> --scope workspace or --scope user, and run /skills reload in an interactive session.

Why does skill packaging fail validation?

Validation fails when SKILL.md is missing, frontmatter lacks name or description, the name is not hyphen-case, the description spans multiple lines or exceeds 1024 characters, or unresolved TODO placeholders remain in any file.

When should a skill include scripts versus references?

Use scripts for deterministic, repeatedly rewritten tasks like file conversion, since they execute without loading into context. Use references for detailed documentation such as schemas or API specs that Gemini CLI reads only when needed, keeping SKILL.md lean.