tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-reference-architectureExecute reference architecture patterns for Cursor IDE projects. Triggers on "cursor architecture", "cursor project structure", "cursor best practices", "cursor team setup". Use when working with cursor reference architecture functionality. Trigger with phrases like "cursor reference architecture", "cursor architecture", "cursor".
Activation
40%This description suffers from vague capability language and overly broad trigger terms. While it attempts to provide explicit triggers, the core functionality ('Execute reference architecture patterns') is abstract and doesn't tell Claude what concrete actions this skill performs. The inclusion of 'cursor' alone as a trigger term creates unnecessary conflict risk.
Suggestions
Replace 'Execute reference architecture patterns' with specific concrete actions (e.g., 'Creates folder structures, generates configuration files, sets up team conventions for Cursor IDE projects')
Remove the overly generic 'cursor' trigger and keep only the more specific compound phrases like 'cursor architecture' and 'cursor project structure'
Add examples of what 'reference architecture' means in practice to clarify when this skill should be selected over other Cursor-related skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Execute reference architecture patterns' without specifying concrete actions. It doesn't explain what actions are actually performed (e.g., create files, configure settings, generate templates). | 1 / 3 |
Completeness | Has a 'Use when' clause and trigger phrases, but the 'what' portion is weak - 'Execute reference architecture patterns' doesn't clearly explain what the skill actually does. The when/triggers are present but the capability description is insufficient. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'cursor architecture', 'cursor project structure', 'cursor best practices', but the final trigger 'cursor' alone is overly generic and would match too broadly. Missing natural variations users might say. | 2 / 3 |
Distinctiveness Conflict Risk | While 'cursor architecture' and 'cursor project structure' are somewhat specific, the inclusion of just 'cursor' as a trigger creates high conflict risk with any other Cursor-related skills. The term 'reference architecture' helps but isn't enough to fully distinguish it. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%This skill is essentially a skeleton with no actionable content. It lists high-level steps without any concrete guidance, code examples, configuration snippets, or specific instructions. Claude would gain almost nothing from this skill that it doesn't already know - it needs actual .cursorrules examples, specific project structure patterns, and concrete configuration content to be useful.
Suggestions
Add concrete .cursorrules file examples showing actual rule syntax and common patterns (e.g., coding standards, file organization rules)
Include specific project structure examples with directory trees for both feature-based and layer-based approaches
Provide executable configuration snippets for .cursorignore and workspace settings rather than just mentioning them
Add validation steps such as 'Verify .cursorrules loads correctly by checking Cursor's status bar' or similar checkpoints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the 'Prerequisites' section stating obvious requirements ('Understanding of project structure conventions') and the 'Output' section listing expected outcomes that don't add actionable value. | 2 / 3 |
Actionability | The instructions are entirely abstract and vague - 'Choose project structure', 'Create comprehensive .cursorrules file' provide no concrete guidance, code examples, or specific commands. There's nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | While steps are numbered, they lack any specificity about what each step entails, have no validation checkpoints, and provide no guidance on how to actually accomplish each task. 'Create comprehensive .cursorrules file' tells nothing about what should be in it. | 1 / 3 |
Progressive Disclosure | The skill does reference external files for errors and examples (one level deep), but the main content is so sparse that it's unclear what value those references provide. The structure exists but the overview itself lacks substance to make the references meaningful. | 2 / 3 |
Total | 6 / 12 Passed |
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 | |
Reviewed
Table of Contents
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.