# asana-usage

Best practices for an agent using Asana tasks, projects, and portfolios in Cursor, such as confirming targets before changes.

Skill by Asana. Category: Agent craft.

## Install

Project (for this project only):

```sh
npx skills add asana/cursor-marketplace-plugin --skill asana-usage
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add asana/cursor-marketplace-plugin --skill asana-usage -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 1. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/asana/cursor-marketplace-plugin/asana-usage)

## Source

[Open the source](https://github.com/asana/cursor-marketplace-plugin/tree/HEAD/skills/asana-usage). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: asana-usage
description: Best practices for using Asana MCP tools in Cursor. Use when working with tasks, projects, or portfolios.
---

# Asana Usage Best Practices

## Before using Asana tools

Always verify the MCP connection is active. If tools are unavailable, run the `asana-setup` skill first.

## Working with tasks

- When creating tasks, always confirm the target project with the user before creating
- When searching, prefer specific project or section filters over broad workspace searches
- Always show the user a summary of what will be created or modified before taking action
- For bulk operations (creating multiple tasks), list them all first and ask for confirmation

## Working with projects

- Never delete a project without explicit user confirmation
- When duplicating a project, confirm the new name before proceeding
- Section names matter — confirm with the user before moving tasks between sections

## Handling ambiguity

- If the user references "my project" or "the team" without being specific, ask which project they mean before taking action
- If multiple workspaces exist, ask the user which one to use before searching or creating

## Error handling

- If an MCP tool call fails with an auth error, run the `asana-setup` skill
- If a task or project GID is not found, do not guess — ask the user to verify the resource exists
- Rate limit errors: wait 10 seconds and retry once before reporting the error to the user
````

- Previous: [asana-setup](https://syn4pse.dev/terminal/asana-setup.md)
- Next: [bootstrap](https://syn4pse.dev/terminal/postman-bootstrap.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
