agentsclimarketplace

Analyze official asana mcp

Skill cyberuni/cyber-asana/.agents/skills/analyze-official-asana-mcp

Internal skill: Use this skill when official Asana MCP catalog changes or maintainers request gap analysis.From its SKILL.md

Install
npx -y skills add cyberuni/cyber-asana --skill analyze-official-asana-mcp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.0 KB, as published. Nobody here has run it

Analyze Official Asana MCP Gap

When to use

  • GitHub issue labeled mcp-gap-analysis or titled chore: official Asana MCP catalog changed
  • Maintainer asks for "MCP gap analysis" or "official catalog changed"
  • After adding or removing cyber-asana MCP tools (run pnpm --filter @cyberuni/gap-analysis run catalog first)

Prerequisites

  • Repo dependencies installed (pnpm install)
  • Committed baselines present under data/

Workflow

1. Refresh cyber-asana catalog if MCP source changed

pnpm --filter @cyberuni/gap-analysis run catalog
pnpm --filter @cyberuni/gap-analysis run check

2. Generate gap report

pnpm --filter @cyberuni/gap-analysis run report -- --json

Read the four buckets:

BucketMeaning
official_onlyPrefer official MCP; document routing
cyber_onlycyber-asana advantages; keep
overlapBoth servers can serve the workflow; update routing
unmapped_*Overlap map references a tool missing from a catalog

3. Classify catalog deltas

For each added official tool:

  • Official-only — no sensible cyber-asana REST equivalent (e.g. previews, search_objects)
  • New overlap — add entry to tools/gap-analysis/src/overlap-map.ts
  • cyber-asana gap — official added capability we should implement via REST

For each removed official tool:

  • Note deprecation in maintainer summary
  • Remove stale entries from overlap-map.ts

4. Update routing, overlap map, and web docs

5. Implementation handoff

If cyber-asana should gain tools:

  • Follow update-asana-sdk — gateway, api, cli, mcp, tests
  • Regenerate catalog: pnpm --filter @cyberuni/gap-analysis run catalog

If docs-only:

  • Routing/readme/web-docs/skills changes suffice

6. Refresh official baseline (separate commit)

After analysis is complete:

pnpm --filter @cyberuni/gap-analysis run fetch-official -- --write

Verify:

# should exit 0 (unchanged vs itself — use a temp fetch instead)
pnpm --filter @cyberuni/gap-analysis run fetch-official -- --json > /tmp/official.json
pnpm --filter @cyberuni/gap-analysis run diff-official -- /tmp/official.json
# should exit 0 after baseline refresh

7. Maintainer summary

Post or include in PR:

  • Added/removed official tools
  • Overlap map edits
  • Routing and web-doc edits
  • Recommended follow-up PRs (implement vs docs-only)

Commands reference

CommandPurpose
pnpm --filter @cyberuni/gap-analysis run catalogRegenerate data/cyber-asana-mcp-catalog.json
pnpm --filter @cyberuni/gap-analysis run checkCI check — catalog matches source
pnpm --filter @cyberuni/gap-analysis run fetch-officialFetch live official tool list
pnpm --filter @cyberuni/gap-analysis run fetch-official -- --writeUpdate official baseline
pnpm --filter @cyberuni/gap-analysis run diff-official -- <file>Compare fetch vs baseline
pnpm --filter @cyberuni/gap-analysis run reportHuman-readable gap report
pnpm --filter @cyberuni/gap-analysis run report -- --jsonMachine-readable gap report

Commit discipline

  1. Analysis + overlap-map + docs (one commit)
  2. Baseline JSON refresh (separate commit)

Never commit with red tests. Run pnpm --filter @cyberuni/gap-analysis run test before pushing.

Keep looking

Skills are one crate of 626,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.