cursor-ai-chat
Master Cursor AI Chat with @-mentions, inline edit, and conversation patterns. Triggers on "cursor chat", "cursor ai chat", "ask cursor", "cursor conversation", "chat with cursor", "Cmd+L", "inline edit".
67
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/cursor-pack/skills/cursor-ai-chat/SKILL.mdQuality
Discovery
72%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 clear distinctiveness for Cursor AI chat functionality. However, it lacks concrete action verbs describing what the skill actually teaches (e.g., composing prompts, referencing files, managing conversations) and would benefit from an explicit 'Use when...' clause to guide skill selection.
Suggestions
Replace 'Master Cursor AI Chat with @-mentions, inline edit, and conversation patterns' with specific actions like 'Compose effective prompts in Cursor AI chat, reference files and symbols with @-mentions, perform inline code edits, and manage multi-turn conversations'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Cursor's chat features, needs help with @-mentions, inline editing, or Cmd+L shortcuts.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Cursor AI Chat) and mentions some features like '@-mentions, inline edit, and conversation patterns', but these are more feature labels than concrete actions. It doesn't list specific actionable tasks like 'compose prompts', 'reference files with @-mentions', or 'edit code inline'. | 2 / 3 |
Completeness | The 'what' is partially addressed ('Master Cursor AI Chat with @-mentions, inline edit, and conversation patterns') and trigger terms are listed, but there is no explicit 'Use when...' clause. The triggers are listed but not framed as guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Good coverage of natural trigger terms including 'cursor chat', 'cursor ai chat', 'ask cursor', 'cursor conversation', 'chat with cursor', and the keyboard shortcut 'Cmd+L'. These are terms users would naturally say when seeking help with Cursor's chat feature. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Cursor AI's chat functionality specifically, with distinct trigger terms like 'Cmd+L' and 'cursor chat' that are unlikely to conflict with other skills. The niche is well-defined. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%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 reference-style skill that covers Cursor AI Chat comprehensively with good use of tables and examples. Its main weaknesses are moderate verbosity (ASCII UI diagrams, enterprise section, model recommendations that may date quickly) and lack of explicit validation/feedback loops in workflows. The prompting patterns are a strength but the skill reads more like documentation than a concise, actionable instruction set.
Suggestions
Remove the ASCII chat panel diagram and enterprise considerations section—these don't add actionable value for Claude and consume significant tokens.
Add a brief feedback loop for inline edit: e.g., 'If the diff looks wrong, press Esc, refine your prompt with more specific constraints, and retry Cmd+K.'
Consider splitting the @-symbol reference table and model selection guidance into separate bundle files, keeping SKILL.md as a lean overview with pointers.
Remove or condense model-specific recommendations (GPT-5, Opus, etc.) which are time-sensitive and may become inaccurate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some unnecessary content Claude already knows (enterprise considerations, model recommendation tables with specific model names that may become outdated, and the ASCII diagram of the chat panel UI). The @-symbol table and comparison tables add value but could be tighter. | 2 / 3 |
Actionability | The prompting patterns provide concrete examples of how to structure chat messages, and keyboard shortcuts are specific. However, there's no executable code—the skill is instruction-oriented, which is appropriate, but the guidance is more descriptive than prescriptive. The inline edit section shows a workflow but lacks precise step-by-step commands. | 2 / 3 |
Workflow Clarity | The multi-turn conversation management section provides useful heuristics for when to start fresh vs continue, and the Chat vs Inline Edit vs Composer table clarifies tool selection. However, there are no explicit validation checkpoints or feedback loops—e.g., no guidance on what to do when chat responses degrade or when inline edits produce incorrect diffs. | 2 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headers and tables, but it's a monolithic file with no bundle files to offload detailed content. The @Docs registration steps, enterprise considerations, and model selection tables could be split into separate reference files. External links at the bottom are helpful but the main body is quite long for a single SKILL.md. | 2 / 3 |
Total | 8 / 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
3a2d27d
- 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.