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
Quality
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 severely underdeveloped, essentially just naming the skill topic without explaining capabilities or providing meaningful trigger guidance. The duplicate trigger term and lack of concrete actions make it nearly useless for skill selection among multiple AWS-related skills. It reads more like a placeholder than a functional skill description.
Suggestions
Add specific actions the skill performs, e.g., 'Creates and manages S3 lifecycle rules to automatically transition objects between storage classes, expire objects, or abort incomplete multipart uploads.'
Include a 'Use when...' clause with natural trigger terms like 'Use when configuring object expiration, storage class transitions, lifecycle policies, auto-delete rules, or managing S3 storage costs.'
Remove the duplicate trigger term and expand with variations users would naturally say: 'lifecycle rules', 'object expiration', 'transition to Glacier', 'storage tier automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain 'S3 Lifecycle Config' without describing any concrete actions. There are no verbs or specific capabilities listed like 'create lifecycle rules', 'configure expiration policies', or 'manage transitions'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and the 'when' guidance is just a duplicate trigger phrase. There is no explicit 'Use when...' clause explaining when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('s3 lifecycle config' repeated twice) and miss natural variations users would say like 'object expiration', 'storage class transition', 'lifecycle rules', 'bucket lifecycle policy', or 'auto-delete old files'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'S3 Lifecycle Config' is a specific AWS feature, the lack of detail means it could overlap with other AWS/S3 skills. The mention of being 'Part of the AWS Skills skill category' provides some context but doesn't clearly distinguish it from other S3-related skills. | 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 an empty template with no actual content about S3 lifecycle configuration. It contains only meta-descriptions of what a skill should do without any concrete guidance, code examples, AWS CLI commands, or lifecycle policy JSON. Claude already knows what S3 lifecycle configurations are; this skill adds zero actionable value.
Suggestions
Add concrete AWS CLI commands or boto3 code for creating lifecycle rules (e.g., `aws s3api put-bucket-lifecycle-configuration --bucket BUCKET --lifecycle-configuration file://lifecycle.json`)
Include example lifecycle policy JSON showing common patterns: transition to Glacier after 90 days, expire objects after 365 days, clean up incomplete multipart uploads
Add a workflow with validation steps: 1) Get current config, 2) Define new rules, 3) Apply config, 4) Verify with `get-bucket-lifecycle-configuration`
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual S3 lifecycle configuration guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual S3 lifecycle configuration information. It explains what the skill does in abstract terms rather than providing any concrete guidance, wasting tokens on meta-description. | 1 / 3 |
Actionability | No concrete code, commands, or examples are provided. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' describe capabilities without demonstrating them. There's no executable content whatsoever. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for configuring S3 lifecycle rules, no validation checkpoints, and no process sequence. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed documentation, no links to examples, and no structured navigation to additional resources. | 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
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.