skill-creator

Validate and document AgentSkills with SKILL.md frontmatter and resource directories.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/191854169/openclawFork --skill skill-creator-191854169
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/191854169/openclawFork/tree/main/skills/skill-creator
Command: npx skills add https://github.com/191854169/openclawFork --skill skill-creator-191854169

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating, editing, auditing, and reorganizing AgentSkills to ensure consistent structure and reliable activation.

Core Features & Use Cases

  • Guidance to create new skills from scratch or audit and tidy existing ones
  • Clear patterns for organizing skill directories (scripts/, references/, assets/)
  • Templates and checks that align SKILL.md with the AgentSkills spec

Quick Start

Start by editing SKILL.md to define the skill and then set up scripts/, references/, and assets/ 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 an AgentSkill from scratch using a SKILL.md template?

To create an AgentSkill from scratch, you edit the SKILL.md file to define a frontmatter with required name and description, then add a contextual Markdown body and optional resource directories for activation.

What is the required frontmatter for validating an AgentSkill directory?

Validating an AgentSkill directory requires a SKILL.md frontmatter that enforces mandatory name and description fields, ensuring a compact metadata layer that aligns with the AgentSkills spec for reliable activation.

How do I audit and tidy existing skill directories to align with the AgentSkills spec?

Auditing and tidying existing skill directories involves restructuring them to align with the AgentSkills spec by validating the SKILL.md frontmatter and organizing optional resources into dedicated directories.

What optional resource directories should I set up when documenting agent skills?

When documenting agent skills, you should set up optional resource directories such as scripts/, references/, and assets/ to organize supporting materials that load on demand during skill execution.

Can I use this skill to reorganize an existing skill without breaking its activation?

Yes, you can reorganize an existing skill without breaking activation by enforcing a compact, frontmatter-driven metadata layer in SKILL.md and structuring optional resources to load on demand during execution.

Why does my AgentSkill fail to activate when the SKILL.md frontmatter is missing?

AgentSkill activation fails without SKILL.md frontmatter because the validation logic requires mandatory name and description fields to establish the compact metadata layer needed for proper skill execution.