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

Agent skill · Audited from source

Asana Automation

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

★ 542pushed 269 days agoversion 1.0.0
✓SAFEGrade B · 89/100 · 28 Oct 2026 · 79d9152
542repo 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 Asana project management workflows, task tracking, team collaboration, and reporting

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Asana Automation (claude-office-skills/skills)”. Retrieved 28 Oct 2026. https://modelsatlas.com/skills/claude-office-skills/asana-automation

Trust audit

Audit 0.4.1 · source read 28 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 · 28 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/asana-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 269 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 Asana project management workflows, task tracking, team collaboration, and reporting

---
name: Asana Automation
description: Automate Asana project management workflows, task tracking, team collaboration, and reporting
version: 1.0.0
author: Claude Office Skills
category: project-management
tags:
  - asana
  - tasks
  - project-management
  - collaboration
  - automation
department: operations
models:
  - claude-3-opus
  - claude-3-sonnet
  - gpt-4
mcp:
  server: project-mcp
  tools:
    - asana_create_task
    - asana_update_task
    - asana_search
    - asana_sections
capabilities:
  - Task creation and management
  - Project automation
  - Team workload tracking
  - Custom field workflows
input:
  - Task details
  - Project configurations
  - Workflow rules
  - Team assignments
output:
  - Created/updated tasks
  - Project reports
  - Workload views
  - Timeline updates
languages:
  - en
related_skills:
  - jira-automation
  - monday-automation
  - notion-automation
---

# Asana Automation

Comprehensive skill for automating Asana project management and team collaboration.

## Core Workflows

### 1. Task Management Pipeline

```
TASK LIFECYCLE:
┌─────────────────┐
│   New Request   │
└────────┬────────┘
         ▼
┌─────────────────┐
│   Triage &      │
│   Prioritize    │
└────────┬────────┘
         ▼
┌─────────────────┐
│   Assign &      │
│   Schedule      │
└────────┬────────┘
         ▼
┌─────────────────┐
│   In Progress   │
└────────┬────────┘
         ▼
┌─────────────────┐
│   Review        │
└────────┬────────┘
         ▼
┌─────────────────┐
│   Complete      │
└─────────────────┘
```

### 2. Automation Rules

```yaml
automation_rules:
  - name: auto_assign_by_section
    trigger:
      type: task_moved_to_section
      section: "Design"
    action:
      assign_to: "design_team"
      add_followers: ["design_lead"]
      set_custom_field:
        Department: "Design"

  - name: due_date_reminder
    trigger:
      type: due_date_approaching
      days_before: 2
    action:
      add_comment: "@{{assignee}} Reminder: This task is due in 2 days"
      add_to_project: "Due This Week"

  - name: completion_notification
    trigger:
      type: task_completed
    action:
      notify_followers: true
      move_to_section: "Done"
      add_comment: "✅ Completed on {{completion_date}}"

  - name: subtask_creation
    trigger:
      type: task_added_to_project
      project: "New Features"
    action:
      add_subtasks:
        - "Requirements gathering"
        - "Design mockups"
        - "Development"
        - "Testing"
        - "Documentation"
```

## Project Templates

### Feature Launch Template

```yaml
project_template:
  name: "Feature Launch - {{feature_name}}"
  team: "Product"
  
  sections:
    - name: "Planning"
      tasks:
        - name: "Define requirements"
          assignee: "product_manager"
          subtasks:
            - "User stories"
            - "Acceptance criteria"
            - "Success metrics"
        - name: "Technical spec"
          assignee: "tech_lead"
          
    - name: "Design"
      tasks:
        - name: "UX research"
          duration: 5
        - name: "Wireframes"
          duration: 3
        - name: "Visual design"
          duration: 5
          
    - name: "Development"
      tasks:
        - name: "Backend implementation"
          duration: 10
        - name: "Frontend implementation"
          duration: 10
        - name: "API integration"
          duration: 5
          
    - name: "Testing"
      tasks:
        - name: "QA testing"
          duration: 5
        - name: "Bug fixes"
          duration: 3
        - name: "UAT"
          duration: 3
          
    - name: "Launch"
      tasks:
        - name: "Documentation"
          duration: 3
        - name: "Marketing materials"
          duration: 5
        - name: "Release notes"
          duration: 1
        - name: "Go live"
          milestone: true
```

### Sprint Template

```yaml
sprint_template:
  name: "Sprint {{number}} - {{dates}}"
  
  sections:
    - "Backlog"
    - "To Do"
    - "In Progress"
    - "Review"
    - "Done"
    
  custom_fields:
    - name: "Story Points"
      type: number
    - name: "Priority"
      type: dropdown
      options: ["P0", "P1", "P2", "P3"]
    - name: "Type"
      type: dropdown
      options: ["Feature", "Bug", "Tech Debt", "Research"]
```

## Custom Fields

### Field Configurations

```yaml
custom_fields:
  - name: Priority
    type: dropdown
    options:
      - name: "🔴 Urgent"
        color: red
      - name: "🟠 High"
        color: orange
      - name: "🟡 Medium"
        color: yellow
      - name: "🟢 Low"
        color: green
    
  - name: Status
    type: dropdown
    options:
      - "Not Started"
      - "In Progress"
      - "Blocked"
      - "In Review"
      - "Complete"
    
  - name: Estimated Hours
    type: number
    precision: 1
    
  - name: Department
    type: dropdown
    options:
      - "Engineering"
      - "Design"
      - "Marketing"
      - "Sales"
      - "Operations"
    
  - name: Due Week
    type: date
    format: week
```

## Workload Management

### Team Capacity

```
TEAM WORKLOAD - THIS WEEK
═══════════════════════════════════════

Sarah (Designer)
██████████████████░░ 85% | 8 tasks
Capacity: 40 hrs | Assigned: 34 hrs

Mike (Engineer)
████████████████░░░░ 78% | 12 tasks
Capacity: 40 hrs | Assigned: 31 hrs

Lisa (PM)
██████████████████████ 110% ⚠️ | 15 tasks
Capacity: 40 hrs | Assigned: 44 hrs

REBALANCING SUGGESTIONS:
• Move "API docs" from Lisa to Mike
• Extend deadline for "Research report"
• Add resources to "Launch prep"
```

### Timeline View

```yaml
timeline_config:
  view: gantt
  date_range: "this_quarter"
  
  grouping: 
    primary: project
    secondary: assignee
    
  milestones:
    show: true
    style: diamond
    
  dependencies:
    show: true
    type: finish_to_start
    
  color_by: custom_field.priority
```

## Forms & Intake

### Request Form

```yaml
intake_form:
  name: "Work Request"
  project: "Incoming Requests"
  
  fields:
    - name: 

Excerpt, first 6,004 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 Asana Automation

What does the Asana Automation skill do?
A curated collection of practical Claude Skills for real-world office tasks
Is Asana 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 Asana 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-28. 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.