cursor-prod-checklist

Production readiness checklist for Cursor IDE setup: security, rules, indexing, privacy, and team standards. Triggers on "cursor production", "cursor ready", "cursor checklist", "optimize cursor setup", "cursor onboarding".

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/cursor-pack/skills/cursor-prod-checklist/SKILL.md

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable production checklist with concrete file examples, specific settings paths, and well-organized sections. Its main weaknesses are the lack of validation/feedback loops for a security-critical checklist and the monolithic structure that could benefit from splitting into referenced sub-documents. The content is mostly concise but includes some sections (onboarding template, enterprise considerations) that inflate the token cost.

Suggestions

Add explicit validation steps after key checklist sections — e.g., 'Verify security rule is active: ask Cursor to generate code with a hardcoded API key and confirm it refuses' or 'Test .cursorignore by searching for a file that should be excluded'.

Split the Team Onboarding Template and Enterprise Considerations into separate referenced files to reduce the main SKILL.md size and improve progressive disclosure.

Add a brief troubleshooting/recovery section for common failures (e.g., indexing stuck, Privacy Mode not reflecting, rules not being picked up).

Dimension	Reasoning	Score
Conciseness	The content is reasonably well-structured but includes some sections that could be tightened. The 'Team Onboarding Template' and 'Enterprise Considerations' sections add bulk that may not be essential for the core checklist purpose. Some items like 'Download Cursor from cursor.com/download' explain things Claude doesn't need to be told. However, most checklist items are concise and earn their place.	2 / 3
Actionability	The skill provides highly concrete, actionable guidance: specific file paths (.cursor/rules/, .cursorignore), complete YAML rule file examples that are copy-paste ready, exact keyboard shortcuts, specific settings locations (Cursor Settings > General > Privacy Mode), and precise items to check. The checklist format itself is inherently actionable.	3 / 3
Workflow Clarity	The checklist format provides clear items to complete, and the onboarding template has a sequenced workflow. However, there are no explicit validation checkpoints or feedback loops — for example, no step to verify that security rules are actually being enforced, no 'if indexing fails, do X' recovery steps, and no verification that .cursorignore is working correctly beyond 'Tested @Codebase queries return relevant results'. For a production readiness checklist involving security-sensitive operations, this is a gap.	2 / 3
Progressive Disclosure	The content references two other skills ('cursor-sso-integration' and 'cursor-api-key-management') and links to external resources, which is good. However, the document is quite long (~150+ lines of substantive content) and could benefit from splitting the onboarding template, maintenance schedule, and enterprise considerations into separate referenced files. Without bundle files, everything is inline in one monolithic document.	2 / 3
	Total	9 / 12 Passed

Description

89%

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 terms and completeness, with explicit 'Triggers on' guidance and a clear niche around Cursor IDE production readiness. Its main weakness is that the capabilities are described as categories (security, rules, indexing) rather than concrete actions, making it somewhat vague about what the skill actually does. Overall it's a solid description that would perform well in skill selection.

Suggestions

Replace category labels with concrete actions, e.g., 'Validates security settings, configures .cursorrules files, audits indexing configuration, reviews privacy settings, and enforces team coding standards' instead of listing abstract areas.

Dimension	Reasoning	Score
Specificity	Names the domain (Cursor IDE setup) and lists areas covered (security, rules, indexing, privacy, team standards), but these are categories rather than concrete actions. It doesn't specify what actions are performed, like 'validates security settings' or 'configures indexing rules'.	2 / 3
Completeness	Clearly answers both 'what' (production readiness checklist for Cursor IDE covering security, rules, indexing, privacy, team standards) and 'when' (explicit triggers listed with 'Triggers on' clause). The trigger guidance is explicit and well-defined.	3 / 3
Trigger Term Quality	Includes explicit trigger terms that users would naturally say: 'cursor production', 'cursor ready', 'cursor checklist', 'optimize cursor setup', 'cursor onboarding'. These are natural phrases covering multiple variations of how a user might request this skill.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — targets a very specific niche (Cursor IDE production readiness) with unique trigger terms that are unlikely to conflict with other skills. The combination of 'Cursor' + 'production/checklist/onboarding' creates a clear, non-overlapping identity.	3 / 3
	Total	11 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: b0b1431

Reviewed: 5 days ago

Table of Contents

Discovery 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.