Shortcut Automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/shortcut-automation --openclawShortcut Automation
Automate your Shortcut project management operations directly from Claude Code. Create and list stories, add tasks and comments, batch-create stories, and navigate workflows -- all without leaving your terminal.
Toolkit docs: composio.dev/toolkits/shortcut
Setup
- Add the Rube MCP server to your Claude Code config with URL:
https://rube.app/mcp - When prompted, authenticate your Shortcut account through the connection link provided
- Start automating your project management workflows with natural language
Core Workflows
1. Create Stories
Add new stories to your Shortcut workspace with full configuration.
Tool: SHORTCUT_CREATE_STORY
Create a feature story called "Add dark mode support" in workflow state 500000001 with estimate 5 and label "frontend"
Key parameters for SHORTCUT_CREATE_STORY:
name(required) -- the story titleworkflow_state_id-- the workflow state to place the story in (recommended overproject_id)story_type--"feature","bug", or"chore"description-- story body/descriptionestimate-- numeric point estimate (or null for unestimated)epic_id-- associate with an epiciteration_id-- associate with an iterationlabels-- array of label objects withname(and optionalcolor,description)owner_ids-- array of member UUIDs to assigndeadline-- due date in ISO 8601 formattasks-- inline task array withdescriptionand optionalcomplete,owner_idscomments-- inline comment array withtextstory_links-- link stories withverb("blocks","duplicates","relates to")
Important: Either workflow_state_id or project_id must be provided, but not both. workflow_state_id is recommended as Projects are being sunset in Shortcut.
2. Batch Create Stories
Create multiple stories in a single API call.
Tool: SHORTCUT_CREATE_MULTIPLE_STORIES
Create 3 bug stories: "Login page 500 error", "Cart total rounding issue", and "Search results empty state broken"
- Requires
storiesarray where each element follows the same schema asSHORTCUT_CREATE_STORY - Each story in the array requires
name - Efficient for bulk imports, sprint planning, or template-based story creation
3. List Stories in a Project
Retrieve all stories within a specific project.
Tool: SHORTCUT_LIST_STORIES
List all stories in project 42 with their descriptions
- Requires
project__public__id(integer project ID) - Optional
includes_description: trueto include story descriptions in the response - Returns all stories with their attributes (status, type, estimate, etc.)
4. Manage Story Tasks
Create tasks (checklists) within stories for tracking sub-work.
Tool: SHORTCUT_CREATE_TASK
Add a task "Write unit tests for dark mode toggle" to story 12345
Key parameters:
story__public__id(required) -- the parent story IDdescription(required) -- the task descriptioncomplete-- boolean, defaults to falseowner_ids-- array of member UUIDs to assign the taskexternal_id-- ID from an external tool if imported
5. Add Story Comments
Post comments on stories for discussion and documentation.
Tool: SHORTCUT_CREATE_STORY_COMMENT
Add a comment to story 12345: "Reviewed the implementation -- looks good, but needs accessibility testing"
Key parameters:
story__public__id(required) -- the story IDtext(required) -- the comment bodyauthor_id-- member UUID (defaults to API token owner)parent_id-- ID of parent comment for threaded replies
6. Workflow and Project Discovery
List workflows and projects to resolve IDs for story creation.
Tools: SHORTCUT_LIST_WORKFLOWS, SHORTCUT_LIST_PROJECTS
Show me all workflows in our Shortcut workspace so I can find the right workflow state ID
SHORTCUT_LIST_WORKFLOWSreturns all workflows with their states (IDs, names, types)SHORTCUT_LIST_PROJECTSreturns all projects with their attributes- Use these to discover valid
workflow_state_idandproject_idvalues before creating stories
Known Pitfalls
workflow_state_idvsproject_id:SHORTCUT_CREATE_STORYrequires exactly one of these. Providing both or neither causes a rejection. Preferworkflow_state_idsince Projects are being sunset.- Projects are being sunset: Shortcut is deprecating Projects in favor of workflow-based organization. Use
workflow_state_idfor new stories. - Label creation is inline: Labels in the
labelsarray are created on-the-fly if they do not exist. Thenamefield is required for each label object. - Story type defaults: If
story_typeis omitted, it defaults to"feature". Always set it explicitly for bugs and chores. - Batch limits:
SHORTCUT_CREATE_MULTIPLE_STORIESprocesses all stories in a single request. Very large batches may time out -- keep batches under 25 stories. - Integer IDs for stories/projects: Story and project IDs are integers, not UUIDs. Member and group IDs are UUIDs. Mixing these formats causes errors.
move_topositioning: Themove_tofield ("first"or"last") moves the story within its workflow state, not across states.
Quick Reference
| Tool Slug | Description |
|---|---|
SHORTCUT_CREATE_STORY | Create a single story (requires name + workflow_state_id or project_id) |
SHORTCUT_CREATE_MULTIPLE_STORIES | Batch-create multiple stories (requires stories array) |
SHORTCUT_LIST_STORIES | List stories in a project (requires project__public__id) |
SHORTCUT_CREATE_TASK | Create a task in a story (requires story__public__id, description) |
SHORTCUT_CREATE_STORY_COMMENT | Add a comment to a story (requires story__public__id, text) |
SHORTCUT_CREATE_STORY_FROM_TEMPLATE | Create a story from a template |
SHORTCUT_LIST_WORKFLOWS | List all workflows and their states |
SHORTCUT_LIST_PROJECTS | List all projects |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/shortcut-automation/SKILL.mdView on GitHub Overview
Shortcut Automation lets you manage stories, tasks, epics, and workflows directly from Claude Code. Create and list stories, add tasks and comments, and batch-create items using natural language commands. It connects via the Rube MCP server and supports targeting with workflow_state_id or project_id.
How This Skill Works
This skill maps natural language requests to Shortcut API tools such as SHORTCUT_CREATE_STORY, SHORTCUT_CREATE_MULTIPLE_STORIES, SHORTCUT_LIST_STORIES, SHORTCUT_CREATE_TASK, and SHORTCUT_CREATE_STORY_COMMENT. After setting up the Rube MCP connection, you authenticate your Shortcut account and issue commands that specify parameters like name, workflow_state_id, story_type, estimate, epic_id, and tasks or comments to perform the desired operation.
When to Use It
- Starting a new sprint and quickly creating multiple stories with specific states and labels.
- Updating daily work by adding tasks or comments to existing stories from the terminal.
- Retrieving all stories within a particular Shortcut project to review progress.
- Organizing work by associating stories with epics, iterations, and labels.
- Batch importing templates or templates-based stories to accelerate planning.
Quick Start
- Step 1: Add the Rube MCP server to Claude Code config with URL: https://rube.app/mcp
- Step 2: When prompted, authenticate your Shortcut account through the connection link provided
- Step 3: Start automating your project management workflows with natural language
Best Practices
- Prefer providing workflow_state_id over project_id, since projects are being sunset in Shortcut.
- Use the appropriate tool for the task (e.g., SHORTCUT_CREATE_STORY for new stories, SHORTCUT_CREATE_TASK for sub-tasks).
- Supply complete parameters (name, story_type, estimate, epic_id, labels, owner_ids) to avoid extra API calls.
- Leverage SHORTCUT_CREATE_MULTIPLE_STORIES for bulk imports or sprint prep.
- Always authenticate via the Rube MCP setup before issuing automation commands.
Example Use Cases
- Create a feature story called "Add dark mode support" in workflow state 500000001 with estimate 5 and label "frontend"
- Create 3 bug stories: "Login page 500 error", "Cart total rounding issue", and "Search results empty state broken"
- List all stories in project 42 with their descriptions
- Add a task "Write unit tests for dark mode toggle" to story 12345
- Add a comment to story 12345: "Reviewed the implementation -- looks good, but needs accessibility testing"