skill_creator

Create or update model-invoked skills with SKILL.md and register_skill.

2.0k|410|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/espressif/esp-claw --skill skill-creator-espressif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill_creator
Source: https://github.com/espressif/esp-claw/tree/main/components/common/skill_builder/skills/skill_creator
Command: npx skills add https://github.com/espressif/esp-claw --skill skill-creator-espressif

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the need to create, update, and register reusable model-invoked skills—especially workflow, function, and Lua-backed capabilities—without leaving the system in an unregistered or inconsistent state.

Core Features & Use Cases

  • Skill authoring guidance: Defines the mandatory creation steps, required skill file layout, and safe skill_id and intent description rules.
  • Lua-backed packaged skill support: Documents how to include bundled Lua files under a skill-local scripts directory and how the skill should invoke them.
  • Correct registration flow: Ensures every created or updated skill is immediately registered via register_skill using the exact expected file path.

Quick Start

Ask to add or update a reusable capability like “create a tool for measuring temperature” and include any Lua requirement so the skill_creation flow can generate the complete SKILL.md and bundled files, then register the new skill.

Frequently Asked Questions about skill_creator

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

FAQPage Schema
How do I create and register reusable agent skills for new workflows?

To create and register reusable agent skills, you write complete skill-owned source files including a root SKILL.md with name and description frontmatter, then finalize registration via register_skill using the <skill_id>/SKILL.md path.

How does Lua packaging work when adding firmware automation skills?

Lua packaging for firmware skills involves bundling Lua files under a skill-local scripts directory, which the skill then invokes to execute project-specific automations under designated build paths.

What is the correct file layout for model-invoked tool registration?

Correct tool registration requires a complete skill-owned source file layout featuring a root SKILL.md with proper name and description frontmatter, followed by final registration via register_skill.

Can I update existing skills without leaving the system in an inconsistent state?

Yes, you can update existing skills by modifying the source files and immediately re-registering them via register_skill using the exact expected file path, ensuring the system avoids unregistered or inconsistent states.

When do I need to introduce Lua-backed automations under project-specific build paths?

You need to introduce Lua-backed automations when user requests involve adding functions, creating tools, or updating skills that require packaged Lua scripts executed under project-specific build paths.

What are the limitations of updating agent workflows with this skill creation approach?

The approach requires writing complete skill-owned source files and mandates final registration via register_skill; failing to follow the exact <skill_id>/SKILL.md path leaves new capabilities unregistered or inconsistent.