Where skills live
.midas/skills/<name>/SKILL.md
~/.config/midas/skills/<name>/SKILL.md
.claude/skills/<name>/SKILL.md
.agents/skills/<name>/SKILL.mdMidas reads all four locations. The first two are Midas-native. The last two let an existing Claude or Agents setup work without a copy. Add more folders or registries with the skills config key.
Write one
---
name: release
description: Cut a release and write the notes
---
Read the commits since the last tag. Draft the release notes,
group them by feature, fix, and breaking change, then open the
pull request. The checklist is in checklist.md.The skill name in the frontmatter is the slash command. The body is the prompt. Other files in the skill folder, such as a checklist or a template, are available relative to the skill directory.
Skills and commands
- A command is one Markdown file in .midas/commands, best for a short prompt.
- A skill is a folder, best when the workflow needs reference files or a longer instruction.
- Both become slash commands. A skill only registers if no built-in or command already owns the name.
Import existing skills
midas sync copies skill folders from .claude/skills and .agents/skills into .midas/skills with the whole directory. The provenance is recorded so a repeat run does not copy the same version twice. See Import.
Share a skill
The team registry stores a skill once and lets anyone in the workspace install it. A push uploads the whole directory; a pull installs it locally.
midas skill list
midas skill push release
midas skill pull release
midas skill pull release --globalWithout --global, a pulled skill goes into the current project. With it, the skill is available in every project. The registry is scoped to the organization, so a personal workspace and a shared workspace have separate catalogs.
Related
- Import copies skills from other agents.
- Slash commands shows how a skill appears in a session.
- Agents covers the agent a skill can run under.