iam-role-generator
Iam Role Generator - Auto-activating skill for AWS Skills. Triggers on: iam role generator, iam role generator Part of the AWS Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.03xAverage 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-role-generator/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 — it is essentially a skill name repeated with minimal context. It provides no concrete actions, no meaningful trigger terms beyond the skill name itself, and no explicit 'Use when...' guidance. It would be nearly indistinguishable from other AWS IAM-related skills and gives Claude insufficient information to select it appropriately.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates AWS IAM role definitions including trust policies, permission policies, and inline policy JSON documents.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create an IAM role, define AWS permissions, generate a trust policy, or write IAM policy JSON.'
Remove the duplicated trigger term ('iam role generator' listed twice) and expand with varied natural language terms users might use, such as 'AWS role', 'IAM permissions', 'assume role policy', 'role ARN'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Iam Role Generator') and mentions AWS, but does not describe any concrete actions like creating IAM policies, defining trust relationships, or generating role JSON. It is essentially a title repeated as a description. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a literal trigger phrase repetition rather than meaningful guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'iam role generator' repeated twice. It misses natural user phrases like 'create IAM role', 'AWS permissions', 'trust policy', 'role policy', 'assume role', or 'IAM JSON'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'IAM role' does narrow the domain somewhat compared to generic AWS skills, but the lack of specificity about what it actually does (e.g., generating role policies vs. auditing roles vs. managing roles) means it could overlap with other AWS/IAM-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 placeholder with no substantive content. It contains only generic boilerplate text that repeats 'iam role generator' without providing any actual IAM role generation guidance, AWS CLI commands, CloudFormation templates, policy JSON examples, or trust relationship configurations. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples such as AWS CLI commands (`aws iam create-role ...`), CloudFormation/CDK snippets, or IAM policy JSON templates for common role patterns (Lambda execution role, EC2 instance role, cross-account role).
Define a clear workflow: 1) Determine the trust policy (which service/principal assumes the role), 2) Define the permissions policy, 3) Create the role with specific commands, 4) Validate with `aws iam simulate-principal-policy` or similar.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that contain no actionable information and replace with lean, instruction-focused content.
Include at least one complete, copy-paste-ready example of generating an IAM role (e.g., a Lambda execution role with least-privilege permissions) with validation steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It repeatedly restates 'iam role generator' without adding any substantive information Claude doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous padding. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no IAM policy JSON, no concrete steps for generating an IAM role. The skill describes what it could do rather than instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, sequence, or steps are provided. There are no validation checkpoints, no process to follow, and no concrete guidance on how to generate an IAM role. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to supporting files, no structured navigation, and no meaningful organization of content across sections. | 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
3a2d27d
- 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.