clickup-ticket-manager_skill

This skill creates high-quality ClickUp tickets from user input, including a clear title and 2-3 sentence description with context and purpose.
  • Python

2.5k

GitHub Stars

4

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill clickup-ticket-manager

  • _meta.json277 B
  • clup.sh6.5 KB
  • README.md5.4 KB
  • SKILL.md2.0 KB

Overview

This skill creates well-formed ClickUp tasks from short user prompts using a simple CLI wrapper. It converts vague requests into concise titles and 2–3 sentence descriptions that capture what, why, and context. It returns the ClickUp URL after creating the task so users can review or click through.

How this skill works

The tool reads environment variables for API key and default list ID and issues ClickUp API calls to create tasks. It enforces title and description quality rules, requiring a short actionable title and a 2–3 sentence minimum description that covers what to do, why it matters, and relevant context. If the input is ambiguous, the tool prompts for clarification before creating a ticket.

When to use it

  • You need to turn a short request into a formal ClickUp task quickly.
  • You want consistent, contextual task descriptions for engineering or ops work.
  • You prefer a CLI workflow or want to script task creation.
  • You need default list, tags, or status applied automatically.
  • You need to include priority or tags when creating operational tickets.

Best practices

  • Provide at least a sentence of context when possible (system, server, user impact).
  • Use clear, actionable titles under 10 words.
  • If the request is vague, prompt for missing info before creation to avoid back-and-forth.
  • Set CLICKUP_API_KEY and CLICKUP_DEFAULT_LIST_ID in your environment for reliable operation.
  • Use --priority and --tags flags to reflect urgency and routing needs.

Example use cases

  • Create a task to open a firewall port between specific servers, including IPs and justification.
  • Add a reminder task to patch a production server with why the patch is needed and what systems it affects.
  • File a bugfix task with steps to reproduce, expected behavior, and the impacted service.
  • Create a feature task that describes the requested change, its business value, and affected components.
  • Script bulk task creation in CI/CD flows by calling the CLI with generated titles and descriptions.

FAQ

Set CLICKUP_API_KEY and CLICKUP_DEFAULT_LIST_ID. Optional defaults include CLICKUP_DEFAULT_TAG and CLICKUP_DEFAULT_STATUS.

What happens if my input is too vague?

The tool will ask for clarification before creating the task to ensure the description meets the 2–3 sentence minimum and includes context.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational