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 strong skill description that concisely lists specific capabilities and provides explicit trigger terms. It uses third person voice correctly and covers both what the skill does and when it should be activated. The trigger terms are natural and well-varied, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure Cursor 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 to Cursor privacy/security configuration. The combination of 'Cursor' + privacy/telemetry/data handling creates a clear niche 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 solid, information-rich skill with strong actionability—concrete settings, paths, and configurations are provided throughout. Its main weaknesses are that it's somewhat verbose for a single SKILL.md (compliance tables, enterprise details, and network security could be separate files), and it lacks explicit validation workflows for confirming that privacy configurations are working as expected. The data flow diagram and tables are effective communication formats.
Suggestions
Add a verification workflow after configuring .cursorignore (e.g., test that an ignored file doesn't appear in Chat context or codebase search results) to improve workflow clarity.
Move compliance mapping (SOC 2, GDPR, HIPAA) and enterprise considerations into a separate COMPLIANCE.md reference file, keeping only a brief summary and link in the main skill.
Trim explanatory content Claude already knows (e.g., 'TLS 1.2+' needs no explanation, proxy config is standard VS Code) to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some content Claude would already know or could infer (e.g., explaining what TLS is, basic proxy configuration, general compliance framework descriptions). The compliance mapping tables and enterprise considerations sections add bulk that could be trimmed or moved to separate reference files. However, the tables and diagrams are efficient formats for the information they convey. | 2 / 3 |
Actionability | The skill provides concrete, actionable guidance throughout: specific UI paths for enabling Privacy Mode, exact settings.json configurations, complete .cursorignore examples with realistic patterns, specific domain allowlists for firewalls, and proxy configuration with real JSON. Nearly everything is copy-paste ready. | 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 workflow for initial setup (e.g., 'do these steps in order'), no validation checkpoints after configuring .cursorignore or telemetry settings, and no feedback loops for verifying that sensitive files are actually excluded from AI features. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, and external resource links are provided at the end. However, the compliance mapping, enterprise considerations, and network security sections are substantial inline content that would benefit from being split into separate reference files, especially given there are no bundle files. The skill tries to be comprehensive in a single file rather than providing an overview with pointers. | 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
3a2d27d
- 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.