cursor-prod-checklist

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-prod-checklist

Execute production readiness checklist for Cursor IDE setup. Triggers on "cursor production", "cursor ready", "cursor checklist", "optimize cursor setup". Use when working with cursor prod checklist functionality. Trigger with phrases like "cursor prod checklist", "cursor checklist", "cursor".

42%

Overall

Validation — 81%

Implementation — 22%

Activation — 40%

SKILL.md

Review

Evals

Activation

40%

This description suffers from circular definitions - it describes itself as doing 'cursor prod checklist functionality' without explaining what that functionality actually entails. The trigger terms are repetitive and include an overly broad 'cursor' trigger that would cause conflicts. The description needs concrete actions and better differentiation.

Suggestions

Replace vague 'production readiness checklist' with specific actions like 'Validates extension configurations, checks keybinding conflicts, verifies AI model settings, and audits workspace preferences'

Remove the overly generic 'cursor' trigger and add more natural user phrases like 'set up cursor for production', 'cursor configuration check', 'is my cursor setup correct'

Clarify the 'what' by explaining what production readiness means in this context - what specific checks or optimizations are performed

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Execute production readiness checklist' and 'optimize cursor setup' without specifying what concrete actions are performed. No specific capabilities like 'configure settings', 'validate extensions', or 'check configurations' are listed.	1 / 3
Completeness	Has a 'Use when' clause and explicit triggers, but the 'what' portion is weak - 'production readiness checklist' and 'cursor prod checklist functionality' are circular and don't explain what the skill actually does. The when is present but the what is essentially undefined.	2 / 3
Trigger Term Quality	Includes some relevant trigger terms ('cursor production', 'cursor ready', 'cursor checklist', 'cursor prod checklist') but they are repetitive and overly specific to the skill name rather than natural user language. The bare 'cursor' trigger is too generic and would cause false matches.	2 / 3
Distinctiveness Conflict Risk	The 'cursor' trigger alone would conflict with any other Cursor-related skills. While 'cursor production' and 'cursor checklist' are more specific, the description doesn't clearly define its niche beyond generic 'production readiness' which could overlap with other setup/configuration skills.	2 / 3
	Total	7 / 12 Passed

Implementation

22%

This skill content reads more like a table of contents than actionable guidance. It lists what should be done without explaining how to do any of it, providing no concrete commands, configuration examples, or specific settings. The heavy reliance on external references without substantive inline content makes this skill ineffective as a standalone guide.

Suggestions

Add concrete, executable examples for each instruction step (e.g., actual .cursorrules file content, specific settings to configure)

Include validation checkpoints after each major step (e.g., 'Verify .cursorrules is loaded by checking X indicator')

Replace vague instructions like 'Configure security and privacy settings' with specific settings paths and recommended values

Provide at least one complete inline example of a production-ready .cursorrules file rather than deferring entirely to examples.md

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes some unnecessary padding like 'comprehensive' and 'properly configured for professional use'. The prerequisites section states obvious things Claude would know (e.g., 'Understanding of Cursor features and settings').	2 / 3
Actionability	Instructions are vague and abstract with no concrete commands, code, or specific steps. 'Complete authentication and licensing setup' and 'Configure security and privacy settings' provide no executable guidance on how to actually perform these tasks.	1 / 3
Workflow Clarity	Steps are listed but lack any detail about what each step involves, no validation checkpoints, and no feedback loops. There's no way to verify if each step was completed correctly before moving to the next.	1 / 3
Progressive Disclosure	References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too sparse to serve as a useful overview. The skill offloads too much to external files without providing enough actionable content in the main file.	2 / 3
	Total	6 / 12 Passed

Validation

81%

Warnings & errors only

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

18 days ago

Table of Contents

Activation Implementation Validation

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.