Skills

Motir’s skills let the agent you already use work your Motir project. Say motir run and it takes the next ready work item, builds it and opens a linked pull request. Say motir log bug and it checks the defect and files it where it belongs. Say motir mark and it closes a manual work item once you have done it.

They are ordinary Agent Skills: one folder per skill, each with a SKILL.md, published in moooon-B-V/motir-skills. Every command on this page installs release v0.1.0.

Before you start

The skills talk to Motir through its MCP server, so your agent needs that server connected first: a Motir project, a personal access token, and the setup for your agent in the MCP server guide. A token with the default permissions can do everything these skills do. You also need git, and the GitHub CLI (gh) for the skills that open or read pull requests.

Install

Pick your agent. Each section installs all three skills for every project on your machine. The terminal commands are for macOS and Linux: they fetch the release, copy the skill folders into the folder that agent reads, and remove the download.

Claude Code

The repository is also a Claude Code plugin marketplace. Add it at the release tag, then install the plugin; it carries all three skills.

in Claude Code

/plugin marketplace add moooon-B-V/motir-skills#v0.1.0
/plugin install motir@motir-skills

or copy them, in a terminal

git clone --depth 1 --branch v0.1.0 https://github.com/moooon-B-V/motir-skills.git
mkdir -p ~/.claude/skills
cp -R motir-skills/skills/motir-* ~/.claude/skills/
rm -rf motir-skills

A plugin’s skills are listed under the plugin’s name, for example /motir:motir-run. Copied skills keep their own names. For one repository only, copy into .claude/skills in that repository instead. · Claude Code documentation · checked 28 September 2026

Codex

Codex reads skills from .agents/skills — in your home folder for every repository, or in a repository for that repository alone.

in a terminal

git clone --depth 1 --branch v0.1.0 https://github.com/moooon-B-V/motir-skills.git
mkdir -p ~/.agents/skills
cp -R motir-skills/skills/motir-* ~/.agents/skills/
rm -rf motir-skills

Codex notices new skills on its own. If they do not appear, restart it. · Codex documentation · checked 28 September 2026

Cursor

Cursor reads skills from ~/.cursor/skills for every project, and from .cursor/skills in a project.

in a terminal

git clone --depth 1 --branch v0.1.0 https://github.com/moooon-B-V/motir-skills.git
mkdir -p ~/.cursor/skills
cp -R motir-skills/skills/motir-* ~/.cursor/skills/
rm -rf motir-skills

Cursor also reads ~/.agents/skills and ~/.claude/skills, so skills you already copied for Codex or Claude Code are picked up without a second copy. · Cursor documentation · checked 28 September 2026

Gemini CLI

Gemini CLI reads your own skills from ~/.gemini/skills, and a workspace’s from .gemini/skills.

in a terminal

git clone --depth 1 --branch v0.1.0 https://github.com/moooon-B-V/motir-skills.git
mkdir -p ~/.gemini/skills
cp -R motir-skills/skills/motir-* ~/.gemini/skills/
rm -rf motir-skills

Run gemini skills list to check they were found. Gemini CLI also reads ~/.agents/skills. · Gemini CLI documentation · checked 28 September 2026

GitHub Copilot in VS Code

Copilot in VS Code reads your personal skills from ~/.copilot/skills, and a project’s from .github/skills.

in a terminal

git clone --depth 1 --branch v0.1.0 https://github.com/moooon-B-V/motir-skills.git
mkdir -p ~/.copilot/skills
cp -R motir-skills/skills/motir-* ~/.copilot/skills/
rm -rf motir-skills

It also reads ~/.claude/skills and ~/.agents/skills. No setting needs turning on for these folders. · GitHub Copilot in VS Code documentation · checked 28 September 2026

OpenCode

OpenCode reads your own skills from ~/.config/opencode/skills, and a project’s from .opencode/skills.

in a terminal

git clone --depth 1 --branch v0.1.0 https://github.com/moooon-B-V/motir-skills.git
mkdir -p ~/.config/opencode/skills
cp -R motir-skills/skills/motir-* ~/.config/opencode/skills/
rm -rf motir-skills

It also reads ~/.claude/skills and ~/.agents/skills. Run opencode debug skill to see what it found. · OpenCode documentation · checked 28 September 2026

Then ask your agent which skills it has. motir-run, motir-log-bug and motir-mark are listed. Another agent that reads SKILL.md skills works the same way: copy the three folders into the folder it reads skills from.

Use

Type what is under Say into your agent. Replace ACME-12 with the key of a work item in your own project.

`motir-run`

Say: motir run
motir run ACME-12
motir next
What happens: Takes the next ready work item in your project, or the one you name, and builds it. It first tidies up after earlier runs whose pull requests have merged, then claims the work item, builds it on a branch of its own, opens one pull request, and links that pull request to the work item. Name a story whose children have no children of their own, and it runs the whole story: one branch and one pull request per repository, with one commit per child. motir next stops after the claim and prints the prompt, for you to hand to an agent yourself.
What you see in Motir: The work item is assigned to you and moves to In Progress, then to Implemented once its pull request is open. Its page shows the pull request and a How to test section. Motir moves it to In Review when CI passes and to Done when the pull request merges; the skill never does either.

`motir-log-bug`

Say: motir log bug the export button does nothing on an empty board
What happens: Treats what you typed as a claim to check. It finds the cause in the code first, looks for a work item someone has already filed, and files nothing if the behaviour turns out to be correct. Otherwise it files one bug: under the story it holds up, or in your project’s Bugs folder when it holds nothing up.
What you see in Motir: A new bug work item with the cause, where it lives in the code and how to reproduce it, linked to the work item it was found on. If it blocks the work item you are running, that work item moves to Blocked.

`motir-mark`

Say: motir mark ACME-12 done
What happens: Closes a work item no pull request can close: a manual one, such as creating an account, setting a secret or changing a setting. Saying it is your confirmation that the work is finished. It refuses a work item that has a pull request, because that pull request’s merge closes it.
What you see in Motir: The work item moves to Done, with a comment recording that you confirmed it. Its parent’s status follows from its children.

When a work item is wrong

Sometimes a work item cannot be built as written. It may ask for something that does not exist, need a design nobody has drawn, or reach into two repositories. motir-run does not guess its way around that. It moves the work item to Planning, so no other run picks it up, and asks Motir’s AI planner to plan the correction. Then it stops. The plan waits for you to review and approve in Motir, and nothing is built until you do.

If your token cannot use AI planning, or your AI credits have run out, it stops anyway. It leaves a comment on the work item with the whole correction and says why it could not hand it over.

Updating

A new release has a new tag, and this page moves to it. For a copy install, run your agent’s install step again: it overwrites the skill folders in place. In Claude Code, a marketplace cannot be added again at a different tag, so remove it, add it at the new tag and install the plugin again:

in Claude Code

/plugin marketplace remove motir-skills
/plugin marketplace add moooon-B-V/motir-skills#v0.1.0
/plugin install motir@motir-skills

Restart your agent afterwards so it reads the new versions.