โ† All skills
Tencent SkillHub ยท Developer Tools

Shortcut Epic and Story skill

Access and manage Shortcut.com (formerly Clubhouse) project management. Use when the user asks to: list stories, view backlog, search issues, check epics, up...

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Access and manage Shortcut.com (formerly Clubhouse) project management. Use when the user asks to: list stories, view backlog, search issues, check epics, up...

โฌ‡ 0 downloads โ˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
references/create-stories.md, SKILL.md

Validation

  • Use the Yavira download entry.
  • Review SKILL.md after the package is downloaded.
  • Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. Paste one of the prompts below and point your agent at the extracted folder.
New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
1.0.2

Documentation

ClawHub primary doc Primary doc: SKILL.md 20 sections Open source page

Shortcut.com Skill ๐ŸŽฏ

Read and write Shortcut.com stories, epics, and workflows via the REST API v3.

Auth Setup

Token is stored at ~/.openclaw/secrets/shortcut (mode 600, readable only by your user). SHORTCUT_API_TOKEN=$(cat ~/.openclaw/secrets/shortcut 2>/dev/null) BASE="https://api.app.shortcut.com/api/v3" If empty, ask the user for their API token, then save it: mkdir -p ~/.openclaw/secrets echo -n "<token>" > ~/.openclaw/secrets/shortcut && chmod 600 ~/.openclaw/secrets/shortcut Generate a token at app.shortcut.com โ†’ Settings โ†’ API Tokens. Shortcut tokens have full member-level access โ€” no scope restriction is available. Rotate or delete the token at any time from the same settings page. If you prefer not to persist the token on disk, skip saving and export it for the session only: export SHORTCUT_API_TOKEN="<token>"

โš ๏ธ JSON Construction Rule

Always use jq -n --arg / --argjson to build request bodies. Never interpolate user-supplied values directly into shell strings โ€” this prevents shell injection from values containing quotes, backticks, or $(). # โœ… Safe โ€” jq handles all escaping DATA=$(jq -n --arg name "$TITLE" --arg desc "$DESCRIPTION" \ '{name: $name, description: $desc}') curl -s -X POST -H "Shortcut-Token: $SHORTCUT_API_TOKEN" \ -H "Content-Type: application/json" -d "$DATA" "$BASE/stories" # โŒ Unsafe โ€” never do this curl ... -d "{\"name\": \"$TITLE\"}"

Get a Story

curl -s -H "Shortcut-Token: $SHORTCUT_API_TOKEN" "$BASE/stories/<id>" | \ jq '{id, name, story_type, description, workflow_state_id, estimate, epic_id, labels: [.labels[].name]}' Strip the sc- prefix from IDs (use the number only).

Search Stories

curl -s -H "Shortcut-Token: $SHORTCUT_API_TOKEN" \ "$BASE/search/stories?$(jq -rn --arg q "$QUERY" 'query=\($q|@uri)&page_size=10')" | \ jq '.data[] | {id, name, story_type, estimate}'

List My Stories

ME=$(curl -s -H "Shortcut-Token: $SHORTCUT_API_TOKEN" "$BASE/member" | jq -r '.id') curl -s -H "Shortcut-Token: $SHORTCUT_API_TOKEN" \ "$BASE/search/stories?owner_id=${ME}&page_size=25" | \ jq '.data[] | {id, name, story_type, workflow_state_id}'

List Workflows & States

curl -s -H "Shortcut-Token: $SHORTCUT_API_TOKEN" "$BASE/workflows" | \ jq '.[] | {workflow: .name, states: [.states[] | {id, name, type}]}'

List Epics

curl -s -H "Shortcut-Token: $SHORTCUT_API_TOKEN" "$BASE/epics" | \ jq '.[] | {id, name, state, total_stories: .stats.num_stories_total}'

Get Epic Stories

curl -s -H "Shortcut-Token: $SHORTCUT_API_TOKEN" "$BASE/epics/<epic_id>/stories" | \ jq '.[] | {id, name, story_type, workflow_state_id, estimate}'

List Teams (Groups)

curl -s -H "Shortcut-Token: $SHORTCUT_API_TOKEN" "$BASE/groups" | \ jq '[.[] | {id, name, mention_name}]'

Writing

All write operations build JSON with jq -n --arg to safely handle user-supplied strings.

Create Story

DATA=$(jq -n \ --arg name "$STORY_TITLE" \ --arg description "$STORY_DESCRIPTION" \ --arg story_type "$STORY_TYPE" \ --argjson estimate "$ESTIMATE" \ --argjson workflow_state_id "$STATE_ID" \ --arg group_id "$GROUP_ID" \ --argjson epic_id "$EPIC_ID" \ '{name: $name, description: $description, story_type: $story_type, estimate: $estimate, workflow_state_id: $workflow_state_id, group_id: $group_id, epic_id: $epic_id}') curl -s -X POST \ -H "Shortcut-Token: $SHORTCUT_API_TOKEN" \ -H "Content-Type: application/json" \ -d "$DATA" "$BASE/stories" | jq '{id, name, app_url}' Story types: feature, bug, chore To add labels, extend the jq expression: DATA=$(jq -n --arg name "$TITLE" --arg label "mobile" \ '{name: $name, labels: [{name: $label}]}')

Create Epic

DATA=$(jq -n \ --arg name "$EPIC_TITLE" \ --arg description "$EPIC_DESCRIPTION" \ --arg group_id "$GROUP_ID" \ '{name: $name, description: $description, group_id: $group_id}') curl -s -X POST \ -H "Shortcut-Token: $SHORTCUT_API_TOKEN" \ -H "Content-Type: application/json" \ -d "$DATA" "$BASE/epics" | jq '{id, name, app_url}'

Update Story (state, estimate, title, etc.)

DATA=$(jq -n --argjson state "$NEW_STATE_ID" '{workflow_state_id: $state}') curl -s -X PUT \ -H "Shortcut-Token: $SHORTCUT_API_TOKEN" \ -H "Content-Type: application/json" \ -d "$DATA" "$BASE/stories/$STORY_ID" | jq '{id, name, workflow_state_id}'

Add Comment

DATA=$(jq -n --arg text "$COMMENT_TEXT" '{text: $text}') curl -s -X POST \ -H "Shortcut-Token: $SHORTCUT_API_TOKEN" \ -H "Content-Type: application/json" \ -d "$DATA" "$BASE/stories/$STORY_ID/comments" | jq '{id, text}'

Wire Story Dependencies (blocker links)

DATA=$(jq -n \ --argjson object_id "$BLOCKED_ID" \ --argjson subject_id "$BLOCKER_ID" \ '{object_id: $object_id, subject_id: $subject_id, verb: "blocks"}') curl -s -X POST \ -H "Shortcut-Token: $SHORTCUT_API_TOKEN" \ -H "Content-Type: application/json" \ -d "$DATA" "$BASE/story-links" | jq '{id, verb}'

Workflow State Reference

Common default state IDs (verify with the workflows endpoint for your workspace): StateTypical IDBacklog500000008Ready for Development500000007In Development500000006Ready for Review500000010Completed500000011 Always confirm state IDs by calling /workflows โ€” they vary per account.

Bulk Story Creation

For creating full epics with multiple dependent stories, see references/create-stories.md.

Display Format

Stories: ๐ŸŽฏ sc-1234 โ€” User Authentication Flow [feature, 5pts] Status: In Development | Epic: Auth & Onboarding Labels: backend, mobile > Users should be able to log in with email/password... Backlog list (table format): | ID | Story | Type | Pts | State | |---------|--------------------------|---------|-----|---------| | sc-1234 | User Auth Flow | feature | 5 | In Dev | | sc-1235 | Fix password reset email | bug | 2 | Backlog |

Tips

Always check for API token before making requests Strip sc- prefix from story IDs for API calls Labels are auto-created by Shortcut if they don't exist โ€” safe to pass new label names Rate limit: 200 req/min โ€” not a concern in normal usage For exact story lookup always use /stories/<id> directly, not search

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
2 Docs
  • SKILL.md Primary doc
  • references/create-stories.md Docs