structured-skill-creator

Create and validate skills in a local skills/ repository with strict template structure.

5|Updated Jul 6, 2025
One-click install
npx skills add https://github.com/GuicedEE/ai-rules --skill structured-skill-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structured-skill-creator
Source: https://github.com/GuicedEE/ai-rules/tree/main/skills/.curated/structured-skill-creator
Command: npx skills add https://github.com/GuicedEE/ai-rules --skill structured-skill-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Creating and validating skills within a local repository is error-prone without a strict, repeatable workflow. This Skill enforces a template-based approach to skill scaffolding and ensures consistent metadata and structure.

Core Features & Use Cases

  • Local template scaffolding that standardizes skill layout (SKILL.md, agents/openai.yaml, LICENSE.txt) and optional folders (scripts/, references/, assets/).
  • Automated validation using internal scripts to verify frontmatter, required files, and directory structure before delivery.
  • Use Case: teams can rapidly bootstrap new skills for internal tooling and governance with guaranteed compliance.

Quick Start

Scaffold a new skill from the template, customize its content, and run strict validation before final delivery.

Frequently Asked Questions about structured-skill-creator

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

FAQPage Schema
How do I automate skill scaffolding for a local repository?

Skill scaffolding is automated by applying a strict template workflow that generates required root files like SKILL.md, agents/openai.yaml, and LICENSE.txt, then validates the directory structure before final delivery.

What's the best way to validate skill metadata and frontmatter before delivery?

Validating skill metadata requires running internal validation scripts that check for required frontmatter fields like name and description, verify mandatory root files exist, and enforce correct directory structure.

How do I create a new skill template with standardized directories?

Creating a new skill template involves scaffolding the standardized layout with required root files and optional folders like scripts/, references/, and assets/, ensuring consistent structure for internal tooling and governance.

Why does my skill validation fail when required files are missing?

Skill validation fails when the strict template workflow detects missing mandatory files such as SKILL.md, agents/openai.yaml, or LICENSE.txt at the root, or when frontmatter lacks required name and description fields.

Do I need a specific repository structure to scaffold and validate skills locally?

A local skills/ repository structure is required to scaffold and validate skills, where the strict template enforces frontmatter compliance and mandates SKILL.md, agents/openai.yaml, and LICENSE.txt at the skill root.

Can I customize skill templates with optional folders like scripts and references?

Customizing skill templates supports optional folders including scripts/, references/, and assets/ alongside the required root files, allowing teams to bootstrap new skills while maintaining guaranteed compliance through validation.