skill-creator

Create and validate aramb SKILL.md definitions with standardized frontmatter and body sections.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/clode-labs/aramb-skills --skill skill-creator-clode-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/clode-labs/aramb-skills/tree/main/skill-creator
Command: npx skills add https://github.com/clode-labs/aramb-skills --skill skill-creator-clode-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables consistent creation and validation of aramb SKILL.md definitions, ensuring standardized structure and high-quality documentation for new or updated skills.

Core Features & Use Cases

  • Standardized frontmatter requirements (name, description, category, tags, license) enforced for every skill.
  • Structured, execution-ready body sections (role, responsibilities, constraints, workflow, best practices, validation).
  • Guidance and templates to help skill authors plan, write, and review skills, improving discoverability and reuse.
  • Use Case: A team wants to add a new skill for a domain; they follow this Skill Creator to generate a compliant SKILL.md and optional references/assets.

Quick Start

Create a new directory skills/my-skill/ and add SKILL.md following the frontmatter rules; then run through the Skill Creator workflow to draft the body sections and save the files.

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 standardized SKILL.md definition for a new aramb skill?▼

Creating a standardized aramb skill requires defining required frontmatter fields like name, description, category, tags, and license, then structuring the body with role, responsibilities, constraints, and workflow sections to ensure execution-ready documentation.

What frontmatter fields are required for aramb skill creation and validation?▼

Required frontmatter for aramb skill validation includes name, description, category, tags, and license. Enforcing these standardized metadata fields ensures high-quality documentation, improving skill discoverability and reuse across teams.

How should I structure the body sections when authoring skill documentation?▼

Authoring skill documentation requires a structured body containing role, responsibilities, constraints, workflow, best practices, and validation sections. This execution-ready format helps skill authors plan, write, and review skills consistently.

What's the best way to validate updated skills for compliance with documentation standards?▼

Validating updated skills for documentation standards involves running them through the Skill Creator workflow to check frontmatter compliance and review body structure, ensuring all required fields and execution-ready sections are correctly defined.

Do I need any specific dependencies or components to start authoring aramb skills?▼

Authoring aramb skills requires no external dependencies or components. You simply create a new directory like skills/my-skill/, add a SKILL.md file following the frontmatter rules, and draft the body sections.

When do I need to include optional resources and references in a SKILL.md file?▼

Optional resources and references in a SKILL.md file are needed when a skill requires supplementary assets or documentation to support its execution-ready workflow, helping teams add domain-specific skills with compliant definitions.