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.
39
Quality
7%
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 severely underdeveloped, essentially just restating the skill name without explaining what it actually does or when to use it. The duplicate trigger term and lack of concrete actions make it nearly useless for skill selection. It reads more like auto-generated boilerplate than a functional skill description.
Suggestions
Add specific actions the skill performs, e.g., 'Generates IAM role policies, creates trust relationships, configures service-linked roles, and defines permission boundaries'
Replace the duplicate trigger with natural user phrases: 'Use when creating AWS IAM roles, defining role permissions, setting up cross-account access, or configuring service roles'
Include common file types or outputs: 'Produces JSON policy documents, CloudFormation templates, or Terraform configurations for IAM roles'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Iam Role Generator') without describing any concrete actions. There are no specific capabilities listed like 'creates IAM policies', 'generates trust relationships', or 'configures permissions'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a circular reference to the skill name rather than describing actual use cases or scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('iam role generator, iam role generator' - duplicated) and miss natural variations users would say like 'create IAM role', 'AWS permissions', 'role policy', 'trust policy', or 'service role'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'IAM role' is somewhat specific to AWS identity management, the lack of detail about what aspects of IAM roles it handles (creation, modification, policy generation, etc.) could cause overlap with other AWS-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no actionable content. It describes what an IAM role generator skill would do but provides zero actual guidance on generating IAM roles - no policy examples, no trust relationships, no CLI commands, no CloudFormation/Terraform templates. The content is entirely meta-description without substance.
Suggestions
Add concrete IAM role policy JSON examples showing common patterns (e.g., Lambda execution role, EC2 instance role, cross-account access)
Include executable AWS CLI commands or CloudFormation/Terraform snippets for creating roles
Define a clear workflow: 1) Identify required permissions, 2) Create trust policy, 3) Create permissions policy, 4) Validate with IAM Access Analyzer
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly but never shows how to actually generate an IAM role - no JSON policies, no CLI commands, no CloudFormation templates. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for generating IAM roles. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, but there are no references to detailed materials. For a skill this empty, there's nothing to progressively disclose. | 2 / 3 |
Total | 5 / 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.