create-command

Scaffold a Codex skill by creating SKILL.md with YAML frontmatter.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/MaplumeX/deepresearch --skill create-command-maplumex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-command
Source: https://github.com/MaplumeX/deepresearch/tree/main/.agents/skills/create-command
Command: npx skills add https://github.com/MaplumeX/deepresearch --skill create-command-maplumex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds a new Codex skill by creating a properly named SKILL.md with a reusable structure and validated frontmatter, enabling consistent discovery and activation.

Core Features & Use Cases

  • Creates a ready-to-use SKILL.md at .agents/skills/<skill-name> containing mandatory YAML frontmatter (name and description) and a starter body.
  • Enforces naming conventions and directory structure for new skills, making it easy to integrate into existing Trellis workflows.
  • Supports on-demand extension with optional directories (scripts/, references/, assets/) as the skill evolves.

Quick Start

Run the create-command <skill-name> <description> to generate a new skill skeleton in the .agents/skills directory.

Frequently Asked Questions about create-command

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

FAQPage Schema
How do I scaffold a new skill with valid YAML frontmatter?

To scaffold a new skill, you generate a SKILL.md file at .agents/skills/<skill-name> with mandatory YAML frontmatter including name and description, plus a concise executable body. This ensures the skill meets discovery and activation criteria.

What is the required directory structure for creating a Codex skill?

The required directory structure places a SKILL.md file directly inside .agents/skills/<skill-name>. It supports on-demand extension by adding optional directories like scripts/, references/, and assets/ as the skill evolves.

How do I standardize skill creation to enforce naming conventions?

You standardize skill creation by using a scaffolding process that automatically applies proper naming conventions to the <skill-name> directory and validates the inclusion of mandatory YAML frontmatter fields before integration.

Can I use this scaffolding process to extend an existing Trellis workflow?

Yes, you can extend a Trellis workflow by scaffolding a new custom or developer workflow skill. The generated SKILL.md integrates directly into the existing .agents/skills directory, maintaining consistent discovery and activation.

What do I need to include in a SKILL.md file for it to be discoverable?

A SKILL.md file requires mandatory YAML frontmatter containing both a name and description field, along with a usable starter body. This structure ensures the skill complies with unit criteria for proper discovery.