cursor-debug-bundle
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-debug-bundleDebug AI suggestions and code generation in Cursor. Triggers on "debug cursor ai", "cursor suggestions wrong", "bad cursor completion", "cursor ai debug". Use when debugging issues or troubleshooting. Trigger with phrases like "cursor debug bundle", "cursor bundle", "cursor".
Validation
81%| 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 | |
Implementation
22%This skill provides a high-level outline but lacks the concrete, actionable guidance needed for effective debugging. The instructions read like a generic troubleshooting checklist rather than Cursor-specific debugging procedures. Critical details like actual menu paths, specific log locations, diagnostic commands, and concrete examples are entirely missing or deferred to external files.
Suggestions
Add specific Cursor menu paths and keyboard shortcuts for accessing developer tools and logs (e.g., 'Help > Toggle Developer Tools' or specific key combinations)
Include concrete examples of common AI issues with their symptoms and specific fixes (e.g., 'If completions ignore your .cursorrules, check that the file is in project root and restart Cursor')
Provide actual commands or steps for enabling verbose logging and where to find log output
Add a quick diagnostic checklist with specific items to verify (e.g., 'Check .cursorrules syntax', 'Verify model selection in settings', 'Test with @codebase context')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary framing ('This skill helps...', 'Overview' section restating the description). The prerequisites list items Claude would already understand. | 2 / 3 |
Actionability | Instructions are vague and abstract ('Check common causes', 'Use debugging tools') with no concrete commands, specific steps, or executable examples. Describes what to do rather than how to do it. | 1 / 3 |
Workflow Clarity | Steps are listed but lack any specificity - no actual debugging commands, no validation checkpoints, no concrete guidance on what 'dev tools' or 'verbose logging' means in Cursor context. | 1 / 3 |
Progressive Disclosure | References external files for errors and examples which is good structure, but the main content is too thin to serve as a useful overview. The referenced files may contain the actual actionable content that should be summarized here. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
82%The description has strong trigger term coverage and completeness with explicit 'Use when' guidance. However, it lacks specific concrete debugging actions and has some overly generic triggers ('cursor', 'debugging issues') that could cause conflicts with other skills. The capability description would benefit from more specific actions beyond the general 'debug AI suggestions'.
Suggestions
Add specific concrete actions like 'analyze completion context', 'review AI model settings', 'diagnose suggestion quality issues' to improve specificity
Remove or qualify the overly generic trigger 'cursor' and 'debugging issues or troubleshooting' to reduce conflict risk with other skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor AI) and general action (debug AI suggestions and code generation), but lacks specific concrete actions like 'analyze completion logs', 'check model settings', or 'review context window'. | 2 / 3 |
Completeness | Explicitly answers both what ('Debug AI suggestions and code generation in Cursor') and when ('Use when debugging issues or troubleshooting. Trigger with phrases like...'). Has clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural trigger terms including 'debug cursor ai', 'cursor suggestions wrong', 'bad cursor completion', 'cursor ai debug', 'cursor debug bundle', and the simple 'cursor'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | While Cursor-specific terms are distinctive, the generic triggers 'cursor' and 'debugging issues or troubleshooting' are overly broad and could conflict with general debugging skills or other Cursor-related skills. | 2 / 3 |
Total | 10 / 12 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.