iam-policy-creator
Iam Policy Creator - Auto-activating skill for AWS Skills. Triggers on: iam policy creator, iam policy creator Part of the AWS Skills skill category.
36
Quality
3%
Does it follow best practices?
Impact
99%
0.99xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/iam-policy-creator/SKILL.mdQuality
Discovery
7%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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It lacks concrete actions (what specific IAM policy tasks it performs), natural trigger terms users would say, and explicit guidance on when Claude should select this skill. The redundant trigger terms and boilerplate category mention add no value.
Suggestions
Add specific concrete actions like 'Creates AWS IAM policy JSON documents, defines permissions for users/roles/groups, specifies allowed actions and resources, configures policy conditions'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user needs to create AWS permissions, write IAM policies, define access controls, or mentions IAM, policy documents, or AWS authorization'
Add common file/format references users might mention: 'JSON policy', 'policy document', 'trust policy', 'resource-based policy', 'identity-based policy'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('IAM Policy Creator') but provides no concrete actions. It doesn't explain what creating an IAM policy involves - no mention of permissions, resources, actions, conditions, or JSON policy documents. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when to use' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('iam policy creator' listed twice) and miss natural variations users would say like 'AWS permissions', 'access policy', 'IAM role', 'policy document', 'JSON policy', or 'grant access'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'IAM Policy Creator' is somewhat specific to AWS IAM, it could overlap with other AWS skills. The mention of 'AWS Skills skill category' provides some context but the lack of specific triggers increases conflict risk with related AWS security or permissions skills. | 2 / 3 |
Total | 5 / 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 IAM policy creation guidance. It contains only generic boilerplate text that could apply to any skill topic. There are no executable examples, no policy JSON structures, no AWS CLI commands, and no workflow for creating least-privilege policies.
Suggestions
Add concrete IAM policy JSON examples showing common patterns (S3 read-only, Lambda execution role, cross-account access)
Include AWS CLI commands for creating and validating policies (aws iam create-policy, aws accessanalyzer validate-policy)
Define a clear workflow: 1) Identify required actions 2) Define resource ARNs 3) Add conditions 4) Validate with IAM Policy Simulator 5) Test with minimal permissions
Add references to policy templates or a separate EXAMPLES.md with common policy patterns for different AWS services
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about IAM policy creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no IAM policy JSON examples, no AWS CLI commands, no specific policy patterns. The skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Creating IAM policies involves specific steps (defining actions, resources, conditions, validating with policy simulator) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples file, no policy templates. The content is a shallow placeholder with no depth or navigation. | 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 | |
- Commit
0c08951
- 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.