logoTskVlo
Download
How-To Guides
ai 7 min read

Best AI Prompts for TskVlo

Ready-to-use prompts for Claude, Cursor, and other MCP-enabled AI tools to manage your TskVlo boards with natural language.

Once your AI tool is connected via MCP, you can manage TskVlo boards with natural language. These prompts work well with Claude Desktop, Cursor, and any MCP-compatible assistant.

Prerequisites

Your AI tool must be configured with the TskVlo MCP server. See the MCP Setup guide for instructions.

Getting an Overview

What boards do I have in my TskVlo workspace?
Show me all items in the "Engineering Backlog" board that are currently In Progress.
List all overdue tasks assigned to me across all boards.

Note: The list_items tool works per board, so cross-board prompts like this make the AI call list_boards first and then list_items for each board in turn. Naming a specific board gets faster results.

Creating Items

Create 5 tasks in the "Sprint 14" group of my Engineering board:
1. Implement login page
2. Write API tests for auth endpoint
3. Update deployment pipeline
4. Review design mockups
5. Update changelog
Set all of them to "Backlog" status and assign them to me.
Add a task called "Client call follow-up" to the Acme workspace, Marketing board, 
Backlog group. Set due date to Friday. Assign to sarah@team.com.

Bulk Updates

Move all items in the "Done" group of the Sprint 13 board to the "Archive" group.
Assign all unassigned tasks in the Engineering Backlog to alex@team.com.
Set the status of all items tagged "Beta" to "In Progress".

Status Updates

Mark the task "Fix login bug" as Done and add a comment that the fix ships with the next release.
Update the due date of all high-priority tasks in the Marketing board to next Monday.

Moving Items Between Boards

Move the task "Checkout fails on Safari" from the Support board to the "Backlog" 
group of the Engineering board. Tell me which field values didn't carry over.
Move every item in the "Escalated" group of the Support board to the "Triage" group 
of the Engineering board.

Note: Sub-items move along with their parent. Field values transfer when the target board has a field with the same name and type — Status and Tags are matched by label — and the AI gets a report of what was moved and what was dropped.

Your Notification Inbox

These prompts need an OAuth connection — an API key has no user and therefore no inbox.

What are my unread notifications? Group them by board and tell me which ones 
need a reply from me.
Show me everything that happened on the Website Redesign board since Monday, 
then mark those notifications as read.
Go through my mentions, summarize each discussion in one sentence, and mark 
them as read.

Automation Rules

List the automation rules on the Support board and explain in plain words 
what each one does.
Create an automation rule on the Support board: when the Status changes to 
"Done", move the item to the "Closed" group.
Add a rule to the Sales board that assigns every item created in the 
"New leads" group to the person who created it.
Run the "Weekly cleanup" rule on the Operations board.

Note: Rules are checked before they’re saved — a rule can only use fields and groups of its own board. New and changed rules show up immediately in the board’s automation settings.

Working with the Wiki

Read the "Release checklist" wiki page and create a task on the Engineering 
board for every step.
Create a wiki page "Sprint 14 retrospective" under "Engineering" with 
sections for what went well, what didn't, and action items.
Find the wiki pages about onboarding and move them under a new parent page 
called "People & HR".

Generating Reports

How many tasks does each team member have assigned in the Engineering board? 
Give me a breakdown by status.
Summarize what was completed in the last 7 days across all boards.
What items have been sitting in "In Progress" for more than 5 days?

Sprint Planning

I'm planning Sprint 15. Here are the features we want to build:
[paste list of features]

Create tasks for each feature in the Engineering board, Sprint 15 group. 
Add sub-tasks for: design, implementation, and QA for each.

Tips for Better Results

  • Be specific about workspace, board, and group names — the AI uses these to find the right location.
  • Name the board when you can — “across all boards” prompts work, but the AI has to iterate every board one by one, which is slower.
  • Reference field names exactly — if your field is called “Priority” not “Urgency”, use “Priority”.
  • Ask for confirmation before bulk operations — “list what you’d change before doing it”.
  • Use a read-only connection for reporting — if you only want answers, a read-only API key or OAuth grant makes sure nothing gets changed by accident.
  • Chain commands: “Create the tasks, then assign them all to me, then set their due date to end of sprint.”
← Back to Guides