做什么
自动化Asana项目管理工作流程、任务跟踪、团队协作和报告
技能库 智客分类:Agent 工作流 Asana Automation
自动化Asana项目管理工作流程、任务跟踪、团队协作和报告
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
自动化Asana项目管理工作流程、任务跟踪、团队协作和报告
官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Asana Automation、Core Workflows、1. Task Management Pipeline、2. Automation Rules、Project Templates、Feature Launch Template。 其中含规范建议的小节:分步指令。
文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。
Automate Asana project management workflows, task tracking, team collaboration, and reporting
Asana AutomationCore Workflows1. Task Management Pipeline2. Automation RulesProject TemplatesFeature Launch TemplateSprint TemplateCustom FieldsField ConfigurationsWorkload ManagementTeam CapacityTimeline View
来源分类:skills.sh agent-skill
nameAsana Automationdescription具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「Asana Automation」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-c7431f90e627aac4-Asana-%E8%87%AA%E5%8A%A8%E5%8C%96.html 请存为 .cursor/skills/asana-automation/SKILL.md 或 .claude/skills/asana-automation/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/claude-office-skills/skills' --list
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
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:
Comprehensive skill for automating Asana project management and team collaboration.
TASK LIFECYCLE:
┌─────────────────┐
│ New Request │
└────────┬────────┘
▼
┌─────────────────┐
│ Triage & │
│ Prioritize │
└────────┬────────┘
▼
┌─────────────────┐
│ Assign & │
│ Schedule │
└────────┬────────┘
▼
┌─────────────────┐
│ In Progress │
└────────┬────────┘
▼
┌─────────────────┐
│ Review │
└────────┬────────┘
▼
┌─────────────────┐
│ Complete │
└─────────────────┘
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_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:
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:
- 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
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_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
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"
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
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
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:
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}}"
Agent 工作流
创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.
Agent 工作流
使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.
Agent 工作流
管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.
Agent 工作流
Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…