Agent Skills

cyber-asana ships workflow skills for Cursor, Claude Code, and other agents. Start here — skills encode when to use MCP tools vs CLI, how to resolve projects from repo config, and common workflows.

Installation

From the repo or after cloning:

npx skills add cyberuni/cyber-asana

Or link individual skills into your agent’s skills directory (e.g. ~/.cursor/skills/, ~/.claude/skills/).

Set authentication before running any workflow.

Included Skills

Skill	Use when
init-asana	First-time setup; ASANA_ACCESS_TOKEN, workspace GID, verify connection
pin-asana-projects	Pin repo projects in .agents/cyber-asana.json via project search keywords
create-asana-task	Create or file a task (URL parse, repo project lookup, MCP asana_task_create)
improve-description	Clean up or rewrite a description — light copy-edit by default, opt-in emoji/template/tone, Asana’s HTML subset
asana-standup	Standup update — recent completions and due-soon tasks
asana-sprint-report	Sprint retro — completed vs incomplete in a project/section
sync-asana-project	Pull project tasks into local markdown for planning
create-tasks-from-code	Scan TODO/FIXME comments and create actionable Asana tasks
link-pr-to-task	Post a GitHub PR URL as a comment on the related task

Prefer create-asana-task over ad-hoc asana_task_create calls so agents resolve workspace, project, and URL fields consistently.

Repo Project Registry

Agents and MCP tools can resolve human-readable project names without an API call. Commit a name → GID map at .agents/cyber-asana.json:

cyber-asana config add <project-gid>              # seed or update an entry
cyber-asana config resolve-project "Backend" --json  # local lookup, no API
cyber-asana config sync                           # refresh cached names from Asana
cyber-asana config show

asana_project_get and project get opportunistically update cached names when results include { gid, name }.