shortcut-epic-update

Update Shortcut epics via the REST API with JSON payloads.

1|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/nicksteffens/claude-config --skill shortcut-epic-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shortcut-epic-update
Source: https://github.com/nicksteffens/claude-config/tree/main/skills/shortcut-epic-update
Command: npx skills add https://github.com/nicksteffens/claude-config --skill shortcut-epic-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill updates Shortcut epics directly via the API when MCP lacks epic update support.

Core Features & Use Cases

  • Link epics to objectives
  • Change epic state or workflow state
  • Update epic name and description
  • Update epic owner

Quick Start

Use this skill to modify an epic via the Shortcut REST API. Ensure you have a workspace token and the epic ID before starting.

Frequently Asked Questions about shortcut-epic-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Shortcut epics when MCP lacks epic update support?

To update Shortcut epics without native MCP support, you can use the Shortcut REST API directly via curl to send JSON payloads that modify epic states, owners, names, and descriptions.

Can I link Shortcut epics to objectives automatically through the API?

Yes, you can link Shortcut epics to objectives by sending a structured JSON payload via curl to the Shortcut API, which directly updates the epic's objective links across workspaces.

What do I need to configure before sending API requests to update Shortcut epics?

You need a workspace-specific Shortcut API token stored in the shortcut-tokens.json file and the exact epic ID you intend to modify before making curl API requests.

How do I change the workflow state or owner of a Shortcut epic using curl?

You change a Shortcut epic's workflow state or owner by constructing a JSON payload with the new values and sending it via curl to the Shortcut REST API endpoint for that specific epic.

Does updating Shortcut epics directly via the API require JSON validation?

Yes, proper JSON handling and validation are required when updating Shortcut epics via the API to ensure the payload structure is correct before the curl request is executed.

Why use direct API calls instead of waiting for MCP to support Shortcut epic updates?

Direct API calls provide an immediate workaround for updating Shortcut epic states, owners, and descriptions without waiting for MCP to implement native epic update support.