Shortcut Automation
Automate project management workflows in Shortcut -- create stories, manage tasks, track epics, and organize workflows through natural language commands.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Shortcut Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate project management workflows in Shortcut -- create stories, manage tasks, track epics, and organize workflows through natural language commands.
When not to use it
Skip Shortcut Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/shortcut-automation # Save SKILL.md to ~/.claude/skills/shortcut-automation/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/shortcut-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/shortcut-automation/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Shortcut Automation skill for this task: Use Shortcut Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 76/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 80/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Shortcut 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](https://composio.dev/toolkits/shortcut)
---
## Setup
1. Add the Rube MCP server to your Claude Code config with URL: `https://rube.app/mcp` 2. When prompted, authenticate your Shortcut account through the connection link provided 3. 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 title - `workflow_state_id` -- the workflow state to place the story in (recommended over `project_id`) - `story_type` -- `"feature"`, `"bug"`, or `"chore"` - `description` -- story body/description - `estimate` -- numeric point estimate (or null for unestimated) - `epic_id` -- associate with an epic - `iteration_id` -- associate with an iteration - `labels` -- array of label objects with `name` (and optional `color`, `description`) - `owner_ids` -- array of member UUIDs to assign - `deadline` -- due date in ISO 8601 format - `tasks` -- inline task array with `description` and optional `complete`, `owner_ids` - `comments` -- inline comment array with `text` - `story_links` -- link stories with `verb` (`"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 `stories` array where each element follows the same schema as `SHORTCUT_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: true` to 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 ID - `description` (required) -- the task description - `complete` -- boolean, defaults to false - `owner_ids` -- array of member UUIDs to assign the task - `external_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 ID - `text` (required) -- the comment body - `author_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_WORKFLOWS` returns all workflows with their states (IDs, names, types) - `SHORTCUT_LIST_PROJECTS` returns all projects with their attributes - Use these to discover valid `workflow_state_id` and `project_id` values before creating stories
---
## Known Pitfalls
- **`workflow_state_id` vs `project_id`:** `SHORTCUT_CREATE_STORY` requires exactly one of these. Providing both or neither causes a rejection. Prefer `workflow_state_id` since Projects are being sunset. - **Projects are being sunset:** Shortcut is deprecating Projects in favor of workflow-based organization. Use `workflow_state_id` for new stories. - **Label creation is inline:** Labels in the `labels` array are created on-the-fly if they do not exist. The `name` field is required for each label object. - **Story type defaults:** If `story_type` is omitted, it defaults to `"feature"`. Always set it explicitly for bugs and chores. - **Batch limits:** `SHORTCUT_CREATE_MULTIPLE_STORIES` processes 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_to` positioning:** The `move_to` field (`"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](https://composio.dev)*
Intended uses
- Use Shortcut Automation when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.