iam-role-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill iam-role-generatorIam Role Generator - Auto-activating skill for AWS Skills. Triggers on: iam role generator, iam role generator Part of the AWS Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any explanation of capabilities, has redundant and limited trigger terms, and provides no guidance on when Claude should select this skill. The description would be nearly useless for skill selection among multiple AWS-related skills.
Suggestions
Add specific actions the skill performs, e.g., 'Generates AWS IAM role policies with least-privilege permissions, creates trust relationships, and outputs CloudFormation or Terraform templates.'
Include a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user needs to create IAM roles, define AWS permissions, set up service roles, or generate role policies.'
Add natural keyword variations users would say: 'IAM policy', 'AWS role', 'permissions', 'trust policy', 'service role', 'cross-account access', 'least privilege'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Iam Role Generator') without describing any concrete actions. There's no explanation of what the skill actually does - no verbs like 'creates', 'generates', 'configures', or specific capabilities listed. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is limited to a redundant trigger phrase. There's no 'Use when...' clause or explicit trigger guidance explaining scenarios for activation. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are redundant ('iam role generator, iam role generator' - duplicated) and miss natural variations users would say like 'create IAM role', 'AWS permissions', 'role policy', 'IAM permissions', or 'access policy'. | 1 / 3 |
Distinctiveness Conflict Risk | Being part of 'AWS Skills' category and mentioning 'IAM role' provides some specificity, but without describing what distinguishes this from other AWS-related skills (like general IAM management or policy creation), there's moderate overlap risk. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only generic descriptions of what the skill supposedly does without any concrete guidance on IAM role generation, policy structures, trust relationships, or AWS CLI/CloudFormation examples. The content fails to teach Claude anything it doesn't already know.
Suggestions
Add executable code examples showing IAM role creation via AWS CLI, CloudFormation, or Terraform with proper trust policies and permission boundaries
Include specific IAM role patterns (e.g., Lambda execution role, EC2 instance profile, cross-account role) with concrete policy JSON examples
Define a clear workflow: 1) Identify required permissions, 2) Create trust policy, 3) Create permission policy, 4) Validate with IAM Access Analyzer, 5) Test with least privilege
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actionable IAM-specific guidance
| 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 | There is zero concrete guidance - no code, no commands, no specific steps for generating IAM roles. The entire content describes what the skill does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, and no validation checkpoints for what should be a multi-step process (creating IAM roles with proper policies). | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials, no examples, and no references to additional resources for IAM role patterns or templates. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.