Skills Guide

Start Work on ClickUp Ticket

VerifiedCaution

Use the "workon" command with a ticket ID to create or checkout a branch for a ClickUp ticket. After the branch is ready, it automatically retrieves ticket context (title, description, acceptance criteria) to help you understand the task. Helpful when starting work on a new ClickUp ticket.

Sby Skills Guide Bot
ProductivityBeginner
506/2/2026
Claude Code
#clickup#ticket-management#branch#workflow

Recommended for

Claude CodeProduct managerSolo / indie hackerProductivity

Our review

Automates starting work on a ClickUp ticket by creating or switching to the appropriate branch and fetching ticket context.

Strengths

  • Automatically fetches ticket context (title, description, acceptance criteria).
  • Handles branch creation or checkout seamlessly.
  • Integrates with ClickUp to provide task details.

Limitations

  • Requires the `workon` command to be set up locally.
  • May prompt for user input on branch conflicts.
  • Only works with ClickUp.
When to use it

Use this skill when you need to start working on a ClickUp ticket and want to quickly set up the branch and get context.

When not to use it

Avoid if you are not using ClickUp or if the `workon` command is not available in your environment.

Security analysis

Caution
Quality score85/100

The skill executes a shell command with user input as an argument. While the intended operation is benign (managing git branches and fetching ClickUp context), the reliance on proper input sanitization in the `workon` script creates a moderate risk of command injection. The restricted Bash permission mitigates some risk, but the wildcard scope still leaves room for potential abuse if the `workon` toolset includes unsafe operations.

Findings
  • •User-provided ticket ID is passed directly to a shell command (`workon $ARGUMENTS`). If the `workon` script does not sanitize input, there is a risk of command injection (e.g., ticket ID containing `;`, `|`, or backticks).
  • •The skill grants access to Bash with a wildcard permission (`workon:*`), which could allow execution of any command prefixed with `workon`. If the `workon` tool is extended or misused, it might expose unintended functionality.

Examples

Standard usage
workon 86b7x5453
Different ticket
workon 86b7x1234

name: workon description: Start work on a ClickUp ticket. Use when the user says "workon" followed by a ticket ID (e.g., "workon 86b7x5453"). argument-hint: <ticket-id> allowed-tools: Bash(workon:*)

Start Work on a ClickUp Ticket

When the user provides a ticket ID, run the workon command to create or checkout the branch for that ticket.

Steps

  1. Run the workon command with the ticket ID:

    workon $ARGUMENTS

  2. After the branch is ready, automatically get the ticket context:

    workon ticket

  3. Use the ticket information (title, description, acceptance criteria) to understand what the user is trying to accomplish.

Notes

  • The workon <ticket-id> command may prompt for user input if the branch already exists (to choose: checkout, recreate, or cancel)
  • If the branch doesn't exist, it creates it automatically
  • Always run workon ticket after to bring context into the session
Related skills

Task Prioritizer

Productivity

Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.

claudechatgptbeginner
241
67
615
Admin

Weekly Status Report Generator

Productivity

Generate structured and concise weekly status reports.

Claude CodeCursorWindsurf+1beginner
234
78
635
Admin

Daily Standup Report

Productivity

Generates structured and concise daily standup reports.

claudeCursorWindsurfbeginner
178
45
483
Admin