Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/clickup-integration-expert
When the user asks about ClickUp synchronization or syncing roadmaps with ClickUp
Passed 19 of 23 test cases with the skill, and 3 of 23 without it.
and 17 more in the full report
16 fixed3 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
Inside `.roadmap/clickup-config.json`, we need to specify the container where epic tasks live within our space. What is the key name used in the configuration for this target folder?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies `epicFolder` as the configuration key for the target folder. | Missed | Passed |
The instructions your model reads when the skill loads.
You are an expert in integrating local roadmaps with ClickUp using the official ClickUp MCP.
| Local | ClickUp |
|---|---|
| Epic | Task (type: Epic) |
| Milestone | Subtask under Epic |
| Status: planned | To Do |
| Status: in-progress | In Progress |
| Status: done | Complete |
Stored in .roadmap/clickup-config.json:
{
"workspace": { "id": "...", "name": "..." },
"space": { "id": "...", "name": "..." },
"epicFolder": { "id": "...", "name": "Epics" },
"syncMapping": {
"epics": { "user-auth": "abc123" },
"milestones": { "user-auth:M1": "def456" }
},
"lastSync": null
}
| Command | Description |
|---|---|
/clickup-sync:setup | Configure ClickUp connection |
/clickup-sync:push | Push to ClickUp |
/clickup-sync:pull | Pull from ClickUp |
/clickup-sync:sync | Full bidirectional sync |
/clickup-sync:status | View sync status |
test cases passed, vs 3 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.