iam-binding-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill iam-binding-creatorIam Binding Creator - Auto-activating skill for GCP Skills. Triggers on: iam binding creator, iam binding creator Part of the GCP Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining what it does or when to use it. It lacks concrete actions, natural trigger terms users would say, and any guidance for skill selection. The only distinguishing element is the GCP context, but this alone is insufficient for Claude to make informed skill selection decisions.
Suggestions
Add specific actions the skill performs, e.g., 'Creates IAM policy bindings to grant roles to users, service accounts, or groups on GCP resources'
Include a 'Use when...' clause with natural trigger terms like 'grant access', 'assign role', 'permissions', 'service account access', 'IAM policy', 'GCP roles'
Specify the types of bindings or resources supported (e.g., project-level, resource-level, conditional bindings) to distinguish from other potential IAM skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Iam Binding Creator') without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what creating an IAM binding actually involves. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated ('iam binding creator, iam binding creator'). Missing natural user terms like 'permissions', 'access control', 'service account', 'role assignment', 'GCP IAM', or 'grant access'. | 1 / 3 |
Distinctiveness Conflict Risk | The GCP/IAM context provides some specificity that distinguishes it from generic document or code skills, but 'IAM binding' is still vague enough to potentially conflict with other GCP IAM-related skills or general permissions management skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains no concrete information about GCP IAM bindings - no gcloud commands, no Terraform examples, no explanation of principals/roles/resources, and no validation steps. The content describes what the skill claims to do rather than providing actionable guidance.
Suggestions
Add concrete gcloud commands for creating IAM bindings (e.g., `gcloud projects add-iam-policy-binding PROJECT_ID --member='user:email@example.com' --role='roles/viewer'`)
Include examples for different binding scenarios: project-level, resource-level, service account bindings
Add a workflow with validation steps: check current bindings, apply new binding, verify the change took effect
Provide Terraform/Pulumi examples for infrastructure-as-code approaches to IAM binding management
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about IAM binding creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps for creating IAM bindings. The skill describes what it claims to do rather than actually instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. IAM binding creation involves specific steps (identifying principals, roles, resources, using gcloud commands or Terraform), none of which are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials. There are no references to examples, API documentation, or related guides. | 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.