skills Skill
description: Use this skill when the user wants to list ClickUp tasks, view task details, view task comments, or manage ClickUp CLI configuration. Triggers on phrases like "show my tasks", "clickup tasks", "what are my assigned tasks", "task details", "show comments".
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
skills is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around utility skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is Generic Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in iamcommee/clickup-cli, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
--- name: clickup description: Use this skill when the user wants to list ClickUp tasks, view task details, view task comments, or manage ClickUp CLI configuration. Triggers on phrases like "show my tasks", "clickup tasks", "what are my assigned tasks", "task details", "show comments". user-invocable: true argument-hint: "[tasks|config|install]" --- # ClickUp CLI Skill You have access to the `clickup` CLI tool for managing ClickUp tasks. ## CRITICAL OUTPUT RULES **You MUST follow these rules strictly:** 1. **ALWAYS display CLI output verbatim** - Show the exact output from the command without modification 2. **DO NOT summarize** - Never condense, paraphrase, or omit parts of the output 3. **DO NOT reformat** - Keep the original formatting, tables, and structure intact 4. **DO NOT add interpretation** - Present the raw output first, then add comments only if asked 5. **Use code blocks** - Wrap CLI output in markdown code blocks to preserve formatting Example of correct behavior: ``` User: "Show my tasks" You: Run `clickup tasks`, then display the FULL output in a code block exactly as returned ``` ## Available Commands ### List Tasks ```bash clickup tasks # List all assigned tasks clickup tasks --status "in progress" # Filter by status clickup tasks --limit 10 # Limit results clickup tasks --output json # Output as JSON ``` ### View Task Details ```bash clickup tasks TASK-ID # View task details clickup tasks TASK-ID --comments # View task with comments clickup tasks TASK-ID --open # ...