skill-creator

Create, validate, and package AI agent skills with scripts and references.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Grong/openhub-client --skill skill-creator-grong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/Grong/openhub-client/tree/main/crates/backend/openhub-app/assets/builtin-skills/auto-inject/skill-creator
Command: npx skills add https://github.com/Grong/openhub-client --skill skill-creator-grong

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing effective skills for AI agents requires knowing the right structure, frontmatter rules, and resource organization, and doing it by hand leads to invalid or bloated skills that fail to trigger correctly. ## Core Features & Use Cases - Guided Skill Authoring: Provides design principles for SKILL.md frontmatter, progressive disclosure, and degrees of freedom so skills stay concise and trigger reliably. - Scaffolding and Packaging Scripts: Includes init_skill.py to generate a template skill directory and package_skill.py to validate and bundle a skill into a distributable .skill file. - Reference Patterns: Ships workflow and output-pattern references covering sequential steps, conditional logic, templates, and examples. - Use Case: You want to build a pdf-editor skill. Run the initializer to scaffold the directory, follow the guidance to write SKILL.md and add a rotate script, then package it into a validated .skill file for distribution. ## Quick Start Ask the agent to create a new skill named pdf-editor that rotates PDF pages and package it for distribution.

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 new skill for an AI agent?

Run init_skill.py with a hyphen-case skill name and output path to scaffold the directory. It generates a SKILL.md template plus example scripts, references, and assets folders that you customize or delete.

What should go in the SKILL.md description field?

The description must state what the skill does and exactly when to use it, including trigger scenarios and file types. It is the primary triggering mechanism, so all when-to-use information belongs there, not in the body.

How do I package a skill into a .skill file?

Run package_skill.py with the skill folder path and an optional output directory. It validates the frontmatter, naming, and structure first, then creates a zip-based .skill file only if validation passes.

When should I use scripts versus references in a skill?

Use scripts for deterministic, repeatedly rewritten code like file conversions, and references for documentation Claude loads on demand such as schemas or API guides. Assets hold files used in output like templates and fonts.

Why does skill validation fail on my frontmatter?

Validation fails when the name is not hyphen-case, exceeds 64 characters, the description contains angle brackets or exceeds 1024 characters, or unexpected keys appear. Only name, description, license, allowed-tools, and metadata are allowed.