cursor-sso-integration
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-sso-integrationConfigure SSO and enterprise authentication in Cursor. Triggers on "cursor sso", "cursor saml", "cursor oauth", "enterprise cursor auth", "cursor okta". Use when working with cursor sso integration functionality. Trigger with phrases like "cursor sso integration", "cursor integration", "cursor".
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 | |
Implementation
35%This skill provides a high-level outline of SSO configuration but lacks the concrete, actionable details needed for Claude to actually help users. The instructions read like a checklist without the specific values, URLs, configuration snippets, or troubleshooting guidance that would make them executable. The structure is reasonable but the content is too abstract to be useful.
Suggestions
Add concrete configuration values: specific ACS URL format (e.g., 'https://cursor.com/sso/saml/acs'), Entity ID patterns, and actual attribute mapping field names for each IdP
Include at least one complete example configuration for a specific IdP (e.g., Okta) with actual field values and screenshots descriptions
Add validation checkpoints with specific success criteria: 'After step 3, verify the ACS URL shows as validated in your IdP dashboard before proceeding'
Move the inline examples.md content into this file or provide a concrete quick-start example here rather than deferring everything to external files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the 'Output' section listing expected outcomes and the 'Prerequisites' section explaining things Claude would know. The overview paragraph could be tighter. | 2 / 3 |
Actionability | Instructions are vague and abstract - 'Configure ACS URL and Entity ID' and 'Download IdP metadata' provide no concrete values, URLs, commands, or code. No actual configuration snippets, specific field names, or copy-paste ready content. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. No guidance on what to do if SSO test fails, no verification steps between configuration stages, and 'Test SSO with admin account' lacks specifics on what success looks like. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content lacks the concrete quick-start material that should be inline. The skill defers too much to external files without providing actionable content here. | 2 / 3 |
Total | 7 / 12 Passed |
Activation
60%The description establishes a clear domain (Cursor SSO/enterprise auth) and includes explicit 'Use when' guidance, but suffers from two major issues: lack of specific concrete actions beyond 'configure', and dangerously broad trigger terms ('cursor', 'cursor integration') that would cause frequent false matches with other Cursor-related skills.
Suggestions
Remove overly generic trigger terms like 'cursor' and 'cursor integration' that would conflict with any Cursor-related skill
Add specific concrete actions such as 'set up SAML identity providers', 'configure OAuth connections', 'manage SSO settings', 'troubleshoot authentication flows'
Include additional natural trigger variations like 'single sign-on', 'identity provider', 'enterprise login', 'SSO setup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SSO/enterprise authentication in Cursor) and general action (configure), but lacks specific concrete actions like 'set up SAML providers', 'configure OAuth flows', or 'manage identity provider connections'. | 2 / 3 |
Completeness | Explicitly answers both what ('Configure SSO and enterprise authentication in Cursor') and when ('Use when working with cursor sso integration functionality') with trigger phrases provided, meeting the explicit trigger guidance requirement. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'cursor sso', 'cursor saml', 'cursor oauth', 'cursor okta', but the final trigger phrases degrade quality significantly - 'cursor integration' and especially just 'cursor' are overly generic and would trigger inappropriately. | 2 / 3 |
Distinctiveness Conflict Risk | The overly broad trigger terms 'cursor integration' and especially 'cursor' alone would cause this skill to conflict with virtually any Cursor-related skill, creating high conflict risk despite the specific SSO focus. | 1 / 3 |
Total | 8 / 12 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.