skill-creator

Create and maintain Kimi skills with structured SKILL.md frontmatter and bundled resources.

72|18|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/MoonshotAI/kimi-agent-rs --skill skill-creator-moonshotai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/MoonshotAI/kimi-agent-rs/tree/main/kimi-agent/src/skills/skill-creator
Command: npx skills add https://github.com/MoonshotAI/kimi-agent-rs --skill skill-creator-moonshotai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework and best practices for designing, documenting, and packaging Kimi Skills, enabling teams to create modular, reusable AI capabilities with consistent metadata and resources.

Core Features & Use Cases

  • Establish SKILL.md frontmatter with name and description to determine triggering and scope.
  • Organize optional resources into scripts/, references/, and assets/ to support deterministic tasks, rich references, and output assets.
  • Apply progressive disclosure patterns to keep SKILL.md concise while routing deeper details to references or scripts for advanced users.
  • Use cases include creating a new skill, updating an existing skill, or documenting standardized workflows for teams.

Quick Start

  • Create a new skill directory named after the skill (e.g., skill-creator).
  • Add SKILL.md with proper YAML frontmatter (name and description) and Markdown body with procedural guidance.
  • Optionally add scripts/, references/, and assets/ as needed.
  • Validate structure and package into a .skill archive when ready.

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 Kimi skill with frontmatter and bundled resources?

To structure a Kimi skill, create a directory with a SKILL.md file containing YAML frontmatter for name and description, then optionally organize bundled resources into scripts/, references/, and assets/ folders for deterministic tasks and output assets.

What is progressive disclosure in skill creation and when should I use it?

Progressive disclosure in skill creation keeps SKILL.md concise by routing deeper procedural details to bundled references or scripts, used when providing reusable instructions across complex tasks without overwhelming the main file.

Do I need external tools to create and maintain documentation for Kimi skills?

No external tools are needed to create Kimi skills; the process requires only standard text editing and file organization to manage SKILL.md, frontmatter, and bundled resource directories effectively.

What's the best way to package and validate a skill archive for team workflows?

The best way to package a skill is to validate its directory structure and frontmatter, then compress the organized folder containing SKILL.md and bundled resources into a .skill archive for team distribution.

How does frontmatter determine the triggering and scope of a custom workflow template?

Frontmatter determines triggering and scope by establishing the skill's name and description metadata, which defines when the skill activates and the boundaries of its execution context within workflows.

When should I not use separate resource directories for my skill assets?

You should not use separate resource directories when your skill requires no deterministic scripts, rich references, or output assets, keeping all procedural guidance directly within SKILL.md instead.