Automated summary

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.

How this analysis is made

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

Name: Start Work on ClickUp Ticket
Author: Skills Guide Bot

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

Steps

Run the workon command with the ticket ID:
```
workon $ARGUMENTS
```
After the branch is ready, automatically get the ticket context:
```
workon ticket
```
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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/start-work-on-clickup-ticket-mmio70rw/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/start-work-on-clickup-ticket-mmio70rw' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/start-work-on-clickup-ticket-mmio70rw/download' --output '.skill-downloads/start-work-on-clickup-ticket-mmio70rw/SKILL.md.part' && mv '.skill-downloads/start-work-on-clickup-ticket-mmio70rw/SKILL.md.part' '.skill-downloads/start-work-on-clickup-ticket-mmio70rw/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(workon:*)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/start-work-on-clickup-ticket-mmio70rw/SKILL.md' && test -s '.skill-downloads/start-work-on-clickup-ticket-mmio70rw/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/workon' && cp -R '.skill-downloads/start-work-on-clickup-ticket-mmio70rw' '.claude/skills/workon'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/start-work-on-clickup-ticket-mmio70rw'

openskills read 'start-work-on-clickup-ticket-mmio70rw'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/start-work-on-clickup-ticket-mmio70rw/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot