Asana Automation logo

Asana Automation

Organization
claude-office-skills
Asana Automation

Automate Asana project management workflows, task tracking, team collaboration, and reporting

Overview

Publisherclaude-office-skills
Repositoryskills
Skill nameAsana Automation
Stars
514
Forks
97
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by claude-office-skills on GitHub. Read the source before you install it.

Installation

Install the Asana Automation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/claude-office-skills/skills/tree/main/asana-automation
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/claude-office-skills/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/asana-automation .claude/skills/claude-office-skills-asana-automation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Asana Automation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Asana Automation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Asana Automation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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: "Request Title"
      type: single_line
      required: true
      
    - name: "Description"
      type: multi_line
      required: true
      
    - name: "Request Type"
      type: dropdown
      options:
        - "New Feature"
        - "Bug Fix"
        - "Content Update"
        - "Design Request"
      required: true
      
    - name: "Priority"
      type: dropdown
      options: ["Low", "Medium", "High", "Urgent"]
      required: true
      
    - name: "Due Date"
      type: date
      required: false
      
    - name: "Attachments"
      type: attachment
      
  routing:
    - condition:
        field: "Request Type"
        equals: "Design Request"
      action:
        assign_to: "design_team"
        add_to_project: "Design Requests"

Reporting

Portfolio Dashboard

PROJECT PORTFOLIO STATUS
═══════════════════════════════════════

Active Projects: 12
On Track: 8 (67%)
At Risk: 3 (25%)
Off Track: 1 (8%)

BY STATUS:
┌────────────────────┬────────┬─────────┐
│ Project            │ Status │ % Done  │
├────────────────────┼────────┼─────────┤
│ Website Redesign   │ 🟢     │ 78%     │
│ Mobile App v2      │ 🟡     │ 45%     │
│ CRM Integration    │ 🟢     │ 92%     │
│ Q2 Marketing       │ 🔴     │ 23%     │
│ Security Audit     │ 🟢     │ 65%     │
└────────────────────┴────────┴─────────┘

UPCOMING MILESTONES:
• Jan 25: Website Beta Launch
• Jan 30: Mobile App QA Complete
• Feb 5: CRM Go-Live

Team Metrics

yaml
reports:
  - name: "Weekly Team Report"
    metrics:
      - tasks_completed
      - tasks_created
      - overdue_tasks
      - completion_rate
    group_by: assignee
    period: last_7_days
    
  - name: "Project Progress"
    metrics:
      - total_tasks
      - completed_percentage
      - days_remaining
      - blockers_count
    group_by: project
    
  - name: "Burnup Chart"
    type: chart
    x_axis: date
    y_axis:
      - total_scope
      - completed_tasks
    period: current_sprint

Integration Workflows

Slack Integration

yaml
slack_integration:
  notifications:
    - trigger: task_assigned_to_me
      channel: dm
      message: "📋 New task assigned: {{task.name}}"
      
    - trigger: task_completed
      channel: "#team-updates"
      message: "✅ {{user}} completed: {{task.name}}"
      
    - trigger: comment_added
      channel: dm
      message: "💬 New comment on {{task.name}}"
      
  commands:
    /asana:
      - create_task
      - list_my_tasks
      - mark_complete

GitHub Integration

yaml
github_integration:
  sync_rules:
    - github_event: issue_opened
      asana_action:
        create_task:
          project: "GitHub Issues"
          name: "{{issue.title}}"
          description: "{{issue.body}}"
          custom_fields:
            GitHub_Issue: "{{issue.number}}"
            
    - github_event: pr_merged
      asana_action:
        complete_task:
          match_field: "GitHub_PR"
          value: "{{pr.number}}"

Best Practices

  1. Clear Task Names: Use action verbs, be specific
  2. Single Assignee: One person accountable per task
  3. Due Dates: Always set realistic deadlines
  4. Subtasks: Break complex work into smaller pieces
  5. Custom Fields: Use consistently across projects
  6. Templates: Create reusable project structures
  7. Regular Reviews: Weekly project check-ins
  8. Archive Completed: Keep workspace organized

Frequently asked questions

What does the Asana Automation AI skill do?

Automate Asana project management workflows, task tracking, team collaboration, and reporting

Why use Asana Automation on TypingMind?

Because you install it once and use it with any model. Asana Automation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Asana Automation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/claude-office-skills/skills/tree/main/asana-automation. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Asana Automation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Asana Automation?

As many as you like. As long as a model supports skills, you can use Asana Automation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Asana Automation AI skill free?

Yes. It is published on GitHub by claude-office-skills under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇