CtrlK
BlogDocsLog inGet started
Tessl Logo

building-identity-governance-lifecycle-process

Design identity governance and lifecycle (IGA) programs on platforms like SailPoint, Saviynt, or Entra ID Governance, covering joiner-mover-leaver (JML) automation, role mining, access requests, periodic recertification, and orphaned-account remediation sourced from an HR feed. Use when automating cross-system JML provisioning, remediating former-employee access, or building lifecycle processes for SOX, HIPAA, or GDPR compliance.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/building-identity-governance-lifecycle-process/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

The content is genuinely actionable with substantial executable, domain-specific code and a clear five-step workflow, but it is undermined by a missing validation/feedback loop for its destructive batch operations (capping workflow clarity) and by failing to surface the existing bundle files while inlining reference-grade material. Tightening these would lift both workflow_clarity and progressive_disclosure.

Suggestions

Add explicit validation/verification checkpoints to the workflow (e.g., after termination, verify account disabled and access revoked; confirm orphaned-account disablement took effect; a validate->fix->retry loop), which is required for destructive batch operations.

Link the existing bundle files from the body (e.g., under Tools & Systems or a new API Reference section, point to references/api-reference.md and scripts/agent.py) and move the bulk inlined config dicts and full class bodies into those files so SKILL.md stays a lean overview.

Trim the Key Concepts table and other explanatory text that restates widely-known ideas, and shorten the fully-inlined IDENTITY_LIFECYCLE / ACCESS_REQUEST_WORKFLOW dictionaries to the essential fields.

DimensionReasoningScore

Conciseness

The body is large but mostly earns its tokens with domain-specific executable code rather than generic padding; the trim candidates are the fully inlined config dicts (IDENTITY_LIFECYCLE, ACCESS_REQUEST_WORKFLOW) and the Key Concepts table explaining terms Claude largely already grasps, placing it at 'efficient with minor over-explanation' rather than the lean 5.

4 / 5

Actionability

Provides copy-paste-ready classes with real libraries and endpoints (WorkdayIdentityConnector, RoleMiningEngine, OrphanedAccountDetector), but AccessRequestEngine depends on an undefined IGA client interface (self.iga.get_identity, check_sod, is_birthright_for_role), a minor gap that keeps it at 4 rather than fully executable 5.

4 / 5

Workflow Clarity

Five steps are clearly sequenced, but this skill performs destructive batch operations (immediate account disabling, mass access revocation, DISABLE_IMMEDIATELY remediation) with no validation/verification checkpoints or feedback loops, so the rubric's destructive-operation cap of 3 applies and overrides what would otherwise be a 4-5 sequence.

3 / 5

Progressive Disclosure

Section structure is clean (When to Use, Prerequisites, Workflow sub-steps, Key Concepts, Tools, Scenarios, Output Format), but ~400 lines of inlined code/config overlap with the provided bundle files and the body never references or links references/api-reference.md or scripts/agent.py, matching the 'structure present but references not clearly signaled and content that should be separate is inline' anchor.

3 / 5

Total

14

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 precise, actionable, and clearly delineates both the capability and the triggering contexts, with strong specificity and explicit use-when guidance. Its only gap is a few common synonyms (offboarding, deprovisioning, access reviews) that keep trigger-term quality just below fully comprehensive.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions ("joiner-mover-leaver (JML) automation, role mining, access requests, periodic recertification, and orphaned-account remediation sourced from an HR feed"), matching the comprehensive-coverage anchor; it does not fit score 4 because coverage is broad rather than having only minor gaps.

5 / 5

Completeness

Explicitly answers both what ("Design identity governance and lifecycle (IGA) programs...") and when ("Use when automating cross-system JML provisioning, remediating former-employee access, or building lifecycle processes for SOX, HIPAA, or GDPR compliance"), matching the score-5 anchor with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers ("automating cross-system JML provisioning, remediating former-employee access," "SOX, HIPAA, or GDPR compliance," plus named platforms) but missing common synonyms like offboarding/deprovisioning and "access reviews," so it sits above the midpoint at 4 rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Clear IGA niche with named platforms and distinct JML/compliance triggers means minimal conflict risk, matching the score-5 anchor rather than the score-4 minor-overlap anchor.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (720 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
mukul975/Anthropic-Cybersecurity-Skills
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.