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
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 extremely weak, essentially just restating the skill name with no substantive information about capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The duplicate trigger term suggests a template was filled in without thought.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates AWS IAM policies with least-privilege permissions, generates policy JSON documents, validates policy syntax, and attaches policies to roles/users/groups.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about AWS IAM policies, access permissions, policy documents, role permissions, least privilege, or needs to create/edit JSON policy files.'
Remove the duplicate trigger term and expand with varied natural language phrases users might say, such as 'AWS permissions', 'access control policy', 'policy JSON', 'IAM role', 'permission boundaries'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('IAM Policy Creator') but does not describe any concrete actions like creating, editing, validating, or attaching IAM policies. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the name, and there is no explicit 'when to use' guidance. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'iam policy creator' repeated twice. It misses natural user phrases like 'IAM policy', 'AWS permissions', 'access control', 'policy JSON', 'least privilege', or 'role permissions'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'IAM policy' and 'AWS' provides some domain specificity that distinguishes it from generic skills, but the lack of detail about what specifically it does (create, validate, review?) could cause overlap with other AWS-related 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 content. It contains only generic boilerplate text that repeats the skill name without providing any actionable guidance on creating IAM policies—no policy JSON examples, no least-privilege patterns, no AWS CLI commands, no common policy templates, and no validation steps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples of IAM policy JSON documents covering common use cases (e.g., S3 read-only, Lambda execution role, cross-account access).
Include a clear workflow: 1) Identify required permissions, 2) Draft policy JSON with least-privilege principle, 3) Validate with `aws iam simulate-custom-policy` or IAM Access Analyzer, 4) Attach to role/user.
Remove all boilerplate sections (Example Triggers, When to Use, Capabilities) that add no value and replace with actionable content like policy structure templates and common condition keys.
Add references to advanced topics like permission boundaries, SCPs, and policy evaluation logic, either inline or via linked files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'iam policy creator' excessively, and provides zero substantive information about how to actually create IAM policies. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code examples, no JSON policy structures, no specific AWS CLI commands, no IAM policy syntax. The content only describes what the skill supposedly does without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. Claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to examples or advanced topics, and no meaningful structure beyond generic boilerplate headings. | 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
4dee593
- 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.