skill-creator

Create and update Codex skill packages with required SKILL.md frontmatter.

4|1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/yoyooyooo/logix --skill skill-creator-yoyooyooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/yoyooyooo/logix/tree/main/.codex/skills/.system/skill-creator
Command: npx skills add https://github.com/yoyooyooo/logix --skill skill-creator-yoyooyooo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of creating effective Codex skills by providing clear structure, required metadata conventions, and practical guidance for building a skill that triggers correctly and stays context-efficient.

Core Features & Use Cases

  • Skill architecture guidance: Defines how SKILL.md frontmatter and body instructions work, plus how to organize optional scripts, references, and assets.
  • Progressive disclosure design: Helps keep SKILL.md concise and delegate large details into bundled resources to reduce context bloat.
  • End-to-end creation process: Guides planning, templating, implementation, validation, packaging, and iteration so skills are usable and distributable.
  • Use case: When you need to build a new workflow/tool/domain capability into Codex as a reusable, modular skill, this skill provides the blueprint for getting it right.

Quick Start

Use the skill to guide you through initializing a new skill folder, completing the SKILL.md frontmatter, and packaging it into a .skill file for distribution.

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 the correct YAML frontmatter and structure?

To create a Codex skill, you must define the required SKILL.md YAML frontmatter (name and description) and organize optional scripts, references, and assets following progressive disclosure principles to keep the context efficient.

What is progressive disclosure in skill packaging and why does it matter?

Progressive disclosure in skill packaging keeps SKILL.md concise by delegating large details into bundled resources, reducing context bloat so the skill triggers correctly and stays efficient during workflow execution.

What's the best way to build a reusable tool integration as a Codex skill?

The best way to build a tool integration skill is to follow the end-to-end creation process: plan the domain workflow, template the SKILL.md, implement scripts, validate naming conventions, and package it into a distributable .skill file.

Do I need to follow specific naming conventions when packaging a skill for distribution?

Yes, you must adhere to specific naming conventions during skill packaging to ensure the resulting skill is discoverable, triggers correctly, and is distributable as a valid .skill file.

Can I update an existing Codex skill package without breaking its workflow?

You can update an existing Codex skill by modifying the SKILL.md frontmatter and body instructions, then validating the changes against the required structure and packaging workflow to ensure the tool integration remains context-efficient.