s3-bucket-policy-generator
S3 Bucket Policy Generator - Auto-activating skill for AWS Skills. Triggers on: s3 bucket policy generator, s3 bucket policy generator Part of the AWS Skills skill category.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill s3-bucket-policy-generatorActivation
22%This description is essentially a title with minimal elaboration. It fails to explain what the skill actually does (generate policies with what capabilities?), lacks meaningful trigger terms beyond the skill name itself, and provides no guidance on when Claude should select this skill. The duplicate trigger term suggests a template that wasn't properly filled out.
Suggestions
Add specific capabilities: 'Generates S3 bucket policies for access control, cross-account access, public/private configurations, and encryption requirements'
Include a proper 'Use when...' clause: 'Use when the user needs to create, modify, or troubleshoot S3 bucket policies, configure bucket permissions, or set up cross-account S3 access'
Expand trigger terms to include natural variations: 'bucket permissions', 'S3 access control', 'bucket security policy', 'who can access my bucket'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('S3 Bucket Policy Generator') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of creating policies, defining permissions, configuring access controls, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. There's no explicit 'Use when...' clause with actionable context. | 1 / 3 |
Trigger Term Quality | Includes 's3 bucket policy generator' as a trigger term (duplicated), which is a natural phrase users might say. However, it misses common variations like 'bucket permissions', 'S3 access policy', 'IAM policy for S3', 'bucket ACL', or 'S3 security'. | 2 / 3 |
Distinctiveness Conflict Risk | The S3-specific focus provides some distinctiveness within AWS skills, but 'AWS Skills skill category' is vague. Could potentially conflict with other AWS security or IAM-related skills without clearer boundaries. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill is essentially an empty placeholder with no actual content. It describes what an S3 bucket policy generator skill would do but provides zero actionable guidance - no policy JSON examples, no common policy patterns (public read, cross-account access, VPC endpoint restrictions), and no validation steps. A user would learn nothing from this skill that they couldn't infer from the title alone.
Suggestions
Add concrete S3 bucket policy JSON examples for common use cases (public read-only, cross-account access, IP restrictions, VPC endpoint policies)
Include a workflow: 1) Identify access requirements, 2) Select base policy template, 3) Customize Principal/Resource/Action/Condition, 4) Validate with AWS Policy Simulator or aws s3api get-bucket-policy
Provide copy-paste ready policy snippets with placeholders like ${BUCKET_NAME}, ${ACCOUNT_ID}, ${VPC_ENDPOINT_ID}
Add common pitfalls section: NotPrincipal gotchas, wildcard resource risks, condition key syntax errors
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with zero actionable information. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever - no S3 bucket policy examples, no JSON policy structures, no IAM principal formats, no actual code or commands. The skill describes what it does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined. For a policy generator, there should be steps like: identify access requirements, select policy template, customize principals/resources/actions, validate policy syntax. None of this exists. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to policy examples, no pointers to AWS documentation or related configuration files. | 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.