Loading...
Skills
Skills are reusable instructions the AI follows on every prompt in a project. How to write one, apply it per project, publish it or import one from GitHub.
What are skills?
A skill is a reusable instruction document the AI follows while generating code. Use skills for things you always want — code style, naming conventions, framework preferences, error-handling patterns.
Creating a skill
- Go to Skills (sidebar)
- Press “Create skill”
- Give it a name (e.g. "Always use Adventure API")
- Write the instruction in plain English and save
Step 2's button, at the top of the Skills page you reach from the sidebar.
Applying skills to a project
Skills are applied per project, so each project only carries the rules it needs.
- Open the project in the Code Studio
- Open “Project Settings → AI”
- Use the Skills picker to apply (or remove) any of your skills
Sharing & importing
- Publish a skill from the Skills page to share it with the community (public skills are reviewed before they appear)
- Add a community skill to make your own copy you can apply anywhere
- Import from GitHub — repos using the
skills/<name>/SKILL.mdconvention can be imported in one click from the Skills page
Official Skills — a shelf you start with
A third entry can sit in the Skills sidebar between My Skills and Community Skills: Official Skills. It appears only once VyroAI has published some, and it holds a set we maintain — the banner at the top says so: Made by VyroAI, ready for every account. Maintained by us, so they cannot be edited or deleted.
Each card carries an Official mark and an Add to my skills button, which copies it onto your own shelf; the banner's Add all to my skills does the lot, and reads All on your shelf once it has. You do not have to copy one to use it — an official skill can be applied straight from a project's Settings → AI.
A skill can be saved and still never run
Every skill is scanned when you save it, published or not. If the scan flags something, the skill is saved but put ON HOLD — a moderator has to approve it, and until they do it is never given to the AI.
You are told once, in a message when you press save: "Skill saved but ON HOLD — it failed the safety scan", with the reason. After that there is nothing on the skill in your list to say so. It looks completely normal, it can be applied to a project like any other, and it quietly does nothing.
So if a skill you wrote seems to be having no effect at all — not "being ignored sometimes", but no effect — this is the first thing to suspect. Reword the part that got flagged and save it again.
Example skills
- "Always use the Adventure API for chat messages, never
ChatColor.translateAlternateColorCodes." - "Use Lombok annotations where possible to reduce boilerplate."
- "Comment all event handlers with @EventHandler priority and reason."
- "Prefer Folia-compatible scheduler calls over Bukkit's scheduler."
Skills apply only to projects you attach them to. For a one-off rule in a single project, write it as a card under Project Settings → AI → Rules instead — skills are for rules you want to reuse. (The old free-text AI Instructions box is gone; if a project still has one, the Rules screen offers to turn it into cards.)
Where to next
- Next in Power User: Chat vs Build Mode
- Only one project needs it: AI Instructions (Rules) — Rules for one project instead of all of them.
- Rather not write one: Community Skills — Skills other people have already published.
1 of 7 in Power User · Last checked 11 September 2026 · Previous: Studio Offers & Failed Messages