cursor-privacy-settings

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-privacy-settings

Configure Cursor privacy and data handling settings. Triggers on "cursor privacy", "cursor data", "cursor security", "privacy mode", "cursor telemetry". Use when working with cursor privacy settings functionality. Trigger with phrases like "cursor privacy settings", "cursor settings", "cursor".

55%

Overall

Validation — 81%

Implementation — 22%

Activation — 82%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

22%

This skill content is a skeleton outline rather than actionable guidance. It lists high-level steps without any concrete commands, configuration syntax, file contents, or specific settings. The content describes what should be done but never shows how to do it, making it nearly unusable for Claude to execute privacy configuration tasks.

Suggestions

Add concrete .cursorignore syntax examples showing how to exclude sensitive files (e.g., `*.env`, `secrets/`, specific patterns)

Provide specific Cursor settings paths and configuration values for privacy mode and telemetry (e.g., exact setting names, JSON config snippets)

Include a verification checklist with specific commands or UI checks to confirm privacy settings are correctly applied

Replace abstract instructions like 'Evaluate privacy mode needs' with decision criteria and concrete configuration steps

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes some unnecessary padding like 'This skill helps configure' and generic prerequisites that Claude would already understand. Could be tightened significantly.	2 / 3
Actionability	Instructions are vague and abstract with no concrete commands, code, or specific settings to configure. 'Evaluate privacy mode needs' and 'Configure .cursorignore' provide no executable guidance on how to actually do these tasks.	1 / 3
Workflow Clarity	Steps are listed but lack any specificity about what each step entails. No validation checkpoints, no feedback loops, and no concrete verification methods. 'Verify API key security' gives no indication of how to verify.	1 / 3
Progressive Disclosure	References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too thin to serve as a useful overview. The skill offloads critical content (examples, error handling) without providing enough substance in the main file.	2 / 3
	Total	6 / 12 Passed

Activation

82%

The description has strong trigger term coverage and completeness with explicit 'Use when' and 'Trigger with' clauses. However, it lacks specificity in describing concrete actions beyond generic 'Configure', and the inclusion of the bare 'cursor' trigger term creates unnecessary conflict risk with other Cursor-related skills.

Suggestions

Add specific concrete actions like 'disable telemetry', 'enable privacy mode', 'configure data collection preferences', 'manage usage analytics'

Remove the overly generic 'cursor' trigger term to reduce conflict risk with other Cursor IDE skills; keep the more specific compound terms like 'cursor privacy' and 'cursor telemetry'

Dimension	Reasoning	Score
Specificity	Names the domain (Cursor privacy/data handling settings) but only describes one vague action 'Configure'. Does not list specific concrete actions like 'disable telemetry', 'enable privacy mode', or 'manage data collection preferences'.	2 / 3
Completeness	Explicitly answers both what ('Configure Cursor privacy and data handling settings') and when ('Use when working with cursor privacy settings functionality') with explicit trigger phrases listed.	3 / 3
Trigger Term Quality	Good coverage of natural terms including 'cursor privacy', 'cursor data', 'cursor security', 'privacy mode', 'cursor telemetry', 'cursor privacy settings', and the generic 'cursor'. These are terms users would naturally say.	3 / 3
Distinctiveness Conflict Risk	The trigger term 'cursor' alone is overly broad and could conflict with skills about cursor positioning, text cursors, or other Cursor IDE features. The more specific terms like 'cursor privacy' and 'cursor telemetry' are distinctive, but the generic 'cursor' trigger creates conflict risk.	2 / 3
	Total	10 / 12 Passed

Reviewed

15 days ago

Table of Contents

Validation Implementation Activation

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.