cursor-sso-integration
Configure SAML 2.0 and OIDC SSO for Cursor with Okta, Microsoft Entra ID, and Google Workspace. Triggers on "cursor sso", "cursor saml", "cursor oauth", "enterprise cursor auth", "cursor okta", "cursor entra", "cursor scim".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is a strong skill description that clearly identifies the specific task (configuring SSO for Cursor), names concrete protocols (SAML 2.0, OIDC) and identity providers (Okta, Entra ID, Google Workspace), and provides explicit trigger terms. It uses third-person voice and is concise without being vague. The only minor note is that it could mention SCIM provisioning in the 'what' portion since 'cursor scim' is listed as a trigger.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: configuring SAML 2.0 and OIDC SSO, names specific identity providers (Okta, Microsoft Entra ID, Google Workspace), and specifies the target application (Cursor). | 3 / 3 |
Completeness | Clearly answers 'what' (configure SAML 2.0 and OIDC SSO for Cursor with specific IdPs) and 'when' (explicit trigger terms listed with 'Triggers on' clause serving as the equivalent of a 'Use when' clause). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'cursor sso', 'cursor saml', 'cursor oauth', 'enterprise cursor auth', 'cursor okta', 'cursor entra', 'cursor scim' — covering multiple common variations and specific provider names. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of Cursor + SSO/SAML/OIDC + specific identity providers creates a very clear niche that is unlikely to conflict with other skills. The trigger terms are all Cursor-specific. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 SSO configuration guide with specific URLs, attribute mappings, and step-by-step instructions for three major IdPs. Its main weaknesses are the inclusion of project management content (rollout phases) that inflates the document beyond what's needed for the technical task, and the lack of explicit validation checkpoints between configuration steps. The content would benefit from being split into separate files per IdP with a concise overview.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Verify the metadata XML downloaded successfully by checking it contains <EntityDescriptor>' before uploading to Cursor.
Move the Rollout Strategy section to a separate ROLLOUT.md file and reference it from the main skill - it's project management guidance rather than technical configuration.
Consider splitting each IdP configuration into separate referenced files (OKTA.md, ENTRA.md, GOOGLE.md) with just the common Cursor-side steps in the main file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code blocks, but includes some unnecessary content like the 'Understanding of SAML 2.0 or OIDC concepts' prerequisite, the detailed rollout strategy (Phase 1-3 checklists are project management advice Claude doesn't need), and enterprise considerations that are more informational than actionable. The core SSO configuration sections are well-structured though. | 2 / 3 |
Actionability | Provides specific URLs, exact configuration values, step-by-step instructions with concrete settings for each IdP (Okta, Entra ID, Google Workspace), SCIM token configuration with exact field names, and DNS record format. The configurations are copy-paste ready with real endpoint URLs and attribute mappings. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced for each IdP with numbered instructions, and the testing step is included. However, there are no explicit validation checkpoints between steps (e.g., verifying metadata XML is valid before uploading, confirming the app is properly created before proceeding). The troubleshooting table helps but is reactive rather than preventive. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers for each IdP and topic, but it's a monolithic document (~180 lines) that could benefit from splitting IdP-specific configurations into separate files. The rollout strategy and enterprise considerations sections could be referenced externally. The Resources section at the end provides good external links. | 2 / 3 |
Total | 9 / 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 — 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 | |
- Commit
70e9fa4
- 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.