Shortcut Automation
by ComposioHQShortcut Automation helps Claude Code manage Shortcut projects through Rube MCP: create and list stories, add tasks and comments, batch-create work, and set estimates, labels, epics, iterations, and workflow states.
Score: 74/100. This is an acceptable listing candidate for directory users who already use Shortcut and are comfortable configuring the Rube MCP server; it provides enough workflow and tool guidance to help an agent act more reliably than a generic prompt, but it is limited by minimal repository support material and reliance on external IDs/docs.
- Clear purpose and trigger surface: automates Shortcut project management tasks such as creating stories, managing tasks/comments, tracking epics, and organizing workflows from natural language.
- Provides explicit setup steps for the required Rube MCP server and Shortcut authentication.
- Names concrete Shortcut tools such as SHORTCUT_CREATE_STORY and includes example prompts plus key parameter guidance, reducing guesswork compared with a generic prompt.
- No bundled scripts, references, README, or install command beyond manual Rube MCP setup, so adoption depends on external MCP configuration and docs.
- Examples require workspace-specific Shortcut IDs such as workflow_state_id, epic_id, or iteration_id, but the evidence does not show strong discovery/error-handling guidance for finding or validating them.
Overview of Shortcut Automation skill
What Shortcut Automation does
Shortcut Automation is a Claude Code skill for managing Shortcut project work through natural language while using the Rube MCP server. It helps you create stories, batch-create work items, add tasks and comments, list existing stories, and navigate Shortcut workflow states without switching away from your development environment.
Best fit for project management teams
This Shortcut Automation skill is best for engineers, tech leads, product managers, and delivery teams who already use Shortcut and want faster project-management operations from Claude Code. It is especially useful when turning planning notes, bug reports, sprint goals, or implementation decisions into structured Shortcut stories with estimates, labels, epics, iterations, and workflow states.
What makes it different from a generic prompt
A generic prompt can draft ticket text, but it cannot reliably act inside Shortcut. This skill is designed around Shortcut-specific actions such as SHORTCUT_CREATE_STORY, with parameters like workflow_state_id, story_type, estimate, epic_id, iteration_id, and labels. The main value is not just writing better tickets; it is converting natural language into actionable Shortcut operations through an authenticated MCP connection.
How to Use Shortcut Automation skill
Shortcut Automation install and setup context
To use Shortcut Automation, install the skill in your Claude skills environment, for example:
npx skills add ComposioHQ/awesome-claude-skills --skill "Shortcut Automation"
Then configure the required MCP dependency. The skill requires the Rube MCP server, so add https://rube.app/mcp to your Claude Code MCP configuration and authenticate your Shortcut account when prompted. If authentication is incomplete, Claude may understand the request but fail when trying to create or retrieve Shortcut data.
Inputs the skill needs for reliable actions
Shortcut Automation usage improves when you provide structured Shortcut details instead of only a vague goal. For story creation, include the title, story type, workflow state, description, estimate, labels, epic, and iteration when available. The upstream skill recommends workflow_state_id over project_id, so collect the IDs your workspace uses before asking Claude to create production work items.
Weak prompt:
Create tickets for the onboarding work.
Stronger prompt:
Use Shortcut Automation to create three feature stories for onboarding. Put them in workflow_state_id 500000001, estimate each at 3 points, label them "onboarding" and "frontend", and attach them to epic_id 12345. Include acceptance criteria for each story.
Suggested workflow for first-time use
Start with a read-only or low-risk action before creating many records. Ask Claude to list or inspect existing Shortcut stories if your MCP setup supports it, then create one test story with a clear title and label. After confirming the output lands in the right workflow state, move to batch creation. For larger planning sessions, first ask Claude to draft the proposed stories in markdown, review names and estimates, then instruct it to create them in Shortcut.
Repository files to read first
This skill is compact: the key file is composio-skills/shortcut-automation/SKILL.md. Read the Setup section for the Rube MCP requirement, then the Core Workflows section for supported Shortcut operations and example phrasing. There are no additional rules/, resources/, references/, or scripts in the current skill folder, so most implementation expectations come directly from SKILL.md and the Composio Shortcut toolkit documentation linked there.
Shortcut Automation skill FAQ
Is Shortcut Automation for Project Management or coding?
Shortcut Automation for Project Management is its main use case. It does not write application code or manage your repository by itself. It helps translate planning and delivery decisions into Shortcut records, comments, tasks, estimates, labels, workflow movement, and related project-tracking actions.
Do I need Shortcut admin access?
You need a Shortcut account with permission to perform the actions you request. Creating stories, adding comments, or changing workflow placement depends on your Shortcut workspace permissions and the authenticated Rube MCP connection. If Claude cannot complete an action, check account access, MCP authentication, and whether the provided IDs exist in the workspace.
When should I not use this skill?
Do not use it as the only review step for large backlog changes, sensitive roadmap changes, or bulk updates that could disrupt a live Shortcut workspace. For high-impact operations, ask Claude to draft a plan first, verify the story list manually, and then create or update items in smaller batches.
How is this better than writing Shortcut tickets manually?
Manual ticket entry is often safer for one-off work, but slower for repetitive planning. Shortcut Automation is most useful when you have many related stories, a consistent labeling scheme, recurring workflow states, or meeting notes that need to become structured Shortcut work items quickly.
How to Improve Shortcut Automation skill
Improve Shortcut Automation results with better context
The fastest way to improve Shortcut Automation output is to provide your workspace conventions. Include valid workflow state IDs, label names, epic IDs, iteration IDs, estimate scale, story-type rules, and examples of a well-written story in your team’s style. Claude can infer formatting, but it should not guess IDs or ownership rules for production work.
Prevent common failure modes
Common problems include missing workflow state IDs, ambiguous story types, duplicate tickets, incorrect labels, and over-broad batch creation. Reduce these by asking Claude to summarize the intended Shortcut changes before execution. For example: Before creating anything, show a table with title, type, estimate, labels, epic_id, iteration_id, and workflow_state_id.
Iterate after the first output
After Claude drafts or creates stories, review for acceptance criteria, dependencies, and scope boundaries. Ask follow-up prompts such as: Split any story larger than 5 points, Add QA tasks to each bug, Rewrite descriptions using Given/When/Then acceptance criteria, or Move backend-only items to the backend label. These iterations improve project clarity more than asking for perfect tickets in one prompt.
Extend the skill for your team’s workflow
If your team relies heavily on Shortcut, consider adding local guidance around naming conventions, default labels, estimation rules, and safe batch limits. A lightweight team-specific wrapper prompt can make the Shortcut Automation guide more reliable by telling Claude which workflow states are safe, which epics are active, and when it must ask for confirmation before changing existing work.