CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

iam-audit

Audit, design, and migrate Identity and Access Management — cloud provider IAM (AWS, GCP, Azure), identity providers (Okta, Entra ID / Azure AD, Auth0, Google Workspace), application authorization (RBAC, ABAC, ReBAC), and federated identity. Use when the user mentions 'IAM,' 'identity,' 'access management,' 'least privilege,' 'role design,' 'SSO,' 'SAML,' 'OIDC,' 'OAuth,' 'JIT access,' 'just-in-time access,' 'break-glass,' 'service accounts,' 'RBAC,' 'ABAC,' 'privilege creep,' 'role explosion,' 'identity governance,' 'IAM strategy,' 'identity migration,' 'Okta,' 'Entra ID,' 'Azure AD,' 'Auth0,' 'Cognito,' or needs identity consultant-level guidance.

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A strong consultant-grade skill body: concrete commands and named tools for every provider, clearly sequenced three-mode workflows with explicit validate-and-fix loops, and a real, well-organized bundle. The only costs are mild verbosity in the verdict examples and some inline detail that duplicates the referenced files.

Suggestions

Trim the long worked examples inside the verdict table (confirmed/needs_validation/rejected rows) down to one short example each and point to references/findings-format.md and references/verification.md, which already carry the detail.

Move the full fingerprint class list ('wildcard-policy', 'admin-attachment', ... 20 classes) into findings-format.md, keeping only the form and 2-3 example fingerprints inline.

Either link or cut the generic unlinked Reference titles (e.g., 'AWS IAM Best Practices', 'NIST SP 800-63') — as bare titles they spend tokens without adding actionable guidance.

DimensionReasoningScore

Conciseness

The body is checklist-dense and assumes Claude's competence (e.g., "'Admin' is not one role — usually 3-5: support, billing, content moderator..." adds judgment, not textbook explanation), but there are trimmable passages: the long worked examples inside the verdict table, and a References section of generic unlinked titles ("AWS IAM Best Practices", "NIST SP 800-63"). This is anchor 4 ('minor instances of over-explanation that could be trimmed'), not 5, and well above anchor 3 since almost every line carries non-obvious guidance.

4 / 5

Actionability

Fully executable throughout: exact read-only commands per provider ("aws accessanalyzer list-findings", "gcloud asset analyze-iam-policy", "az role assignment list --all"), a concrete fingerprint format with worked examples ("iam-audit/shadow-admin/aws/123456789012/role/ci-deploy"), runnable validation ("node references/validate-findings.mjs findings.json"), and named tooling for each design decision (Cerbos, OpenFGA, IRSA, Azure PIM). Copy-paste-ready guidance covering the common cases, matching the anchor-5 example.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: the migration playbook is 7 numbered steps each with a rollback/deadline discipline, and the 'Verify, then record' section is a numbered 7-step flow ending in an explicit feedback loop — "write findings.json, and fix until it passes" — plus a re-run protocol matching by fingerprint. This matches anchor 5 ('explicit validation steps; feedback loops for error recovery'); the destructive/batch cap does not apply because validation is present.

5 / 5

Progressive Disclosure

References are one level deep, well-signaled with markdown links, and all resolve to real files (references/ad-tier0-paths.md, findings-format.md, findings.schema.json, severity-calibration.md, verification.md, validate-findings.mjs, to-sarif.mjs), and the shared-bundle note makes the structure explicit. It falls short of anchor 5 because the ~260-line body still inlines material that overlaps the referenced files (the detailed verdict table examples and the full fingerprint class list duplicate findings-format/verification content), i.e., 'minor organization gaps' per anchor 4.

4 / 5

Total

18

/

20

Passed

Description

100%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.

A model description: third-person, concise for its breadth, with three concrete capability verbs, a fully enumerated scope, and an explicit 'Use when' clause covering natural trigger terms and their synonyms. No fluff, over-claims, or padding are present.

DimensionReasoningScore

Specificity

Opens with three concrete actions — "Audit, design, and migrate Identity and Access Management" — and comprehensively enumerates the covered scope ("cloud provider IAM (AWS, GCP, Azure), identity providers (Okta, Entra ID / Azure AD, Auth0, Google Workspace), application authorization (RBAC, ABAC, ReBAC), and federated identity"). This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; it is not score 4 because coverage of subdomains is thorough rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both questions: the what ("Audit, design, and migrate Identity and Access Management...") and the when ("Use when the user mentions 'IAM,' 'identity,'... or needs identity consultant-level guidance"). This is the anchor-5 pattern: concrete what plus explicit trigger phrases, not the anchor-4 case where the 'when' could be more specific.

5 / 5

Trigger Term Quality

The "Use when the user mentions..." clause lists ~25 natural terms users would actually say, including synonyms and product aliases ('JIT access,' 'just-in-time access,' 'Entra ID,' 'Azure AD,' 'Okta,' 'Cognito,' 'privilege creep,' 'role explosion'). This matches 'Comprehensive coverage of natural terms including synonyms'; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — IAM/identity — with distinct product- and protocol-level triggers (SAML, OIDC, Okta, Entra ID, break-glass) that adjacent security skills would not claim. Matches 'Clear niche with distinct triggers; minimal conflict risk'; generic terms like 'identity' are anchored by the surrounding IAM-specific vocabulary.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/iam-audit/SKILL.md

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.