Cursor CLI
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent and purpose-aligned, but it delegates prompts to Cursor's CLI/agent and has a minor metadata version inconsistency users should verify.
This appears safe to install if you already trust Cursor and want the agent to use Cursor for coding tasks. Before using it on private projects, verify your Cursor CLI installation, understand whether Cursor Agent is in ask or edit mode, and avoid sending secrets or sensitive code unless Cursor's data handling is acceptable to you.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The assistant may invoke another coding tool on your prompt or project, so its output or changes should be reviewed before relying on them.
The skill exposes Cursor Agent as a callable coding assistant; this is central to the stated purpose, but one example relies on Cursor Agent's default mode rather than explicitly selecting ask mode.
cursor-agent -p "your question" --mode=ask --output-format text ... cursor-agent -p "Review this code for bugs" --output-format text
Use explicit ask/review modes when you only want advice, and verify Cursor Agent's behavior before allowing it to make code changes.
Prompts, and any context Cursor Agent uses from the project, may be handled by Cursor's tooling rather than only by the current agent.
The skill delegates prompts to a separate AI coding assistant/service. This is expected for the skill, but the artifact does not define Cursor's data boundary or what project context Cursor Agent may include.
Use Cursor Agent (AI coding assistant) ... Works best with Cursor Pro for full AI capabilities
Use this only in projects where you are comfortable using Cursor Agent, and avoid sending sensitive code or secrets unless Cursor's data handling terms are acceptable to you.
You may want to confirm that the package you are installing is the intended version, especially because it relies on external Cursor binaries.
The registry metadata lists the evaluated version as 1.1.1 and source as unknown, while the included _meta.json and origin.json report version 1.1.0. This is a provenance/version consistency issue, not evidence of malicious behavior.
Source: unknown ... Version: 1.1.1
Verify the skill listing and the Cursor CLI installation against the official Cursor documentation before use.