skill-file-structure

Organize Skill units with a standardized SKILL.md file structure.

31|4|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/kissrosecicd-hub/agents-evolution --skill skill-file-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-file-structure
Source: https://github.com/kissrosecicd-hub/agents-evolution/tree/main/.agents/skills/skill-file-structure
Command: npx skills add https://github.com/kissrosecicd-hub/agents-evolution --skill skill-file-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide standardizes how to structure a Skill unit to separate metadata from code and resources, reducing confusion and improving collaboration.

Core Features & Use Cases

  • Encourages a consistent layout: SKILL.md at the root, with optional scripts/, references/, and assets/ directories to house executable code and resources.
  • Prevents inline scripting in SKILL.md by moving code to dedicated files under scripts/.
  • Improves maintainability when creating, updating, or sharing skills across teams and projects.

Quick Start

Create a new skill folder at .agents/skills/<name>/ with a SKILL.md frontmatter and place any executable scripts in scripts/ next to it.

Frequently Asked Questions about skill-file-structure

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

FAQPage Schema
What is the best way to structure skill files for team collaboration?

To standardize skill layout, place a root SKILL.md with YAML frontmatter and use optional scripts, references, and assets directories to separate executable code from metadata for easier team collaboration.

How do I organize scripts and metadata when creating a new skill?

To organize scripts and metadata, create a skill folder with a root SKILL.md containing YAML frontmatter, then move executable code into a dedicated scripts directory instead of writing it inline.

Can I write executable code directly inside SKILL.md?

No, inline scripting is not allowed in SKILL.md. You must move executable code to dedicated files under the scripts directory to maintain a clean separation between metadata and code.

What directories are supported for organizing skill resources?

The supported directories for organizing skill resources are scripts for executable code, references for documentation, and assets for housing additional files alongside the root SKILL.md.

What frontmatter is required in a SKILL.md file?

The required frontmatter in a SKILL.md file is YAML format that must include the skill name and description to properly define the metadata for the standardized file structure.

Why should I separate metadata from code in skill file structures?

Separating metadata from code reduces confusion and improves maintainability when creating, updating, or sharing skills across teams and projects by enforcing a consistent layout.