cursor-rules-config
Configure .cursorrules for project-specific AI behavior. Triggers on "cursorrules", ".cursorrules", "cursor rules", "cursor config", "cursor project settings". Use when configuring systems or services. Trigger with phrases like "cursor rules config", "cursor config", "cursor".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-rules-configOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%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 has strong trigger term coverage and completeness with explicit 'Use when' and 'Triggers on' clauses. However, it lacks specificity about what configurations are possible, and the generic 'configuring systems or services' phrase introduces unnecessary conflict risk with other configuration skills.
Suggestions
Add specific capabilities beyond just 'configure' - e.g., 'set up code style rules, define AI assistant behavior, customize autocomplete preferences'
Replace the generic 'Use when configuring systems or services' with a more targeted clause like 'Use when setting up Cursor IDE project settings or AI coding assistant rules'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (.cursorrules) and one action (configure), but lacks comprehensive detail about what specific configurations or behaviors can be set up. | 2 / 3 |
Completeness | Explicitly answers both what ('Configure .cursorrules for project-specific AI behavior') and when ('Triggers on...', 'Use when configuring systems or services', 'Trigger with phrases like...'). | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural terms: 'cursorrules', '.cursorrules', 'cursor rules', 'cursor config', 'cursor project settings', and variations users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The phrase 'Use when configuring systems or services' is overly broad and could conflict with many configuration-related skills. However, the specific 'cursor' triggers help narrow the scope. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a structural outline but lacks the concrete, actionable content needed to actually create a .cursorrules file. The instructions are too abstract, with no actual file content examples shown inline. The skill tells Claude what to do conceptually but doesn't show how to do it with executable examples.
Suggestions
Add a concrete, copy-paste ready .cursorrules example file showing actual syntax and common configuration options
Replace abstract instructions like 'Define coding rules and conventions' with specific examples of rule definitions
Include at least one inline example before referencing examples.md, showing a minimal working .cursorrules configuration
Add a validation step explaining how to verify the .cursorrules file is being recognized by Cursor (e.g., test prompt and expected behavior change)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section explains what .cursorrules is, which Claude likely already knows. The prerequisites include unnecessary items like 'Basic understanding of YAML syntax'. However, the overall structure is reasonably compact. | 2 / 3 |
Actionability | Instructions are vague and abstract ('Add project metadata', 'Define coding rules') with no concrete code examples, no actual .cursorrules file content shown, and no executable guidance. The skill describes rather than instructs. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack specificity. No validation checkpoint to verify the .cursorrules file works correctly. 'Test with Cursor AI' is vague without explaining what to test or how to verify success. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present but the main skill lacks the essential content that should be inline. The examples should be in the skill itself or at least show one quick example before pointing to more. | 2 / 3 |
Total | 7 / 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 — 13 / 16 Passed
Validation for skill structure
| 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 | |
- 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.