skill-creator

Create reusable Skill Units with SKILL.md frontmatter and packaging.

119|21|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/stvlynn/dingtalk-wukong-skills --skill skill-creator-stvlynn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/stvlynn/dingtalk-wukong-skills/tree/main/skill-creator
Command: npx skills add https://github.com/stvlynn/dingtalk-wukong-skills --skill skill-creator-stvlynn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Creating and maintaining modular, reusable agent Skills from scattered task patterns can be error prone and hard to scale. This guide provides a standardized skeleton, templates, and tooling to turn ad-hoc workflows into packaged Skill Units.

Core Features & Use Cases

  • Standard SKILL.md frontmatter (name, description) to enable discovery and triggering.
  • Optional resource directories (scripts/, references/, assets/) to organize tooling, references, and outputs.
  • Step-by-step Skill Creation process: understand intent, plan with files, implement resources, validate, and package.
  • Packaging ready zip artifacts for distribution.

Quick Start

Create a new skill by running init_skill.py <skill-name> --path <path> and then tailor SKILL.md plus add any needed resources.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I turn ad-hoc task patterns into reusable agent skills?

To turn ad-hoc task patterns into reusable agent skills, use this tool to capture intent, plan with files, implement resources, validate frontmatter, and package the workflow into a zip artifact. It standardizes scattered workflows into modular Skill Units for process automation and document processing.

What is the standard structure required to package an agent skill?

The standard structure to package an agent skill requires a SKILL.md file with required frontmatter for discovery and triggering. It also supports optional resource directories including scripts, references, and assets to organize tooling and outputs for distribution.

How do I create a new skill from a template and initialize the directories?

To create a new skill and initialize directories, run init_skill.py with the desired skill name and path. This generates the standardized skeleton where you can tailor SKILL.md and add any needed resources before validation and packaging.

Does skill creation require specific dependencies or environments to validate frontmatter?

Skill creation and frontmatter validation require the yaml dependency to parse configuration correctly. The workflow operates within the agent ecosystem, using a plan-with-files approach to enforce required metadata and optional resource directory structures before packaging.

What is the best way to organize scripts and references when designing agent skills?

The best way to organize scripts and references when designing agent skills is using the optional resource directories. Place tooling in scripts, reference materials in references, and outputs in assets to maintain a standardized structure that enables reliable discovery and triggering.

When should I not use a standardized skill template for process automation?

You should not use a standardized skill template for process automation when your workflow cannot be modularized into discrete intent, planning, and validation steps. Complex ad-hoc workflows lacking defined triggers or reusable patterns are unsuitable for this packaging approach.