cli-cursor

Cursor CLI Orchestrator - Cross-AI Task Delegation

CRITICAL — SELF-INVOCATION PROHIBITED

This skill dispatches to the Cursor CLI binary (cursor-agent). If the agent currently reading this skill is itself running inside cursor-agent (detection signals listed in §2), the skill MUST refuse to load and return the documented error message instead of generating any cursor-agent invocation.

A running CLI skill never dispatches itself. The cli-X skills are for cross-AI delegation only — never self-invocation.

Orchestrate Cursor's terminal coding agent (cursor-agent) for tasks that benefit from a second AI perspective, Cursor's native model (Composer), read-only plan/ask exploration, or its unique worktree/cloud-worker/plugin surfaces.

Core Principle: Use Cursor for what it does best. Delegate, validate, integrate. The calling AI stays the conductor.

1. WHEN TO USE

Activation Triggers

• Cross-AI Validation — code review second perspective, bug detection, an independent implementation attempt.
• Composer Dispatch — tasks that specifically want Cursor's own native model (composer-2.5/composer-2.5-fast), or the Grok (4.5/4.6) / GLM 5.2 tiers already on the enforced allowlist (see §3 Model Selection).
• Read-Only Exploration — --mode plan (read-only planning) or --mode ask (read-only Q&A) when a task wants Cursor's analysis without any file writes.
• Isolated Experimentation — Cursor's native git worktree isolation (-w/--worktree) for a change the operator wants tried in a disposable checkout, documented in references/cursor-tools.md as an opt-in escape hatch, not this packet's default dispatch shape.
• Specialized Generation — explicit Cursor requests naming Grok (4.5 or 4.6) or GLM 5.2 specifically (the only non-Composer models on the enforced allowlist).