Skill Package Builder

Build a portable SKILL.md from structured fields, validate it live, and download a complete ZIP package.

Step 1 · Configure skill

Fill in the details and review live

Sections follow the publishing workflow; the preview and validation update as you type.

Spec checks passed

Identity & trigger description

Help the Agent decide when this skill should be selected.

Skill namekebab-case: release-notes

Trigger keywords

Scenario

Action & output

Usage boundaries

Describe both applicable and non-applicable situations to reduce false triggers.

When to use

When not to use

Instructions

List up to 20 steps in their actual execution order.

Examples & resources

Add verifiable input/output examples and optional resource notes.

Input / output examples

Resource notes (one per line, up to 10)

Optional metadata: License & Compatibility

License

Compatibility

Step 2 · Preview & download

SKILL.md

Validated

---
name: "release-notes"
description: "Use when creating release notes from reviewed Git commits: group verified changes into concise Markdown release notes. Keywords: release notes, git, changelog."
---

# Release Notes

## When to use
Use after code changes have been merged and the commit range is known.

## When not to use
Do not invent unreleased changes or infer user impact without source commits.

## Instructions
1. Read the supplied commit messages and pull request summaries.
2. Group user-facing changes by feature, fix, and breaking change.
3. Omit internal-only commits unless the user requests them.

## Examples
Input: Three reviewed commit messages.
Output: Categorized Markdown release notes with no unverified claims.

## Bundled resources
- references/style-guide.md — optional release-note style rules

WARNING · LINT003
The body references bundled paths that cannot be verified from a single file.
When publishing a package, include the referenced references/, scripts/, or assets/ entries.

Include README.md

ZIP contains SKILL.md, optional README, and empty references/scripts/assets placeholders. Form fields are not persisted automatically.

About this tool

Made for the task at hand.

Turn skill requirements into a consistent, portable package without an AI call. The form assembles a three-part trigger description and fixed body sections, then runs the same validation rules as the Skill Validator before creating a ZIP with empty resource directories and an optional README.

How to use

Enter a name, scenario, action, keywords, applicable and non-applicable situations, up to 20 instructions, and optional examples or resource notes.
Review the read-only SKILL.md preview and inline validation findings, then correct any errors.
Choose whether to include a README and download the generated ZIP for manual testing and review.

Your work stays yours.
Tool inputs are processed locally in your browser and are never sent to KitVerse servers. Clear the workspace when using a shared device.

Common questions

Does the builder call an AI model?

No. It deterministically assembles only the text you enter. Review the generated draft and test it in your target Agent hosts before distribution.

Are form drafts saved automatically?

No. Fields and generated content remain in page memory and disappear on refresh. Download the ZIP to keep a copy; nothing is written to localStorage by this workspace.

Skill Package Builder

Fill in the details and review live

Identity & trigger description

Usage boundaries

Instructions

Examples & resources

Made for the task at hand.

How to use

Related tools · AI & LLM

Skill Validator & Linter

Skill Security Scanner

Prompt to Skill Converter