Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Asana Sync · tetherto | DecimalAI

tetherto/qv-asana-sync

SkillScore67Maintained

Look up and update Asana tasks using local developer-workflow config and direct Asana REST calls. Use when the user asks to sync an Asana task, move task status, add a PR link to Asana, or validate Asana configuration.

productivityby tetherto

Links this skill to your agents and keeps it current with the author’s updates.

On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.

Project Management pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/tetherto-qv-asana-sync/SKILL.md

decimalai skills pull tetherto-qv-asana-sync --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/tetherto-qv-asana-sync/SKILL.md https://app.decimal.ai/s/tetherto-qv-asana-sync/SKILL.md

Raw file: /s/tetherto-qv-asana-sync/SKILL.md ↗ · machine-readable summary at /s/tetherto-qv-asana-sync.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 7d ago

—+28% tokens0% turns82% of whole cases pass with skill (18/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	57%	0%
case-02	✗→✓	▲ Improved	-26%	0%
case-04	✗→✓	▲ Improved	32%	0%
case-05	✗→✓	▲ Improved	-7%	0%
case-06	✗→✓	▲ Improved	48%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

tetherto / qvac

.cursor/skills/qv-asana-sync/SKILL.md

View on GitHub ↗

License Apache-2.0Imported 8/3/2026Version v1

Skill contents

SKILL.md

Asana Sync

Manual Asana task lookup and lifecycle sync using direct REST helpers. No Asana MCP binary.

Default Behavior

If the user invokes this skill without a ticket, task GID, or specific action, do not only run config validation and exit. Show the operation menu below and ask what they want to do.

Ask for the missing input:

Ticket ID or task GID
Desired action: find, status, move, comment, or complete
Target status for move
Comment text for comment

Prerequisites

Local config at ~/.config/qvac-pr-skills/config.json
ASANA_ACCESS_TOKEN set in the current environment or available from the user's default shell startup files, unless config uses a different asana.tokenEnv

Create the token:

Open Asana developer console.
Create a Personal Access Token with a clear description, e.g. Cursor local qvac-pr-skills.
Permission model: Asana Personal Access Tokens do not require choosing scopes in this setup. The token acts as the current Asana user and can access whatever that user can access.
For status enrichment, the user must be able to read the configured workspace/project/tasks. For sync actions, the user must also be allowed to comment, move, and complete tasks in that project.
No OAuth app or Asana MCP server is needed.
Store it in your default shell startup file or export it locally. Cursor agents may not inherit the app environment, so the helper falls back to asking your default shell for this variable.

bash
export ASANA_ACCESS_TOKEN='<token>'

Verify:

bash
curl https://app.asana.com/api/1.0/users/me \
  -H "Authorization: Bearer $ASANA_ACCESS_TOKEN"

Docs: Asana personal access token

Validate:

bash
node .cursor/skills/_lib/developer-workflow/config-init.mjs --validate --asana

Common Operations

Show these options when no action is provided:

status - validate local Asana config and token access
find <ticket> - find an Asana task by ticket
task <task-gid> - read a task by Asana GID
move <ticket-or-task-gid> <status> - move task to configured status
comment <ticket-or-task-gid> <text> - add task comment
complete <ticket-or-task-gid> - mark task complete and move to completed

Available statuses: todo, inProgress, blocked, inReview, readyForQa, qaPassed, staging, storeReview, readyForProd, completed, closed.

Status / config validation:

bash
node .cursor/skills/_lib/developer-workflow/asana-cli.mjs status

Find a task by ticket:

bash
node .cursor/skills/_lib/developer-workflow/asana-cli.mjs find QVAC-12345

Read a task by Asana task GID:

bash
node .cursor/skills/_lib/developer-workflow/asana-cli.mjs task <task-gid>

Move a ticket/task to a configured status. If asana.statusOptions is configured, this uses Asana's custom_type_status_option. Otherwise it falls back to old section movement:

bash
node .cursor/skills/_lib/developer-workflow/asana-cli.mjs move QVAC-12345 inProgress
node .cursor/skills/_lib/developer-workflow/asana-cli.mjs move QVAC-12345 inReview
node .cursor/skills/_lib/developer-workflow/asana-cli.mjs move QVAC-12345 blocked
node .cursor/skills/_lib/developer-workflow/asana-cli.mjs move QVAC-12345 completed

Add a comment, for example a PR URL:

bash
node .cursor/skills/_lib/developer-workflow/asana-cli.mjs comment QVAC-12345 "PR opened: https://github.com/owner/repo/pull/123"

Complete a task and move it to configured completed status:

bash
node .cursor/skills/_lib/developer-workflow/asana-cli.mjs complete QVAC-12345

Lifecycle Mapping

Use this mapping after user confirmation:

Start working: move <ticket> inProgress
PR opened: move <ticket> inReview, then comment <ticket> "PR opened: <url>"
Blocked: move <ticket> blocked, then comment with blocker context
PR merged/done: complete <ticket>

For mutations, show the exact planned command first and wait for explicit user confirmation.

Safety

Never write tokens or Asana IDs into repo files.
Do not mutate Asana without user confirmation unless the user already approved the lifecycle action in the current workflow.
Use /users/me to discover the current user; never copy another developer's user GID.

Want to see if tetherto/qv-asana-sync would activate on your phrasing? Try it before you install — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/22/2026, 17:19 UTC · 22 cases

Measured on 21 comparable cases — below the 22 needed to publish a lift, so this result is shown here but not on the registry card or leaderboard.

Lift

+33%

67% vs 33%

Agent turns

1.0 vs 1.0

Tokens

+28%

1,756.81 vs 1,370.67

fail → pass · 11pass → pass · 7fail → fail · 3pass → fail · 1

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-18 I want to know if 'qaPassed' and 'storeReview' are valid status options in our Asana CLI move command. What are the recognized status names?	pass→pass	10,379	2,770	-73%	1	1	0%	1,634	1,708	+5%	0	0	—
case-01 I need to sync my task progress with Asana, but I haven't picked a ticket or specific action yet. Show me the available sync options and ask me for whatever missing inputs you need to proceed.	fail→pass	12,583	3,808	-70%	1	1	0%	1,274	2,000	+57%	0	0	—
case-02 I just created pull request https://github.com/my-org/core-service/pull/404 for ticket QVAC-55432. Update Asana to reflect that the PR is open with the link attached, and make sure to show me the planned terminal command before running it.	fail→pass	14,440	4,559	-68%	1	1	0%	2,750	2,033	-26%	0	0	—
case-03 Our PR for ticket QVAC-88123 was just merged to main. Please finalize and complete this task in Asana, showing me the CLI command first so I can confirm the mutation.	fail→fail	6,814	8,401	+23%	1	1	0%	381	1,658	+335%	0	0	—
case-04 I want to verify that my local Asana settings and environment setup in config.json are correct before starting my workflow. What CLI command checks the Asana configuration?	fail→pass	8,364	2,470	-70%	1	1	0%	1,207	1,597	+32%	0	0	—
case-05 How can I check the local Asana config and test API token access via the project's developer workflow CLI without running custom python or web searches?	fail→pass	10,310	2,780	-73%	1	1	0%	1,812	1,683	-7%	0	0	—
case-06 I have ticket QVAC-99881. I want to look up the corresponding Asana task using our internal CLI helper. What command should I run?	fail→pass	6,522	1,955	-70%	1	1	0%	1,017	1,510	+48%	0	0	—
case-07 I have a direct Asana task GID 1204958302918. What command reads this task details using our repository workflow scripts?	fail→pass	2,862	2,306	-19%	1	1	0%	423	1,603	+279%	0	0	—
case-08 I am beginning work on ticket QVAC-33411 right now. Show me the exact CLI script command to update Asana so my team knows I started.	fail→pass	10,240	2,762	-73%	1	1	0%	1,793	1,627	-9%	0	0	—
case-09 Work on ticket QVAC-77123 is blocked because the API endpoint is returning 500 errors. How should I update Asana's status and document the issue?	fail→pass	9,189	3,426	-63%	1	1	0%	1,436	1,800	+25%	0	0	—
case-10 Post a web link to pull request #88 on task QVAC-11223 in Asana using the repository CLI. Do not alter the task stage.	fail→fail	12,741	6,940	-46%	1	1	0%	2,073	1,700	-18%	0	0	—
case-11 My feature branch for QVAC-44556 has passed unit tests and is ready for QA testing. Which CLI command moves the task to the QA state?	fail→pass	7,742	2,848	-63%	1	1	0%	1,238	1,679	+36%	0	0	—
case-12 Deployment to staging succeeded for QVAC-66778. Show the command to transition this ticket to the staging status in Asana.	fail→pass	6,979	2,461	-65%	1	1	0%	1,300	1,629	+25%	0	0	—
case-13 When setting up Asana integration script calls, I need to know which current user account is making API calls. Should I hardcode my colleague's GID or call a specific API endpoint?	pass→pass	9,325	4,036	-57%	1	1	0%	1,646	1,938	+18%	0	0	—
case-19 I want to move ticket QVAC-22334 to inReview immediately. Can you execute the change directly without showing me the command first?	pass→pass	3,896	3,328	-15%	1	1	0%	582	1,788	+207%	0	0	—
case-14 I need to save my ASANA_ACCESS_TOKEN and Asana task IDs so the team can use them. Where in the Git repository should I save these strings?	pass→pass	10,836	4,871	-55%	1	1	0%	1,835	2,041	+11%	0	0	—
case-15 I exported ASANA_ACCESS_TOKEN in my terminal. What curl command directly verifies this Personal Access Token against the official Asana API?	pass→pass	6,619	2,640	-60%	1	1	0%	1,128	1,608	+43%	0	0	—
case-16 What environment variable name does the Asana CLI helper look for by default to authenticate calls?	pass→pass	4,124	1,557	-62%	1	1	0%	581	1,406	+142%	0	0	—
case-17 Where is the default local developer workflow configuration file stored for this Asana sync system?	fail→pass	4,335	1,512	-65%	1	1	0%	638	1,377	+116%	0	0	—
case-20 I need to transition my Jira ticket JIRA-4567 to 'In Progress' and add a comment using the CLI tool. How do I do this?	fail→fail	9,035	3,315	-63%	1	1	0%	1,729	1,798	+4%	0	0	—
case-21 Create a new pull request on GitHub for branch feature/auth-fix targeting main branch using git/gh CLI.	pass→fail	6,802	6,466	-5%	1	1	0%	1,225	2,261	+85%	0	0	—
case-22 Trigger a GitLab CI pipeline run for branch fix/login-bug using GitLab API curl command.	pass→pass	7,576	5,867	-23%	1	1	0%	1,463	2,107	+44%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 21 counted toward the lift figure. The other 1 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +33 percentage points is the difference between those two pass rates over the 21 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 33.3%
Pass rate with the skill: 66.7%
Cases attempted: 22
Cases counted toward lift: 21
Cases that regressed: 1
Skill version measured: v1
Run completed: 8/22/2026, 17:19 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-01

Prompt

I need to sync my task progress with Asana, but I haven't picked a ticket or specific action yet. Show me the available sync options and ask me for whatever missing inputs you need to proceed.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run67

Live evalNeeds ≥20 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+42% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 6 days ago

Other measured skills in the registry, with their headline benchmark lift.