shortcut
Skill7 starsChanged 4 months agoMITView on GitHub
Manage Shortcut stories, epics, objectives, iterations, docs, labels, teams, and more using the short CLI — view, search, update, and create items for project management and issue tracking. Use when the user mentions Shortcut, references tickets or tasks in Shortcut, or when you see URLs matching `app.shortcut.com/*` (use this skill instead of WebFetch).
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- apideck-libraries/api-skillstheir own version, first seen Aug 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- apideck-libraries/api-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- ponderSkill
- review-workflowSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
When invoked with /shortcut $ARGUMENTS:
- Very specific: line 27
Verify the short CLI is installed and authenticated:
- Distinctive: line 33
If not found: Guide user through installation (see Prerequisites), then STOP
- Very specific: line 34
If found but version < 5.0.0: Warn user to upgrade (brew upgrade shortcut-cli or npm update -g @shortcut-cli/shortcut-cli)
- Distinctive: line 35
If found and >= 5.0.0: Continue to step 2
- Very specific: line 60
Create supports stories, epics, iterations, objectives, docs, and labels — see references/commands.md for each.
- Distinctive: line 62
Always quote user-provided strings and escape double quotes in input.
- Distinctive: line 67
Search results: Numbered list with ID, title, state
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Shortcut CLI Skill
Manage Shortcut stories, epics, objectives, iterations, docs, labels, teams, and more via the short CLI tool.
Instructions
When invoked with /shortcut $ARGUMENTS:
1. Check Prerequisites
Verify the short CLI is installed and authenticated:
which short && short --version- If not found: Guide user through installation (see Prerequisites), then STOP
- If found but version < 5.0.0: Warn user to upgrade (
brew upgrade shortcut-cliornpm update -g @shortcut-cli/shortcut-cli) - If found and >= 5.0.0: Continue to step 2
2. Parse $ARGUMENTS
Route based on argument pattern (in priority order):
| Pattern | Action |
| No arguments | Show help menu with available commands |
URL containing /story/<id> | Extract numeric ID, run short story <id> |
URL containing /epic/<id> | Extract numeric ID, run short epic view <id> |
search <text> | Run short search -t "<text>" |
my | Run short search -o me |
list | Run short search (no filters) |
create | Ask for entity type + details, run create command (see references/commands.md ## Create) |
objectives [...] | Route to objectives commands (see references/commands.md ## Objectives) |
teams [...] | Route to teams commands (see references/commands.md ## Teams) |
iterations [...] | Route to iterations commands (see references/commands.md ## Iterations) |
docs [...] | Route to docs commands (see references/commands.md ## Docs) |
labels [...] | Route to labels commands (see references/commands.md ## Labels) |
workflows | Run short workflows |
projects | Run short projects |
story <id> <subcommand> | Route to story subcommands: history, comments, tasks, relations (see references/commands.md ## Stories) |
| Numeric value | Treat as story ID, run short story <id> |
Create supports stories, epics, iterations, objectives, docs, and labels — see references/commands.md for each.
Always quote user-provided strings and escape double quotes in input.
3. Present Results
- Story/epic details: Show ID, title, state, owner, description, URL
- Search results: Numbered list with ID, title, state
- Creation: Success message with new item URL
- Lists (teams, labels, iterations, etc.): Clean formatted table
Suggest relevant follow-up actions after presenting results.
4. Handle Errors
| Error | Detection | Response |
| CLI not found | which short empty | Show installation instructions, do NOT auto-install |
| Auth failure | "unauthorized" or "invalid token" | Guide user to run short install |
| Not found | "not found" in output | Confirm ID, suggest search |
| Network error | Timeout or connection error | Ask user to check connection |
| Node.js version | ESM/import errors or "unsupported engine" | User needs Node.js >= 20.19.0 |
Prerequisites
- Node.js >= 20.19.0 (required by shortcut-cli v5+)
# Install via Homebrew (preferred)
brew install shortcut-cli
# Or via npm (fallback)
npm install -g @shortcut-cli/shortcut-cli
# Verify version (expect >= 5.0.0)
short --version
# Authenticate
short install
# Or: export SHORTCUT_API_TOKEN="your-api-token"Reference
| Task | Reference |
| CLI commands (stories, epics, objectives, iterations, docs, labels, teams, search, create, API) | references/commands.md — use ## Section headers to find specific command families |
| Shortcut API spec | references/shortcut.swagger.json |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

