skill-creator

Scaffold Agent Skills with SKILL.md metadata and package them as .skill files.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/Dianshu-Liao/SkilLGuard --skill skill-creator-dianshu-liao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/Dianshu-Liao/SkilLGuard/tree/main/data/skills/skill-creator
Command: npx skills add https://github.com/Dianshu-Liao/SkilLGuard --skill skill-creator-dianshu-liao

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Skill Creator helps you author and package effective Agent Skills by turning vague goals into a clear SKILL.md description and a maintainable skill structure.

Core Features & Use Cases

  • Skill authoring guidance: Produces a usable SKILL.md layout with correct YAML frontmatter, concise instructions, and progressive disclosure.
  • Resource planning: Helps decide what belongs in scripts/, references/, and assets/ so the skill stays token-efficient and organized.
  • Packaging & iteration workflow: Guides the process of initializing, validating, packaging into a .skill file, installing, and improving based on real usage (including required user steps after install).

Quick Start

Run the initializer to scaffold a new skill directory, then edit the generated SKILL.md frontmatter (name and single-line description) and body instructions to match your exact trigger scenarios.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I package an Agent Skill for Gemini CLI?

Structuring an Agent Skill requires correct YAML frontmatter, hyphen-case naming, and a progressive-disclosure body that includes only essentials while using bundled scripts and references on demand.

What is the best way to structure a SKILL.md file for reliable triggering?

Structuring an Agent Skill requires correct YAML frontmatter, hyphen-case naming, and a progressive-disclosure body that includes only essentials while using bundled scripts and references on demand.

How do I organize scripts and references to keep my skill token-efficient?

Keep your skill token-efficient by planning resources carefully: place executable logic in scripts/, reference materials in references/, and load bundled assets on demand instead of embedding everything in the main body.

Can I validate a skill package before installing it in Gemini CLI?

Yes, you can validate a skill package before installation by checking it against skill requirements to ensure the SKILL.md layout, frontmatter, and directory structure meet the expected standards.

What do I need to do after installing a .skill package in Gemini CLI?

After installing a .skill package in Gemini CLI, you must complete required user steps to reload the skill, then iterate and improve its instructions based on real usage and triggering performance.