cursor-privacy-settings
Configure Cursor privacy mode, data handling, telemetry, and sensitive file exclusion. Triggers on "cursor privacy", "cursor data", "cursor security", "privacy mode", "cursor telemetry", "cursor data retention".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly specifies concrete capabilities (privacy mode, data handling, telemetry, file exclusion) within a distinct domain (Cursor editor privacy). The explicit trigger terms provide strong selection signals, and the description is concise without unnecessary padding. It effectively distinguishes itself from general privacy or general Cursor skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configure privacy mode, data handling, telemetry, and sensitive file exclusion. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure privacy mode, data handling, telemetry, sensitive file exclusion) and 'when' (explicit trigger terms listed with 'Triggers on' clause serving as the 'Use when' equivalent). | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger terms that users would say: 'cursor privacy', 'cursor data', 'cursor security', 'privacy mode', 'cursor telemetry', 'cursor data retention'. Good coverage of natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Cursor editor privacy configuration. The combination of 'Cursor' + privacy/telemetry/data terms creates a distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and actionable privacy configuration guide with strong concrete examples, specific UI paths, and useful reference tables. Its main weaknesses are length (compliance and enterprise sections could be split into separate files) and missing verification/validation steps for several configuration actions beyond Privacy Mode itself. The content is well-structured but would benefit from progressive disclosure to reduce the token footprint of the main skill file.
Suggestions
Move compliance mapping (SOC 2, GDPR, HIPAA) and enterprise considerations into a separate COMPLIANCE.md file, referenced from the main skill with a one-line summary per framework.
Add explicit verification steps for .cursorignore (e.g., how to confirm a file is excluded from indexing) and for proxy/network configuration (e.g., test connectivity command).
Trim the 'Data Flow' section by removing the explanatory parentheticals in the ASCII diagram—Claude can infer what 'zero retention' means in context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some content Claude already knows or could infer (e.g., explaining what TLS is, general compliance framework descriptions). The compliance mapping tables and enterprise considerations sections add bulk that could be summarized or linked out. However, the tables and diagrams are efficient formats for the information they convey. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste ready configuration snippets (settings.json for telemetry, proxy config), specific file examples (.cursorignore with realistic patterns), exact UI navigation paths, and specific domain allowlists. The guidance is specific and immediately executable. | 3 / 3 |
Workflow Clarity | The verification steps for Privacy Mode are clear (3-step check), and the defense-in-depth layering is well-sequenced. However, there's no explicit validation/feedback loop for confirming that .cursorignore exclusions are actually working, or for verifying network/proxy configuration succeeded. For a security-sensitive skill, missing verification steps for several configurations is a gap. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's quite long and monolithic. The compliance mapping, enterprise considerations, and network security sections could be split into separate reference files. The Resources section at the end provides external links but doesn't offload any internal content to supplementary files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
70e9fa4
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.