Skip to content

DocsUsing Praxis

Skills and commands

The workflows every agent gets on connect, the four Praxis skills, the Claude plugin's commands, and where your team's own conventions go.

What every agent gets

When an AI app connects, Praxis sends it a short core workflow: call praxis_meta first, search before creating, claim before working, finish or hand back with an outcome, and publish updates only when told. ChatGPT, Claude, Cursor and others pass it to the model, so nothing has to be installed.

Skills add the fuller workflows for tools that support them.

The four skills

SkillUse it for
praxis-workTaking a ticket, claiming it, recording decisions, and finishing or handing it back with an outcome.
praxis-intakeTurning a conversation, meeting notes, a bug report or a document into a few clear tickets, without duplicates.
praxis-planningWhat to work on next, what is blocked, how long work really takes, and bulk triage.
praxis-updatesStakeholder updates, personal Notes with checklists, and mentions.

None of them assume software, folders or board names. They work for any team that tracks work in Praxis.

Install them

  • Claude Code and Cowork: install the Praxis plugin. It adds the skills and the commands below.
  • Other tools with skills: download each skill from https://praxis.theorem-labs.com/skill/<name>.md with your key, for example /skill/praxis-work.md.
  • Tools with one instructions file: use https://praxis.theorem-labs.com/skill/praxis.md, which holds all four.
  • The setup prompt in Settings installs them for you.

Set up before November 2026? The old /skill/kanban-task.md address still works and now serves the same four workflows.

Claude plugin commands

CommandDoes
/praxis:next [board]Takes the most important ready ticket and proposes a first step.
/praxis:status [board]Summarises what is ready, in progress, blocked and stale. Changes nothing.
/praxis:file [text]Files tickets from the text or the conversation, after you confirm the list.
/praxis:update [topic]Drafts a stakeholder update. It never publishes on its own.
/praxis:handoff [key]Records where the work got to and releases the ticket.

Add your team's conventions

Put rules that are specific to your team in Project settings → Team and agent instructions: which board each kind of work goes on, how to name branches, what needs a review. Every agent reads them through praxis_meta, whichever tool it runs in, so you write them once.