cursor

Route prompts to the cursor-rescue subagent for independent cursor-agent analysis.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zjh08177/agent-harness --skill cursor-zjh08177
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cursor
Source: https://github.com/zjh08177/agent-harness/tree/main/skills/cursor
Command: npx skills add https://github.com/zjh08177/agent-harness --skill cursor-zjh08177

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cursor acts as a thin routing layer that delegates user prompts to a dedicated cursor-rescue subagent so you can keep main Claude flow clean while getting a specialized second opinion.

Core Features & Use Cases

  • Delegates work to the cursor-rescue subagent for cursor-agent handling.
  • Keeps domain logic out of the main flow by routing specific tasks to a second voice.
  • Use Case: When you need a targeted cursor-agent analysis without altering the primary agent's behavior.

Quick Start

Invoke the cursor path by saying a trigger like 'cursor review' and the system will route the request to the cursor-rescue subagent.

Frequently Asked Questions about cursor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate prompts to a cursor-agent for an independent code review?

To delegate prompts to a cursor-agent, you route requests through the Cursor CLI to a cursor-rescue subagent. This delegates work to a secondary voice, providing a targeted independent perspective for review or investigation tasks.

What is a cursor-rescue subagent used for in CLI task delegation?

A cursor-rescue subagent is used to handle delegated tasks routed via the Cursor CLI. It provides a specialized second opinion during review, handoff, or investigation tasks without altering the primary agent's behavior.

Do I need the cursor-agent binary on PATH to use cursor routing?

Yes, you need the cursor-agent binary on PATH to use cursor routing. The system routes prompts through the cursor-rescue subagent without local reasoning, requiring this binary to execute the delegated tasks.

How do I trigger task delegation to a secondary voice using the Cursor CLI?

To trigger task delegation using the Cursor CLI, invoke the cursor path with a trigger phrase like 'cursor review'. The system routes the request to the cursor-rescue subagent for processing.

When should I route work to a second voice instead of using my main agent flow?

You should route work to a second voice when you need a targeted cursor-agent analysis during review, handoff, or investigation tasks. This keeps domain logic out of the main flow while getting a specialized second opinion.