createskill_skill

This skill helps validate and canonicalize skills by ensuring TitleCase structure and YAML accuracy across skill files.
  • TypeScript

10.2k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill danielmiessler/personal_ai_infrastructure --skill createskill

  • SKILL.md8.0 KB

Overview

This skill validates that a skill follows the canonical structure and naming conventions so it can integrate smoothly with agentic workflows. It enforces TitleCase naming, a single-line frontmatter description with a USE WHEN clause, required routing and examples sections, and overall filesystem structure. The outcome is a clear pass/fail report and actionable remediation guidance.

How this skill works

The validator reads the authoritative canonical spec and then inspects the target skill directory and files. It checks directory and file naming, frontmatter formatting, required markdown sections, workflow routing consistency, tooling flags, and CLI-first intent-to-flag mappings where applicable. Finally, it produces a compliance report with recommended fixes or a pass confirmation.

When to use it

  • When introducing a new skill to the shared skills collection
  • When updating a skill to ensure naming and routing remain canonical
  • Before merging a skill into a production agent to avoid runtime mismatches
  • When converting older skills from legacy frontmatter formats
  • When adding CLI tools to ensure intent-to-flag mappings exist

Best practices

  • Use TitleCase for skill directories, workflow files, and tool files consistently
  • Keep the frontmatter description single-line and include a clear USE WHEN phrase
  • Maintain a ## Workflow Routing table that mirrors actual workflow filenames
  • Include a ## Examples section with 2–3 concise patterns showing user→action→result
  • Place reference docs at the skill root and keep a tools/ directory (even if empty)
  • For CLI tools, expose behavior via flags and include an intent-to-flag mapping table

Example use cases

  • Validate a newly created skill before publishing to the shared skill index
  • Audit an existing skill after a refactor to catch naming or routing regressions
  • Check CLI-based skills to ensure flags cover mode, output, and resource choices
  • Run a pre-merge check to ensure frontmatter is canonical and under length limits
  • Generate a remediation checklist when a skill fails one or more validations

FAQ

Any mismatch in TitleCase naming, a multi-line or missing USE WHEN frontmatter, absent routing or examples sections, missing tools/ directory, or incorrect CLI intent-to-flag mappings will mark the skill non-compliant.

Does the validator auto-fix issues?

It provides precise remediation steps but does not modify files automatically; use the Canonicalize workflow or manual edits to apply fixes.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
createskill skill by danielmiessler/personal_ai_infrastructure | VeilStrat