Skip to content
cccskills
FreePublished on GitHub

cursor-setup

Check whether the Cursor package and agent are ready for Claude Code Harness, and see which implementation backend is resolved. When requested, set Cursor as the user or project default, or remove that setting.

OriginalShow the original description

Configure and verify the Cursor backend for Claude Code Harness. Use when user invokes cursor:setup, wants Cursor as the local default implementation backend, or asks to check Cursor plugin/agent readiness. Distribution default remains opt-in; only local env/user settings are changed when explicitly requested.

Chachamaru127/claude-code-harness3,187 stars(GitHub 3,187 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Check Cursor backend readiness
  • Make Cursor the user-level default backend
  • Set or unset a project-level backend

Files included (1)

  • SKILL.md4.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

cursor:setup - Cursor Backend Setup

Cursor backend の setup / verification 用 skill。配布 plugin の fallback は claude のままにし、現在の repo / user 環境だけ cursor default にする時に使う。

Quick Reference

cursor:setup --check
cursor:setup --user-default
cursor:setup --project-default
cursor:setup --unset

Rules

  • Do not change distribution defaults or plugin manifests to make Cursor the shipped fallback.
  • Use scripts/resolve-impl-backend.sh / scripts/set-impl-backend.sh; do not infer from HARNESS_IMPL_BACKEND alone.
  • Treat ~/.cursor/permissions.json, .cursorignore, and Claude sandbox allowlists as manual/user-owned setup surfaces unless the user explicitly asks to edit a local file.

Flow

First resolve the Harness helper root. Keep the current working directory as the target project so project-scoped env.local writes still land in the user's repo:

HARNESS_PLUGIN_ROOT="${HARNESS_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}"
if [ -z "$HARNESS_PLUGIN_ROOT" ] && [ -n "${CLAUDE_SKILL_DIR:-}" ]; then
  probe="$(cd "${CLAUDE_SKILL_DIR}" && pwd)"
  while [ "$probe" != "/" ] && [ ! -d "$probe/scripts" ]; do
    probe="$(cd "$probe/.." && pwd)"
  done
  [ -d "$probe/scripts" ] && HARNESS_PLUGIN_ROOT="$probe"
fi
if [ -z "$HARNESS_PLUGIN_ROOT" ]; then
  echo "ERROR: HARNESS_PLUGIN_ROOT is not set and could not be derived from CLAUDE_PLUGIN_ROOT or CLAUDE_SKILL_DIR" >&2
  exit 2
fi
  1. For --check, run:

    bash "${HARNESS_PLUGIN_ROOT}/scripts/setup-cursor.sh" --check
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --show
    bash "${HARNESS_PLUGIN_ROOT}/scripts/resolve-impl-backend.sh" --role worker
    CURSOR_AGENT_BIN="${CURSOR_AGENT_BIN:-}"
    if [ -z "$CURSOR_AGENT_BIN" ]; then
      # `agent`(公式の新表記)→ `cursor-agent`(legacy alias)の順に探す。
      # `agent` は汎用的な名前なので、symlink 解決後の実パスの「成分」に
      # cursor-agent が完全一致で現れる場合だけ採用する(部分文字列一致だと
      # /x/cursor-agent-not-really/agent のようなディレクトリ名で突破される)。
      for _c in agent cursor-agent; do
        _p="$(command -v "$_c" 2>/dev/null)" || continue
        [ -n "$_p" ] || continue
        _r="$(realpath "$_p" 2>/dev/null || readlink -f "$_p" 2>/dev/null || echo "$_p")"
        case "/$_r/" in */cursor-agent/*) CURSOR_AGENT_BIN="$_p"; break ;; esac
      done
      if [ -z "$CURSOR_AGENT_BIN" ] && [ -x "$HOME/.local/bin/cursor-agent" ]; then
        CURSOR_AGENT_BIN="$HOME/.local/bin/cursor-agent"
      fi
    fi
    if [ -z "$CURSOR_AGENT_BIN" ]; then
      echo "ERROR: cursor-agent not found in PATH or $HOME/.local/bin" >&2
      exit 3
    fi
    "$CURSOR_AGENT_BIN" --version
    
  2. For --user-default, run:

    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --user cursor
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --show
    
  3. For --project-default, run:

    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" cursor
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --show
    
  4. For --unset, ask whether the target is user or project scope if not clear from the request, then run exactly one matching unset command:

    Project scope:

    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --unset
    

    User scope:

    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --unset --user
    

Output

Report three facts only:

  • resolved backend (claude / codex / cursor)
  • Cursor package readiness (setup-cursor.sh --check)
  • next manual step if Cursor is not ready

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-browser

FreeSummary

Use the agent-browser CLI to navigate web pages, inspect interactive elements, fill forms, capture screenshots, and collect page information. It helps check web app behavior through browser actions and snapshots.

  • Navigate a page and inspect its current state
  • Fill and submit a web form
  • Capture a screenshot for a UI check
Chachamaru127/claude-code-harness3.2KUpdated Oct 26, 2026

breezing

FreeSummary

Run planned work through a team workflow: delegate implementation to workers, coordinate independent review and revisions, then report the outcome. Select a task range or backend, or run all unfinished tasks in one command.

  • Run all unfinished planned tasks
  • Delegate a selected task range
  • Request implementation through the Codex or Cursor backend
Chachamaru127/claude-code-harness3.2KUpdated Oct 26, 2026

breezing

FreeSummary

Run planned software tasks as a coordinated team workflow. It assigns ready tasks to isolated workers, performs per-task and integrated reviews, incorporates approved changes, and reports progress and completion. Worker execution can use the selected backend, including optional Cursor delegation.

  • Run all remaining planned tasks as a team
  • Delegate a selected task range to workers
  • Use Cursor for worker implementation
Chachamaru127/claude-code-harness3.2KUpdated Oct 26, 2026

cc-update-review

FreeSummary

Review changes that integrate Claude Code or Codex updates. Classify each new Feature Table entry as implemented, inherited upstream, or tracked in Plans, and flag entries that are only documented without supporting work.

  • Review a Claude Code or Codex update integration
  • Check new Feature Table entries against implementation
  • Confirm future work is recorded in Plans
Chachamaru127/claude-code-harness3.2KUpdated Oct 26, 2026

ci

FreeSummary

Diagnose failed CI runs by reviewing logs, reproduction details, specifications, and recent commits. Identify whether the cause lies in implementation, tests, or the environment, then make authorized fixes without hiding failures by skipping checks.

  • Find the cause of a failed CI run
  • Trace a build error to a recent commit
  • Fix implementation issues behind failing tests
Chachamaru127/claude-code-harness3.2KUpdated Oct 26, 2026

cursor-ask

FreeSummary

Send a question, investigation, or design discussion to cursor-agent in read-only ask mode. It returns a second opinion or evidence-based findings that the host agent summarizes, without making file changes or running implementation work.

  • Ask for a second opinion on a design decision
  • Investigate code or configuration and request supporting evidence
  • Get an adversarial sanity check on a proposed change
Chachamaru127/claude-code-harness3.2KUpdated Oct 26, 2026

See all skills by Chachamaru127

Report a problem with this skill