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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with concrete, copy-paste-ready SSO configuration. Its main weaknesses are duplicated content already covered by unlinked reference files and missing validation checkpoints for risky org-wide enforcement steps.

Suggestions

Link to the existing references/ files instead of inlining the same SAML config, troubleshooting table, and rollout phases; keep SKILL.md as an overview pointing one level deep to them.

Reconcile the conflicting Entity ID between the body (https://cursor.com/api/auth/saml) and references/saml-2.0-configuration.md (https://cursor.com/saml/sp) to avoid confusing users.

Add explicit validation checkpoints before destructive/batch steps — e.g., gate org-wide SSO enforcement and password-login disable behind a 'test user sign-in verified' validation step.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable with little concept-explanation padding, but it duplicates substantial config (3 IdPs), troubleshooting, and rollout content already present in references/, including a conflicting Entity ID (body: cursor.com/api/auth/saml vs reference: cursor.com/saml/sp), so it could be tightened.	2 / 3
Actionability	Concrete config blocks give exact ACS/Entity URLs, attribute mappings, SCIM base URL, bearer-token auth, and DNS TXT record values with step-by-step UI navigation — copy-paste ready.	3 / 3
Workflow Clarity	Multi-step processes are sequenced with checklists, but risky batch/enforcement operations (org-wide SSO enforcement, disabling password login, SCIM provisioning) lack explicit validate→fix→retry feedback loops, capping clarity at 2.	2 / 3
Progressive Disclosure	Bundle files exist in references/ (saml-2.0-configuration, errors, rollout-strategy, testing-sso, user-provisioning, examples) but the body never links to them, instead inlining content that should be separate — references present but not signaled.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is concise, names concrete protocols and IdPs, and supplies explicit trigger terms that clearly answer both what and when. It avoids fluff and conflicts well with other skills.

Dimension	Reasoning	Score
Specificity	"Configure SAML 2.0 and OIDC SSO for Cursor with Okta, Microsoft Entra ID, and Google Workspace" lists multiple concrete actions (two SSO protocols) plus three specific IdPs, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It states what the skill does (configure SAML 2.0 / OIDC SSO for specific IdPs) and provides an explicit "Triggers on..." when-clause, satisfying both halves; the missing-trigger cap at 2 does not apply.	3 / 3
Trigger Term Quality	Trigger strings like "cursor sso", "cursor saml", "cursor oauth", "cursor okta", "cursor entra", and "cursor scim" are natural phrasings a user would say, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Cursor-scoped triggers ("cursor sso", "cursor saml", "cursor scim") carve a clear niche unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 2 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.