ClickUp Skill

Name: ClickUp Skill
Availability: InStock
Author: topastro73-it

Create and update ClickUp Epics and Tasks from product specs via MCP.

9|3|Updated Jun 1, 2026

Search Tags:#automation #integration #roadmap #task-management #clickup #epic

Ready to run

npx skills add https://github.com/topastro73-it/founder-os --skill clickup-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ClickUp Skill
Source: https://github.com/topastro73-it/founder-os/tree/main/.skills/clickup
Command: npx skills add https://github.com/topastro73-it/founder-os --skill clickup-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates and coordinates ClickUp actions through MCP for agent-based workflows in founder-os. It ensures tasks, epics, and roadmaps are created, linked, and updated from repository-driven inputs, reducing manual overhead and inconsistencies.

Core Features & Use Cases

Create and link Epics and Tasks from product specs, roadmaps, and approvals, ensuring traceability via tags and frontmatter.
Read and sync ClickUp boards with repository state to reflect progress and blockers.
Enforce naming conventions, frontmatter requirements, and governance rules to maintain alignment between repo and ClickUp.

Quick Start

Invoke a command such as /pm clickup sync-spec company/product/specs/prd-sample.md to begin synchronizing a new spec with ClickUp.

Frequently Asked Questions about ClickUp Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I synchronize tasks between ClickUp and my repository?▼

Yes, you can create ClickUp Epics and Tasks directly from product specs and roadmaps. The skill automates this through MCP, parsing repository-driven inputs to generate linked structures while enforcing naming conventions and governance rules for consistency.

How does MCP automate ClickUp task management workflows?▼

MCP automates ClickUp task management by coordinating actions through agent-based workflows. It reads repository state to reflect progress and blockers, enforces workspace scoping, and requires explicit approvals to safeguard task integrity during synchronization.

Do I need explicit approvals to update ClickUp boards from my repo?▼

Yes, explicit approvals are required to update ClickUp boards from your repository. The skill enforces this governance rule alongside workspace scoping and formatting requirements to maintain strict alignment between repository changes and ClickUp task integrity.

What's the best way to sync a product spec with ClickUp?▼

The best way to sync a product spec with ClickUp is invoking a command like /pm clickup sync-spec followed by your spec file path. This triggers the skill to apply formatting rules, generate tags, and link the spec to your ClickUp workspace.

Can I enforce naming conventions and frontmatter requirements when syncing ClickUp tasks?▼

Yes, the skill enforces naming conventions and frontmatter requirements when syncing ClickUp tasks. It applies these governance rules during the creation and updating of Epic and Task structures to maintain alignment between your repository and ClickUp workspace.