Skip to content

Prepare a skill

This page assumes you have installed the official plugin and connected MCP.

A skill saves a way of asking for work that you want to repeat. The official plugin teaches the AI the basic operations, so you write only your team’s decision rules and the result you want. Tool names, IDs, and date conversion are not needed.

Start with a template from the skill collection, then adapt the board name and criteria.

Part What to describe Example
Scope Which work to look at The Customer Experience board
Steps What to check, in what order Find overdue tasks and tasks without a ball holder
Decision rules What the AI may decide, and what it should ask Do not invent dates or assignees
Report How to present the result A table of tasks, questions, and links

If board names are duplicated, include the workspace name or a link to the board.

Replace the text in [brackets] and send this to your connected AI:

I want to review my UTSUROI tasks before our weekly meeting.
Scope: [Board name] in [Workspace name]
Check incomplete tasks that I am assigned to, hold the ball for, or created.
Group them into the categories below, with a table of task name, question to resolve, and link.
- Overdue
- No due date
- No ball holder
Do not change any tasks. Leave empty fields as they are and tell me what needs a decision.
If you cannot verify information, say what you could check rather than filling gaps with guesses.

Review the result and adjust the request. For example, add “Include the assignee” or “Sort by nearest due date” to make it fit your team.

Save the tested request using your AI app’s skill feature. Choose a name such as “Weekly task review” and a description explaining when to use it, such as “Before the weekly meeting, check overdue tasks and missing ownership.”

If you are unsure how to save it, ask the connected AI:

I want to reuse the request we just tried under the name “Weekly task review.”
Tell me how to save it as a skill in this app.
If saving is supported, explain where it will be stored and how to invoke it.

Storage and invocation depend on the AI app. After saving, invoke the skill again and check that it contains the intended request.

“Organize this nicely” leaves the decision rules unclear. State your team’s agreements directly:

Intention Example wording
Keep undecided details open If no due date or assignee is given, leave it undecided and ask me.
Preserve existing information Keep the existing labels when adding new ones.
Make handoffs clear When sending work for review, confirm who should hold the ball next.
Review changes first Show the proposed changes and reasons, then apply them after I confirm.
Check the outcome Report successful and unsuccessful actions separately.

These are instructions for the AI’s workflow. To restrict access to reading, also choose read-only connection permissions.