Andrés Bayón
c925dd3135
* docs: add CONTRIBUTING guide and link it from README Document how to contribute a skill: the public-safety rule, the skills/<name>/SKILL.md folder layout and frontmatter, that skills go in as plain folders (not zipped .skill files), the versioning approach, and the PR flow. Link it from the README. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: tighten CONTRIBUTING prose Reduce em-dash density and split welded clauses for readability. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2.2 KiB
Contributing
Thanks for wanting to add a skill. This repo is a shared, public collection of agent skills for Unity workflows, and new contributions are welcome.
Before you start
This is a public repository built on the open skills.sh standard. Anything you contribute ships publicly, so a skill must not reference anything internal: no internal services, internal URLs, credentials, or confidential workflows. If a skill only makes sense inside Unity's network, it doesn't belong here.
Skill structure
Each skill is a folder under skills/, with a SKILL.md at its root:
skills/
your-skill/
SKILL.md
SKILL.md starts with YAML frontmatter, then the instructions the agent follows. The unity-cli skill is a good template to copy:
---
name: your-skill
description: Use when … (one or two sentences on exactly when an agent should reach for this skill).
allowed-tools:
- Bash
---
name: matches the folder name, in kebab-case.description: what the agent reads to decide whether to trigger the skill, so be specific about when it applies. Start with "Use when …".allowed-tools: optional. List the tools the skill needs, or leave it out if there's no restriction.
A README, CHANGELOG, and reference .md files alongside SKILL.md are all fine; the installer pulls the whole folder. Keep SKILL.md focused on instructions and move long reference material into separate files it links to.
Submit skills as plain folders committed to the repo. Don't check in a zipped .skill archive. Agents read SKILL.md directly, which is what the skills.sh tooling and review expect. You're welcome to package a .skill for distribution elsewhere.
Versioning
There's no per-skill release mechanism. Versioning is just the repo's git history and PRs. A CHANGELOG.md inside your skill folder is welcome as documentation, but nothing automated reads it.
Submitting
- Add your skill folder under
skills/. - Test it with realistic prompts in your own agent first.
- Open a PR. Stick to one skill per PR where you can.
- A maintainer reviews and merges.
Help
Questions or feedback? Post in the Unity Discussions forum.