CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/okta-tests

Authors tests against Okta - uses org-isolation strategy (per-PR org via Okta Developer Edition vs shared org with namespaced data); tests sign-in policy + MFA enforcement; exercises Okta Identity Engine (OIE) workflows including factor enrollment, recovery flows, and SCIM provisioning; tests scoped API tokens for least-privilege automation. Use when the user works with Okta as IdP and needs unit / integration tests for org config, sign-in policies, or OIE workflows.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

87%

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

A token-efficient, highly actionable body that walks through eight concrete test-authoring steps with executable code, anti-patterns, and limitations. Its only weakness is the absence of explicit validate-retry feedback loops around its destructive/batch operations, which caps workflow clarity at 2.

Suggestions

Add explicit validation-and-retry loops for destructive/batch steps — e.g., after SCIM user provisioning, assert cleanup/teardown and re-run on failure; after org config changes, gate subsequent test steps behind a passing `terraform plan -detailed-exitcode` check.

For Step 4 (sign-in policy enforcement), show how to verify the expected MFA outcome and what to do on a non-matching redirect rather than deferring to 'consult the docs'.

Add a teardown/cleanup step (or 'Step 9') that namespaced fixtures and per-PR orgs are torn down even when tests fail, to make the batch operations self-cleaning.

DimensionReasoningScore

Conciseness

Lean prose plus executable code throughout, with no padding explaining basic OAuth/SCIM/Terraform concepts Claude already knows; even the Classic-vs-OIE framing earns its place because the anti-patterns depend on it.

3 / 3

Actionability

Provides fully executable, copy-paste-ready guidance — `terraform plan -detailed-exitcode`, Python requests tests for token/SCIM endpoints, and concrete CI YAML — rather than vague direction.

3 / 3

Workflow Clarity

Steps 1-8 are clearly sequenced and the terraform drift check is an explicit checkpoint, but the destructive/batch operations (org config changes, SCIM user creation, per-PR org spin-up) lack explicit validate-fix-retry feedback loops, which caps this at 2 per the rubric.

2 / 3

Progressive Disclosure

Self-contained body with no bundle files and well-organized sections; external references (developer.okta.com, sister skills) are clearly signaled and only one level deep, with no nested internal references.

3 / 3

Total

11

/

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.

A highly specific, well-triggered description that concretely lists test-authoring capabilities and pairs them with an explicit 'Use when' clause tied to Okta-as-IdP. It is clearly distinguishable from sibling IdP skills and free of vague fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Authors tests against Okta', 'tests sign-in policy + MFA enforcement', 'exercises OIE workflows including factor enrollment, recovery flows, and SCIM provisioning', 'tests scoped API tokens for least-privilege automation'.

3 / 3

Completeness

Clearly answers what (test authoring for org config, sign-in policies, OIE workflows, scoped tokens) and when via the explicit 'Use when the user works with Okta as IdP and needs unit / integration tests...' clause.

3 / 3

Trigger Term Quality

Strong natural-term coverage with 'Okta', 'IdP', 'unit / integration tests', 'org config, sign-in policies, OIE workflows' that a user would actually say; minor missing variations like 'SSO'/'MFA tests' keep it from being exhaustive but still anchor-3.

3 / 3

Distinctiveness Conflict Risk

Narrowly scoped to Okta-as-IdP testing with distinct triggers, clearly separated from sister skills (keycloak-tests, auth0-tests) and unlikely to fire for non-Okta work.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents