cursor-composer-workflows
Execute master Cursor Composer for multi-file AI edits. Triggers on "cursor composer", "multi-file edit", "cursor generate files", "composer workflow", "cursor scaffold". Use when working with cursor composer workflows functionality. Trigger with phrases like "cursor composer workflows", "cursor workflows", "cursor".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-composer-workflowsOverall
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' guidance. However, it lacks specificity about what concrete actions the skill performs beyond vague 'multi-file AI edits', and the inclusion of the generic trigger 'cursor' creates potential conflict risk with other cursor-related skills.
Suggestions
Replace vague 'Execute master Cursor Composer' with specific concrete actions like 'Creates, modifies, and scaffolds multiple files simultaneously using Cursor Composer'
Remove the overly generic trigger 'cursor' from the trigger list to reduce conflict risk with other cursor-related skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor Composer) and mentions 'multi-file AI edits' as an action, but lacks comprehensive concrete actions. 'Execute master' is vague and doesn't describe what specific operations are performed. | 2 / 3 |
Completeness | Explicitly answers both what ('multi-file AI edits', 'cursor composer workflows functionality') and when ('Use when working with cursor composer workflows functionality. Trigger with phrases like...'). Has clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural trigger terms including 'cursor composer', 'multi-file edit', 'cursor generate files', 'composer workflow', 'cursor scaffold', and variations like 'cursor workflows'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The trigger term 'cursor' alone is overly broad and could conflict with other cursor-related skills. However, the more specific terms like 'cursor composer' and 'multi-file edit' provide some distinctiveness. | 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 is a skeleton that promises workflow patterns but delivers only generic, vague instructions. It lacks the concrete examples, specific commands, and actionable guidance that would make it useful. The content defers too much to external references while providing insufficient value in the main skill file.
Suggestions
Add 2-3 concrete Composer prompt examples showing actual multi-file edit requests with expected outcomes (e.g., 'Generate a React component with tests: @components/Button.tsx create UserProfile component following this pattern')
Replace the generic 6-step instructions with specific workflow patterns for different use cases (feature scaffolding, refactoring, etc.) with actual prompt templates
Remove the Overview, Prerequisites, and Output sections - they add no actionable value and waste tokens
Add validation guidance: how to review Composer's proposed changes, what to check before applying, and how to handle partial failures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary sections like 'Overview' that explains what the skill does (Claude can infer this), and 'Prerequisites' listing things Claude would already understand. The 'Output' section is vague filler. | 2 / 3 |
Actionability | Instructions are extremely vague ('Describe the files and changes needed', 'Use @-mentions to reference existing patterns') with no concrete examples, specific commands beyond the keyboard shortcut, or executable guidance. No actual workflow patterns are provided despite promising them. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack any validation checkpoints, feedback loops, or specific guidance on what to do if changes are incorrect. The 6-step process is generic and doesn't address error recovery or verification. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too thin - it defers all substantive content to other files while providing almost no actionable quick-start material 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.