skill-creator

Guide developers to create and update Codex skills with standardized SKILL.md structure.

16|2|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/Altinity/Skills --skill skill-creator-altinity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/Altinity/Skills/tree/main/altinity-expert-clickhouse/skills/.system/skill-creator
Command: npx skills add https://github.com/Altinity/Skills --skill skill-creator-altinity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml.

What problem does it solve?

Provides a standardized approach and templates to create and update Codex skills, reducing ambiguity and ensuring consistency across team skill artifacts.

Core Features & Use Cases

  • Standard SKILL.md frontmatter with required fields (name and description) and a well-structured body that describes the skill's purpose and usage.
  • Guidance on structuring SKILL.md using common patterns (workflow-based, task-based, reference/guidelines, capabilities-based) and progressive disclosure to minimize context load.
  • Clear guidance on bundling resources (scripts, references, assets) and guidance for initialization, organization, and packaging workflows from start to distribution.

Quick Start

Create a new skill by populating SKILL.md with a clear name and description, then structure the body and plan optional resource directories.

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 Codex skill with a standardized SKILL.md structure?

To create a Codex skill, populate SKILL.md with required frontmatter fields like name and description, then structure the body using established patterns like workflow-based or task-based layouts to ensure consistency and reduce ambiguity.

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

Progressive disclosure in skill creation minimizes context load by keeping SKILL.md lean and actionable, organizing detailed resources into separate scripts, references, or assets rather than embedding everything directly in the main file.

How do I package and distribute Codex skills with bundled resources?

Packaging Codex skills involves bundling external resources like scripts and assets into organized directories, following initialization and distribution workflows to maintain a high-quality, consistent artifact structure across team projects.

Do I need YAML to manage frontmatter standards for Codex skills?

YAML is required to define and manage SKILL.md frontmatter standards, ensuring required fields like name and description are properly formatted and parsed during skill initialization and packaging workflows.

What is the best way to structure a SKILL.md body for task-based workflows?

The best way to structure a task-based SKILL.md body is to follow standard organization patterns, using concise frontmatter and progressive disclosure to describe the skill's purpose and usage without overwhelming the context window.

Why does my Codex skill lack consistency across team artifacts?

Codex skills lack consistency when developers do not follow standardized approaches for frontmatter and body organization, which this skill resolves by providing templates and guidelines for high-quality structure.