Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

ClickUp Automation

skill · claude-office-skills/skillsMIT licenceAudited 31 Oct 2026 · source 79d91524ef4c

★ 555pushed 273 days agoversion 1.0.0
✓SAFEGrade B · 89/100 · 31 Oct 2026 · 79d9152
555repo stars · whole claude-office-skills/skills

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 79d91524ef4c and found no filesystem, network or shell access and no hard-coded secrets. What it does: Automate ClickUp workspace management, task workflows, time tracking, and team productivity

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “ClickUp Automation (claude-office-skills/skills)”. Retrieved 31 Oct 2026. https://modelsatlas.com/skills/claude-office-skills/clickup-automation

Trust audit

Audit 0.4.1 · source read 31 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 79d91524ef4c · 31 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publisherclaude-office-skills GitHub organizationOwner of the repository this skill is read from
  • Source folderclaude-office-skills/skills/clickup-automationThe exact folder we audited
  • LicenceMITAs the repository states it
  • Commit pinned for this verdict79d91524ef4cA new audit runs when the source changes
  • Repository statusNot archivedLast push 273 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Automate ClickUp workspace management, task workflows, time tracking, and team productivity

---
name: ClickUp Automation
description: Automate ClickUp workspace management, task workflows, time tracking, and team productivity
version: 1.0.0
author: Claude Office Skills
category: project-management
tags:
  - clickup
  - tasks
  - productivity
  - project-management
  - automation
department: operations
models:
  - claude-3-opus
  - claude-3-sonnet
  - gpt-4
mcp:
  server: project-mcp
  tools:
    - clickup_task
    - clickup_list
    - clickup_space
    - clickup_automation
capabilities:
  - Task management
  - Workflow automation
  - Time tracking
  - Goal tracking
input:
  - Task details
  - Space configurations
  - Automation rules
  - Time entries
output:
  - Created/updated tasks
  - Workspace reports
  - Time reports
  - Goal progress
languages:
  - en
related_skills:
  - asana-automation
  - jira-automation
  - monday-automation
---

# ClickUp Automation

Comprehensive skill for automating ClickUp workspace and task management.

## Core Concepts

### Workspace Hierarchy

```
CLICKUP HIERARCHY:
┌─────────────────────────────────────────────────────────┐
│ 🏢 WORKSPACE                                            │
├─────────────────────────────────────────────────────────┤
│   ├── 📁 SPACE: Engineering                             │
│   │   ├── 📂 FOLDER: Q1 Projects                       │
│   │   │   ├── 📋 LIST: Feature Development             │
│   │   │   │   ├── ✅ Task: Implement Auth              │
│   │   │   │   │   └── ☑️ Subtask: OAuth setup          │
│   │   │   │   └── ✅ Task: Build API                   │
│   │   │   └── 📋 LIST: Bug Fixes                       │
│   │   └── 📂 FOLDER: Infrastructure                    │
│   │                                                     │
│   ├── 📁 SPACE: Marketing                               │
│   │   └── 📋 LIST: Content Calendar                    │
│   │                                                     │
│   └── 📁 SPACE: Operations                              │
└─────────────────────────────────────────────────────────┘
```

### Task Structure

```yaml
task_structure:
  required:
    name: "{{task_name}}"
    list_id: "{{list_id}}"
    
  optional:
    description: "{{description}}"
    assignees: ["user_id_1", "user_id_2"]
    tags: ["feature", "priority"]
    status: "Open"
    priority: 2  # 1=Urgent, 2=High, 3=Normal, 4=Low
    due_date: "2024-01-20"
    start_date: "2024-01-15"
    time_estimate: 28800000  # milliseconds (8 hours)
    
  custom_fields:
    - id: "field_id"
      value: "custom_value"
      
  checklists:
    - name: "Acceptance Criteria"
      items:
        - name: "Requirement 1"
          resolved: false
```

## Automation Rules

### Built-in Automations

```yaml
automations:
  - name: auto_assign_on_create
    trigger:
      type: task_created
      list_id: "list_123"
    conditions:
      - tag_contains: "design"
    actions:
      - add_assignee: "design_lead_id"
      - set_priority: high
      
  - name: due_date_reminder
    trigger:
      type: due_date
      before: 1_day
    actions:
      - send_notification:
          to: assignees
          message: "Task due tomorrow: {{task.name}}"
      - add_tag: "due-soon"
      
  - name: status_change_workflow
    trigger:
      type: status_changed
      to: "In Review"
    actions:
      - remove_assignee: "{{previous_assignee}}"
      - add_assignee: "reviewer_id"
      - add_comment: "Ready for review @reviewer"
      
  - name: complete_parent_task
    trigger:
      type: all_subtasks_done
    actions:
      - set_status: "Complete"
      - add_comment: "All subtasks completed ✓"
```

### Advanced Automations

```yaml
advanced_rules:
  - name: sprint_rollover
    trigger:
      type: schedule
      cron: "0 0 * * 1"  # Monday midnight
    conditions:
      - status_not: "Complete"
      - due_date_passed: true
    actions:
      - move_to_list: "{{next_sprint_list}}"
      - update_due_date: "+7 days"
      - add_comment: "Rolled over from previous sprint"
      
  - name: escalation_workflow
    trigger:
      type: task_blocked
      duration: 48_hours
    actions:
      - set_priority: urgent
      - notify: manager
      - add_watcher: "manager_id"
      - add_tag: "escalated"
```

## Views & Layouts

### View Types

```yaml
views:
  list_view:
    type: list
    group_by: status
    sort_by: priority
    columns:
      - name
      - assignees
      - due_date
      - priority
      - time_estimate
      
  board_view:
    type: board
    group_by: status
    card_fields:
      - assignees
      - due_date
      - tags
      - subtasks_count
      
  calendar_view:
    type: calendar
    date_field: due_date
    color_by: priority
    
  timeline_view:
    type: timeline
    start_field: start_date
    end_field: due_date
    dependencies: true
    
  workload_view:
    type: workload
    capacity_field: time_estimate
    group_by: assignee
```

### Dashboard Widgets

```yaml
dashboard:
  widgets:
    - type: sprint_burndown
      list_id: "current_sprint"
      
    - type: workload
      space_id: "engineering"
      period: this_week
      
    - type: task_status
      filter:
        assignee: me
        
    - type: time_tracked
      group_by: project
      period: this_month
      
    - type: goals_progress
      folder_id: "q1_goals"
```

## Time Tracking

### Time Entry Configuration

```yaml
time_tracking:
  settings:
    billable_default: true
    rounding: 15_minutes
    require_description: false
    
  entry:
    task_id: "task_123"
    start: "2024-01-15T09:00:00Z"
    end: "2024-01-15T11:30:00Z"
    duration: 9000000  # 2.5 hours in ms
    billable: true
    description: "Development work"
    
  reports:
    - type: user_summary
      period: this_week
      group_by: task
      
    - type: project_summary
      period: this_month
      group_by: user
```

### Time Reports Dashboard

```
TIME TRACKING - THIS WEEK
═══════════════════════════════════════

TOTAL: 32h 45m

BY PROJECT:
Feature Dev   ██████████████

Excerpt, first 6,009 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 79d9152

Download folder ↗
git clone https://github.com/claude-office-skills/skills
git -C skills checkout 79d91524ef4c

The author documents no install command, so this uses the repository directly. Our verdict covers commit 79d91524ef4c only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 79d91524ef4c

Questions about ClickUp Automation

What does the ClickUp Automation skill do?
A curated collection of practical Claude Skills for real-world office tasks
Is ClickUp Automation safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can ClickUp Automation access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (79d91524ef4c), read on 2026-10-31. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.