The skill folder

A practical layout#

The open format requires a SKILL.md entry file. Supporting folders are optional; use only what the workflow needs.

release-note-draft/
├── SKILL.md
├── references/
│   └── editorial-guide.md
├── assets/
│   └── release-template.md
└── scripts/
    └── check-links.py

Give each file a clear role#

Keep the main workflow in SKILL.md. Put detailed background in references, reusable output material in assets, and executable helpers in scripts. Describe how a script is invoked and what it changes.

Use relative links so resources travel with the skill folder. Avoid references to files that only exist on your own machine.

Review the complete package#

Before sharing or installing, check the full folder for secrets, unnecessary files, missing dependencies, and broken references. A readable entry file alone is not enough to evaluate everything the skill can do.