cursor-best-practices
Best practices for working with Cursor. Use when learning how to effectively use Cursor features or optimizing your workflow.
Install with Tessl CLI
npx tessl i github:siviter-xyz/dot-agent --skill cursor-best-practices68
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
40%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 description is too vague to be effective for skill selection. It mentions Cursor but fails to specify what practices, features, or workflows it covers. The lack of concrete actions makes it difficult for Claude to determine when this skill is more appropriate than general coding or IDE skills.
Suggestions
Replace 'best practices' with specific capabilities like 'Configure AI-assisted code completion, use multi-cursor editing, set up custom keybindings'
Add specific trigger terms users would say: 'Cursor IDE, Cursor editor, AI code completion, Cursor shortcuts, Cursor settings'
Expand the 'Use when...' clause with concrete scenarios: 'Use when configuring Cursor settings, learning Cursor-specific shortcuts, or troubleshooting Cursor AI features'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'best practices' and 'effectively use Cursor features' without listing any concrete actions. No specific capabilities are mentioned. | 1 / 3 |
Completeness | Has a 'Use when...' clause addressing when to use it, but the 'what' portion is extremely weak - 'best practices' doesn't explain what the skill actually does or teaches. | 2 / 3 |
Trigger Term Quality | Includes 'Cursor' as a relevant keyword and 'workflow' which users might say, but lacks specific feature names, common tasks, or variations users would naturally mention when seeking Cursor help. | 2 / 3 |
Distinctiveness Conflict Risk | While 'Cursor' provides some specificity, 'best practices' and 'workflow' are generic enough to potentially conflict with other IDE or productivity skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at conciseness and progressive disclosure, providing a clean overview that respects token budget and points to detailed references. However, it sacrifices actionability by being too abstract—the main file lacks any concrete examples, specific commands, or executable guidance that would make it immediately useful without consulting references.
Suggestions
Add at least one concrete example for a key workflow (e.g., show the actual TDD cycle: write test → run → implement → verify)
Include a specific, executable example for Plan Mode usage showing what a good plan looks like
Add a brief 'Quick Start' section with 2-3 copy-paste ready commands or keyboard shortcuts with their expected outcomes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every bullet point is actionable guidance without explaining what Cursor is or how AI assistants work. No wasted tokens on concepts Claude already knows. | 3 / 3 |
Actionability | Provides direction (e.g., 'Use Plan Mode (Shift+Tab)') but lacks concrete examples or executable steps. Bullets describe what to do conceptually rather than showing specific commands or workflows. | 2 / 3 |
Workflow Clarity | Workflows are listed as concepts (TDD, git workflows) but no actual step sequences are provided. The skill defers all workflow details to reference files without giving even a minimal example in the main file. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to specific topics. Each reference file is clearly labeled with its purpose, making navigation easy. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.