skill-creator

Parse SKILL.md files into structured metadata for downstream discovery.

1.4k|193|Updated Jun 4, 2025
One-click install
npx skills add https://github.com/Jamailar/RedBox --skill skill-creator-jamailar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/Jamailar/RedBox/tree/main/desktop/electron/builtin-skills/skill-creator
Command: npx skills add https://github.com/Jamailar/RedBox --skill skill-creator-jamailar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables Codex to be extended with modular, self-contained Skills that encode domain knowledge, workflows, and tool integrations, empowering teams to standardize capabilities and accelerate automation.

Core Features & Use Cases

  • Specialized workflows: multi-step procedures tailored to specific domains.
  • Tool integrations: guidance for working with file formats, APIs, and external tools.
  • Domain expertise: encapsulated company knowledge, schemas, and business logic.
  • Bundled resources: scripts, references, and assets to accelerate complex tasks.
  • Progressive disclosure: load lightweight metadata initially and bring in full guidance or references on demand as users trigger the skill.
  • Reusability: skill units are reusable building blocks that can be combined or extended for new tasks.

Quick Start

Initialize a new skill with scripts/init_skill.py <skill-name> --path <output-directory> and then customize SKILL.md and add resources as needed.

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 modular skill to standardize workflows in Codex?

Initialize a new skill using scripts/init_skill.py with a chosen skill-name and output directory, then customize the SKILL.md file and add any required bundled resources like scripts, references, or assets to complete the setup.

How does progressive disclosure work for loading skill metadata?

A skill unit requires a root SKILL.md file containing YAML frontmatter with at least a name and description. You can optionally include scripts, references, and assets directories to support complex tasks.

Can I package external tool integrations and business logic into a reusable unit?

Extracted skill metadata includes the name, description, dependencies, components, toxicity status, and other optional fields to enable downstream discovery and execution within the Codex environment.

What is the best way to structure a multi-step domain workflow for automation?

Structure multi-step workflows by writing procedural guidance in the Markdown body of SKILL.md, keeping lightweight metadata in YAML frontmatter, and storing complex execution logic in the bundled scripts directory.