Productivity & Workflow Agent Skills for VS Code

Upgrade Cursor versions, migrate from VS Code, and transfer settings

When to activate: customer success, onboarding, health score, QBR, churn prevention, expansion, NPS, escalation, customer retention, renewal

Adjust your Colombian Criminal Law practice profile without repeating the entire interview: change a house position, a threshold…

Codified expertise for customs documentation, tariff classification, duty optimization, restricted party screening, and regulatory compliance across multiple jurisdictions. Informed by trade…

Prunes bloated architecture and cuts over-engineering by re-anchoring project designs to core requirements without modifying files.

Optimizes and refines Claude Code skills autonomously using a multi-dimensional rubric, paired judge evaluations, and git-backed…

Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins.

Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors.

Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users.

Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations.

Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio).

Ask which skill or flow fits your situation.

Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

Expert advisor and thinking partner for strategic situations.

Deal negotiation skill — synthesizes Chris Voss (Never Split the Difference), Trump (Art of the Deal), Roger Fisher (Harvard PON / Getting…

Use to run structured opportunity inspections that align pipeline data

Model close-date slip scenarios; never invent win odds.

Multi-role debate to explore compromises.

Recover a software debugging effort that is repeating failed fixes, tests, or hypotheses without gaining useful evidence.

Diagnose a persistent or unclear failure by stopping speculative edits, inventorying evidence and failed hypotheses, verifying assumptions…

Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions