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".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/cursor-pack/skills/cursor-rules-config/SKILL.mdQuality
Discovery
89%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 solid skill description with excellent trigger term coverage and clear distinctiveness. Its main weakness is the lack of specific action verbs beyond 'configure' — listing concrete capabilities like creating, editing, migrating, or validating rules would strengthen it. The explicit trigger list is a strong feature that ensures reliable skill selection.
Suggestions
Expand the capability description with more specific actions, e.g., 'Creates, edits, migrates, and validates Cursor project rules' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor project rules) and mentions specific file paths (.cursor/rules/*.mdc, .cursorrules), but doesn't list multiple concrete actions beyond 'configure'. It lacks detail on what configuring entails (e.g., creating, editing, validating, migrating). | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Cursor project rules using specific file formats) and 'when' (explicit trigger terms listed). The 'Triggers on' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including variations like 'cursorrules', '.cursorrules', 'cursor rules', 'cursor config', 'cursor project settings', '.mdc rules', and 'project rules'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — Cursor rules configuration is a very specific niche. The trigger terms are unique to this tool and unlikely to conflict with other skills. The mention of .mdc files and .cursorrules makes it unmistakable. | 3 / 3 |
Total | 11 / 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, actionable skill that provides comprehensive guidance on Cursor rules configuration with excellent concrete examples and clear structure. Its main weakness is length — the multiple full code examples make it verbose for a SKILL.md that could benefit from splitting detailed examples into bundle files. The migration workflow could also use explicit verification steps.
Suggestions
Move the detailed code examples (React patterns, API routes) into separate bundle files (e.g., examples/react-patterns.mdc, examples/api-routes.mdc) and reference them from the main SKILL.md to improve progressive disclosure and conciseness.
Add explicit verification steps to the migration workflow, e.g., 'Type @Cursor Rules in chat to confirm all migrated rules appear' before deleting .cursorrules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured but includes some content that could be tightened. The multiple complete code examples (React component, API route handler) are quite lengthy and border on excessive for a configuration-focused skill. However, most content earns its place by showing concrete patterns rather than explaining concepts Claude already knows. | 2 / 3 |
Actionability | Highly actionable with complete, copy-paste ready .mdc file examples including proper frontmatter, concrete code patterns, specific file naming conventions, and exact commands (Cmd+Shift+P > New Cursor Rule). The migration steps and debugging instructions are specific and executable. | 3 / 3 |
Workflow Clarity | The migration workflow (steps 1-4) is clearly sequenced but lacks explicit validation checkpoints — step 4 says 'after verifying all rules load' without explaining how to verify. The debugging section is separate rather than integrated into workflows. For a configuration skill, the workflows are adequate but could benefit from verification steps. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but it's quite long for a single file with no bundle files to offload detailed examples into. The extensive code examples for React patterns and API routes could be split into separate reference files. External resource links at the end are helpful but the inline content is heavy. | 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
c81cea4
- 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.