Iam Policy Reviewer - Auto-activating skill for Security Advanced. Triggers on: iam policy reviewer, iam policy reviewer Part of the Security Advanced skill category.
32
0%
Does it follow best practices?
Impact
92%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/iam-policy-reviewer/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It fails across all dimensions: it names the skill but provides zero information about what it does, when to use it, or what distinguishes it from other security skills. The repeated trigger term and boilerplate category reference offer no value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Reviews IAM policies for overly permissive access, identifies privilege escalation risks, checks for least-privilege compliance, and flags unused or stale permissions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about IAM policy review, AWS permissions audit, access control analysis, role permissions, least privilege checks, or policy security assessment.'
Include distinguishing details such as supported cloud providers (AWS, GCP, Azure), specific policy formats (JSON IAM policies), or compliance frameworks to differentiate from other security-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill name and category ('Security Advanced') without describing what it actually does—no mention of reviewing, analyzing, auditing, or any specific IAM policy operations. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'iam policy reviewer' repeated twice. There are no natural user keywords like 'IAM permissions', 'access control', 'policy audit', 'AWS IAM', 'role permissions', 'least privilege', or other terms users would naturally use. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Security Advanced' category provides minimal differentiation. It could easily conflict with any other security-related skill since no specific niche, file types, or distinct triggers are defined. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content about IAM policy review. It contains only auto-generated boilerplate that describes what the skill would do without providing any actionable guidance, security review criteria, code examples, or policy analysis techniques. It would be completely useless for helping Claude perform IAM policy reviews.
Suggestions
Add concrete IAM policy review checklists covering common misconfigurations (e.g., wildcard actions, missing resource constraints, overly broad principals, missing conditions).
Include executable code examples for parsing and analyzing IAM policies (e.g., Python/boto3 scripts to enumerate policies, detect overly permissive statements, or check for least privilege violations).
Define a clear multi-step workflow: gather policies → analyze against least privilege principles → flag risky patterns → generate remediation recommendations, with specific validation at each step.
Add concrete examples of bad vs. good IAM policies with explanations of why specific patterns are risky (e.g., 'Action: *' vs. scoped actions, missing condition keys for MFA).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual IAM policy review guidance, techniques, or examples. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code, no commands, no specific IAM policy patterns, no review checklists, no examples of policy analysis. The content only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. For a security review task involving IAM policies, there should be clear steps for analyzing policies, identifying overly permissive permissions, checking for least privilege violations, etc. None of this exists. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain no meaningful content—just boilerplate descriptions. There are no references to detailed materials, no examples, and no structured navigation to deeper resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
3076d78
Table of Contents
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.