create-skill_skill

This skill guides you in creating or updating a skill with a clean SKILL.md layout and consistent naming conventions.
  • Python

16

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

3 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 dcjanus/prompts --skill create-skill

  • SKILL.md5.9 KB

Overview

This skill defines the repository conventions and minimal template for creating or updating a skill. It explains directory layout, frontmatter requirements, script standards, and where to put references and assets so a new skill is immediately usable. Follow these rules to ensure consistency, discoverability, and reproducible execution.

How this skill works

It inspects and enforces a single-skill-per-directory layout where the directory name matches the declared skill name. It prescribes a minimal frontmatter (name and description), a concise body that gets users executing quickly, and optional folders for scripts, references, and assets. For executable flows it defines exact Python script conventions, dependency declarations, and recommended CLI/tooling patterns so scripts run deterministically.

When to use it

  • Creating a new skill directory and initial files
  • Rewriting or updating a skill’s metadata and usage template
  • Adding executable scripts that provide deterministic, repeatable flows
  • Standardizing how skills reference templates, docs, and assets
  • Preparing a skill for review or publication in the directory

Best practices

  • Name constraint: lowercase letters, digits and hyphens only; no leading/trailing hyphen; no consecutive hyphens
  • Keep description short and include what it does + when to use it (keywords)
  • Body must be the shortest usable flow: one-line purpose, Quick start, common commands, how to inspect uncommon params, and resource links
  • If scripts are used, make them directly executable at ./scripts/* and document the working directory in examples
  • For Python scripts: use uv script shebang, manage dependencies via uv commands, prefer Typer/Rich/Pydantic, and run ruff checks/format before commit
  • Reference and asset links should be one-hop relative paths; link text should be the filename only

Example use cases

  • Add a new skill: create skills/my-skill, populate frontmatter, write a one-line purpose and Quick start
  • Convert a manual flow into a repeatable script: add scripts/flow.py with uv init, declare deps with uv add, and show ./scripts/flow.py usage
  • Update a skill description to improve discoverability by adding user-facing keywords
  • Provide a template asset and show a minimal example of using it from Quick start
  • Prepare a skill for review by verifying name == frontmatter name and running ruff checks

FAQ

At minimum include name and description. Description must state what it does and when to use it, with visible keywords.

How should I declare script dependencies?

Use uv add --script ... and uv remove --script ... to edit the /// script metadata block; do not manually edit the block.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational