Content
68%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, well-organized settings reference with concrete types, defaults, and example values, plus useful guardrails (legacy-field sync guidance, a do-not-modify list). The main weaknesses are the absence of any validation step around the destructive config write and one setting (approvalMode's Run Everything) lacking its concrete value.
Suggestions
Add a validation checkpoint to the modify workflow: after writing the file, verify the JSON parses (e.g., re-read and parse it) and note to confirm the change took effect after CLI restart — this lifts the workflow_clarity cap that destructive config writes without validation trigger.
State the concrete enum value for approvalMode's Run Everything option instead of the vague "set approval mode to the non-allowlist value", so the guidance is fully executable.
Trim the redundancy: drop the opening sentence that restates the description and "The file is standard JSON", and state the config path once instead of three times.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a terse reference of Cursor-specific settings Claude would not know (types, defaults, enum values), so most tokens earn their place. It is not a 5 because of minor trimmable redundancy: the opening line restates the frontmatter description, "The file is standard JSON" explains the obvious, and the config path is repeated in both the intro and its own section. | 4 / 5 |
Actionability | "Read ~/.cursor/cli-config.json, apply changes, and write it back" plus concrete value patterns ("Shell(**)", "Mcp(server-name, tool-name)") gives mostly executable, actionable guidance appropriate for an instruction-only skill. It misses a 5 because the Run Everything option never states its actual enum value ("set approval mode to the non-allowlist value") and no example config snippet is provided. | 4 / 5 |
Workflow Clarity | The modify workflow (read → apply changes → write back → restart CLI) is a clear, correctly ordered sequence. However, writing a whole config file back to the user's home directory is a destructive operation with no validation checkpoint (no JSON-parse verification before writing, no confirmation the setting took effect after restart), and the rubric caps workflow clarity at 3 for destructive operations without validation. | 3 / 5 |
Progressive Disclosure | Sections are well organized and easy to navigate (Config File Location, How to Modify, Available Settings, Fields You Should NOT Modify) with no nested or buried references, and the ~84-line body is appropriately self-contained. It is not a 5 because the under-50-line simple-skill exception does not apply and the settings catalog is at the size where a references/ file would be the natural next split as it grows. | 4 / 5 |
Total | 15 / 20 Passed |