organize-skills

Organize skill definitions into canonical skills/ directories with SKILL.md metadata.

68|10|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/google/capsem --skill organize-skills
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: organize-skills
Source: https://github.com/google/capsem/tree/main/skills/meta-organize-skills
Command: npx skills add https://github.com/google/capsem --skill organize-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and standardize how skills are defined and discovered across Claude Code and Gemini CLI, ensuring a single source of truth for skill metadata and directory structure.

Core Features & Use Cases

  • Establish a canonical skills/ directory at the repo root, with one skill per subdirectory and a mandatory SKILL.md frontmatter.
  • Define and communicate how optional references/, scripts/, and assets/ directories are used to store documentation, helpers, and templates for each skill.
  • Provide a structured guide for adding, reorganizing, or removing skills so both CLIs can discover them reliably.

Quick Start

Create a new folder skills/<name> with a SKILL.md frontmatter and body, then optionally add references/, scripts/, and assets/ as needed.

Frequently Asked Questions about organize-skills

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

FAQPage Schema
How do I organize skills in a canonical directory for Claude Code and Gemini CLI?▼

To organize skills, establish a canonical skills/ directory at your repo root with one subdirectory per skill. Each subdirectory must contain a mandatory SKILL.md file with standardized frontmatter to ensure reliable discovery by Claude Code and Gemini CLI.

What is the SKILL.md metadata format for standardizing skill definitions?▼

The SKILL.md metadata format uses required frontmatter fields to provide a single source of truth for skill definitions. It supports a Progressive disclosure approach, guiding users from basic metadata to full resources like optional references, scripts, and assets.

How to add or remove skills while preserving a consistent discovery workflow?▼

To add or remove skills while preserving discovery workflow, create a new skills/<name> folder with a SKILL.md file for additions, or delete the subdirectory for removals. This maintains a standardized structure for Claude Code and Gemini CLI.

Can I use optional directories like scripts and assets when structuring skill metadata?▼

Yes, you can use optional references/, scripts/, and assets/ directories within each skill's subdirectory. These store documentation, helper scripts, and templates respectively, supporting a Progressive disclosure approach from core SKILL.md metadata to full resources.

Does this skill discovery approach work with both Claude Code and Gemini CLI projects?▼

Yes, this skill discovery approach applies to any project using Claude Code and Gemini CLI. It standardizes skill definitions across both CLIs by enforcing a canonical skills/ directory and per-skill SKILL.md metadata for reliable organization.