cursor-rules-config

Configure Cursor project rules using .cursor/rules/*.mdc files and legacy .cursorrules. Triggers on "cursorrules", ".cursorrules", "cursor rules", "cursor config", "cursor project settings", ".mdc rules", "project rules".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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 executable examples and a clear, validated migration workflow. Its main gaps are verbosity in full code examples and a failure to route readers to the bundled reference files that already exist.

Suggestions

Link to the existing reference files from the relevant sections (e.g. "See references/framework-specific-templates.md" under rule examples, "See references/errors.md" under Debugging) instead of duplicating that content inline.

Trim the full API route and React component code blocks to the minimal snippet needed to demonstrate the .mdc rule format.

Move detailed advanced/tips material into the corresponding reference files and keep SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and Cursor-specific (no generic concept explanations), but several full code examples (a complete Zod/NextResponse API route, a full React component) are longer than needed to illustrate the rule format and could be tightened.	2 / 3
Actionability	It provides complete, executable .mdc file contents with frontmatter, a concrete command (Cmd+Shift+P > New Cursor Rule), file-naming conventions, and copy-paste-ready code examples.	3 / 3
Workflow Clarity	The migration workflow is a clearly sequenced numbered list with an explicit verification checkpoint ("Delete .cursorrules after verifying all rules load") before the destructive step, and the Debugging Rules section supplies feedback loops for error recovery.	3 / 3
Progressive Disclosure	Six reference files exist (advanced-configuration, basic-configuration, errors, examples, framework-specific-templates, tips-for-effective-rules) but the body never links to or signals them, leaving advanced/examples/tips/errors content inline that duplicates what those files hold.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 third-person, names its domain concretely, and supplies an explicit, well-covered trigger list that makes it distinctive. Its only weakness is that it describes a single action rather than enumerating the full set of capabilities.

Suggestions

Expand the capability statement beyond "Configure" to list concrete actions, e.g. "Create, edit, and migrate Cursor project rules...".

Consider phrasing the trigger guidance as a natural "Use when..." clause describing scenarios in addition to the keyword list.

Dimension	Reasoning	Score
Specificity	It names the domain and one concrete action ("Configure Cursor project rules using .cursor/rules/*.mdc files and legacy .cursorrules") but does not enumerate multiple distinct actions such as creating, editing, migrating, or splitting rules.	2 / 3
Completeness	It states what the skill does (configure Cursor project rules via .mdc/.cursorrules) and provides explicit trigger guidance via the "Triggers on" clause, answering both what and when.	3 / 3
Trigger Term Quality	The "Triggers on" list gives good coverage of natural phrasings a user would say ("cursor rules", "cursor config", "cursor project settings", "project rules", ".mdc rules") including common variations.	3 / 3
Distinctiveness Conflict Risk	The Cursor-specific triggers (.cursorrules, .mdc rules, cursor config) carve a clear niche that is unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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.