s3-lifecycle-config
S3 Lifecycle Config - Auto-activating skill for AWS Skills. Triggers on: s3 lifecycle config, s3 lifecycle config Part of the AWS Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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/s3-lifecycle-config/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 across all dimensions. It essentially just names the topic ('S3 Lifecycle Config') without describing any concrete capabilities, providing meaningful trigger terms, or explaining when Claude should select this skill. The duplicate trigger term suggests minimal effort in crafting the description.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, modifies, and troubleshoots S3 lifecycle rules including object expiration, storage class transitions, and incomplete multipart upload cleanup.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about S3 object expiration, storage class transitions, moving objects to Glacier, lifecycle policies, or automating S3 object management.'
Include common user-facing keywords and variations such as 'lifecycle rules', 'object expiration', 'transition to Glacier/Intelligent-Tiering', 'storage class policy', and 'bucket lifecycle configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'S3 Lifecycle Config' but does not describe any concrete actions like creating, modifying, or managing lifecycle rules. It only states it's an 'auto-activating skill' without explaining what it actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and the 'when' clause is essentially just restating the skill name as a trigger rather than providing meaningful guidance on when to use it. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 's3 lifecycle config' repeated twice. It misses natural variations users would say like 'S3 expiration policy', 'object lifecycle rules', 'transition to Glacier', 'storage class transition', 'bucket lifecycle policy', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'S3 Lifecycle Config' is somewhat specific to a particular AWS feature, which provides some distinctiveness. However, it could overlap with broader AWS S3 skills or general AWS configuration skills since no concrete actions are described. | 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 essentially a placeholder template with no actual technical content. It contains no S3 lifecycle configuration examples, no AWS CLI commands, no SDK code, no policy JSON/YAML, and no workflow guidance. It would provide zero value to Claude when attempting to help a user configure S3 lifecycle rules.
Suggestions
Add concrete, executable examples of S3 lifecycle configurations—e.g., a JSON lifecycle policy with transitions from STANDARD to GLACIER, and expiration rules, plus the AWS CLI command to apply it (`aws s3api put-bucket-lifecycle-configuration`).
Include a clear workflow: 1) Define lifecycle rules (with JSON example), 2) Apply via CLI/SDK (with command), 3) Verify with `aws s3api get-bucket-lifecycle-configuration`, 4) Validate transitions are working as expected.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') that describe the skill abstractly and replace them with actionable technical content covering common lifecycle patterns (e.g., transition tiers, expiration, abort incomplete multipart uploads, noncurrent version handling).
Add at least one complete, copy-paste-ready lifecycle policy JSON and corresponding Terraform/CloudFormation snippet for infrastructure-as-code users.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea—that it helps with S3 lifecycle config—without adding substance. | 1 / 3 |
Actionability | There are zero concrete instructions, no code examples, no CLI commands, no AWS SDK snippets, no JSON/YAML lifecycle policy configurations. The skill describes rather than instructs, providing no executable or copy-paste-ready guidance whatsoever. | 1 / 3 |
Workflow Clarity | There is no workflow, no sequenced steps, and no validation checkpoints. S3 lifecycle configuration involves specific steps (defining rules, transitions, expiration policies, applying via CLI/SDK) and none are mentioned. | 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 layered content organization. There are no bundle files to reference either, but the content itself doesn't even organize its own (absent) material well. | 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.