cursor-advanced-composer
Manage advanced Cursor Composer techniques for complex edits. Triggers on "advanced composer", "composer patterns", "multi-file generation", "composer refactoring". Use when working with cursor advanced composer functionality. Trigger with phrases like "cursor advanced composer", "cursor composer", "cursor".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-advanced-composerOverall
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.
This description has strong trigger term coverage and completeness with explicit 'Use when' and 'Trigger with' clauses. However, the specificity of actual capabilities is moderate - 'advanced techniques' and 'complex edits' are somewhat vague. The very broad 'cursor' trigger term creates potential conflict risk with other Cursor-related skills.
Suggestions
Replace vague terms like 'advanced techniques' and 'complex edits' with specific concrete actions (e.g., 'coordinate changes across multiple files', 'generate boilerplate code structures', 'refactor function signatures')
Narrow the trigger term 'cursor' to more specific variants to reduce conflict risk with other potential Cursor skills (e.g., remove standalone 'cursor' or qualify it further)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor Composer) and mentions some actions like 'complex edits', 'multi-file generation', 'composer refactoring', but these are not fully concrete or comprehensive - 'advanced techniques' and 'complex edits' remain somewhat vague. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage advanced Cursor Composer techniques for complex edits') and when ('Use when working with cursor advanced composer functionality. Trigger with phrases like...') with clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural trigger terms including 'advanced composer', 'composer patterns', 'multi-file generation', 'composer refactoring', 'cursor advanced composer', 'cursor composer', and 'cursor' - these are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | While 'Cursor Composer' is specific, the broad trigger 'cursor' could conflict with other Cursor-related skills. The 'advanced' qualifier helps but 'complex edits' and 'refactoring' could overlap with general coding skills. | 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 skeletal framework for Cursor Composer usage but lacks the concrete, actionable guidance that would make it useful. The instructions are generic enough that Claude could generate them without the skill. The content defers critical details (examples, error handling) to external files while providing only abstract procedural steps.
Suggestions
Add concrete examples of Composer prompts that demonstrate effective multi-file generation patterns (e.g., 'Create a new API endpoint following @src/api/users.ts pattern')
Include specific validation steps: what to check after each phase, common failure modes, and how to recover from partial applies
Replace generic instructions with executable patterns - show actual @-mention syntax, specific file naming conventions, and example Composer conversations
Inline at least one complete worked example rather than deferring all examples to external files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary filler like the Overview section that restates the description, and generic statements like 'Well-configured .cursorrules file' without specifics. | 2 / 3 |
Actionability | Instructions are vague and abstract ('Describe the feature or changes needed', 'Reference existing patterns'). No concrete examples, code snippets, or specific commands are provided - just generic procedural steps Claude could infer. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. 'Review each proposed change' and 'testing between phases' are mentioned but not operationalized with specific validation criteria or error recovery steps. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is thin - it defers too much to external files without providing enough actionable content in the skill itself. | 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.