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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete config snippets, but it is a verbose monolithic document that duplicates its own references/ bundle without linking to it, and it lacks a cohesive sequenced workflow with validation feedback loops. Progressive disclosure and conciseness are the weakest areas.

Suggestions

Convert the body into a concise overview and link out to the existing references/ bundle files (e.g., "Network security: see [references/network-security.md]", "Sensitive file exclusion: see [references/sensitive-file-exclusion.md]") instead of inlining content that already exists in those files.

Extend the "Verifying Privacy Mode" checkpoint pattern into explicit validate→fix→retry steps for other config changes (e.g., after editing .cursorignore or telemetry settings, verify the setting took effect before proceeding).

Trim or relocate verbose descriptive sections (Compliance Mapping, Enterprise Considerations) into a reference file so SKILL.md keeps only what is needed to act.

Dimension	Reasoning	Score
Conciseness	The body is mostly Cursor-specific and useful but is a ~150-line monolithic document whose data-handling, network-security, and exclusion sections duplicate content already present in references/, so it could be tightened significantly; it is not level 1 because it does not explain basic concepts Claude already knows, and not level 3 because it is far from lean.	2 / 3
Actionability	Concrete executable snippets are provided throughout — settings.json keys ("telemetry.telemetryLevel": "off", proxy config), a copy-paste .cursorignore block, firewall allowlist domains, and exact navigation paths ("Cursor Settings > General > Privacy Mode > ON"); this matches the level-3 copy-paste-ready anchor.	3 / 3
Workflow Clarity	Content is organized by topic rather than as a sequenced workflow, and while "Verifying Privacy Mode" offers a 3-step checkpoint there is no validate→fix→retry feedback loop; it is above level 1 because some sequence and a verification step exist, but below level 3 because checkpoints are partial and implicit.	2 / 3
Progressive Disclosure	Seven bundle files exist in references/ covering the same topics (privacy-mode.md, network-security.md, sensitive-file-exclusion.md, etc.) but the body never links to them, and content that should be separate is inlined; this matches the level-2 anchor (structure present, references not signaled, separable content inline) rather than level 1 because section organization is decent and references are only one level deep.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is strong: it lists concrete actions, provides natural trigger terms, explicitly answers both what and when, and occupies a distinct niche. It uses imperative voice consistent with the rubric's good examples with no first/second-person penalty.

Dimension	Reasoning	Score
Specificity	"Configure Cursor privacy mode, data handling, telemetry, and sensitive file exclusion" names multiple specific concrete actions across a defined domain, matching the level-3 anchor; it is not the level-2 anchor because it is comprehensive rather than naming only some actions.	3 / 3
Completeness	It states what ("Configure Cursor privacy mode, data handling, telemetry, and sensitive file exclusion") and explicit when guidance ("Triggers on ..."), an equivalent of a 'Use when...' clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Triggers "cursor privacy", "cursor data", "cursor security", "privacy mode", "cursor telemetry", and "cursor data retention" are natural phrases a user would say, giving good coverage; it is not level 2 because common variations are well represented rather than partially missing.	3 / 3
Distinctiveness Conflict Risk	The Cursor-prefixed niche triggers ("cursor privacy", "cursor telemetry", etc.) define a clear niche unlikely to fire for unrelated skills; it is not level 2 because the triggers are distinct rather than merely somewhat specific.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.