# Sync Roadmaps with ClickUp

Teams often lose alignment when local roadmap files and ClickUp tasks drift apart. This skill provides mapping rules and sync guidance for ClickUp MCP workflows.

## Install

```bash
npx skillstore add andresnaza/clickup-integration-expert
```

## Metadata

- - Slug: andresnaza-clickup-integration-expert
- - Version: 1.0.0
- - Author: AndresNaza
- - GitHub username: AndresNaza
- - License: MIT
- - Repository: https://github.com/AndresNaza/claude-plugins/tree/main/clickup-sync/skills/clickup-integration
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: network
- - Quality score: 77
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/andresnaza-clickup-integration-expert
- - Manifest: https://skillstore.pages.dev/api/skills/andresnaza-clickup-integration-expert/manifest

## Capabilities

- Maps local epics to ClickUp tasks with an Epic type.
- Maps local milestones to ClickUp subtasks under epics.
- Documents setup for the official ClickUp MCP endpoint.
- Defines status mappings between roadmap states and ClickUp states.
- Provides basic conflict resolution rules for status, points, and title fields.

## Use Cases

- Prepare a Roadmap Sync: Set up ClickUp workspace, space, and folder mappings before the first sync.
- Review Sync Status: Check whether local epics and milestones are linked to the correct ClickUp tasks.
- Resolve Roadmap Conflicts: Apply clear ownership rules when ClickUp and local roadmap fields disagree.

## Prompt Templates

### Set Up ClickUp Sync

```
Help me configure ClickUp sync for my local roadmap. Walk me through the workspace, space, folder, and OAuth setup.
```

### Map Roadmap Items

```
Review my roadmap structure and explain how each epic and milestone should map to ClickUp tasks and subtasks.
```

### Plan a Dry Run

```
Help me plan a dry-run sync. Identify what should be pulled from ClickUp and what should be pushed from the local roadmap.
```

### Resolve Sync Conflicts

```
Analyze these roadmap and ClickUp differences. Apply the documented conflict rules and recommend the final values for status, points, and title.
```

## Limitations

- Requires a configured ClickUp MCP connection and OAuth authentication.
- Does not include executable sync scripts or API implementation code.
- Covers the documented roadmap schema only.
- Conflict rules are simple and may need project-specific changes.

## Best Practices

- Pull from ClickUp before pushing local roadmap changes.
- Use dry-run mode to preview sync changes before writing data.
- Check sync status before linking or unlinking roadmap items.

## Anti Patterns

- Do not push local changes before reviewing recent ClickUp updates.
- Do not manually edit sync mappings without verifying task identifiers.
- Do not assume conflict rules fit every team without review.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T08:54:27.241\+00:00
- - Summary: The static external-command and weak-cryptography findings are false positives caused by Markdown code fences, inline command names, and table text. The only confirmed concern is a documented setup command that adds the official ClickUp MCP endpoint and requires OAuth, which is expected for this integration.

## Stats

- - Views: 235
- - Downloads: 7
- - Favorites: 0
- - Popularity score: 0