gcs-lifecycle-policy
Gcs Lifecycle Policy - Auto-activating skill for GCP Skills. Triggers on: gcs lifecycle policy, gcs lifecycle policy Part of the GCP Skills skill category.
41
11%
Does it follow best practices?
Impact
100%
1.35xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/14-gcp-skills/gcs-lifecycle-policy/SKILL.mdQuality
Discovery
22%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 thin—it essentially restates the skill name without describing any concrete capabilities or providing meaningful trigger guidance. It lacks both a 'what does this do' explanation and an explicit 'when to use' clause, making it very difficult for Claude to select this skill appropriately from a large skill set.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, modifies, and deletes GCS bucket lifecycle rules including age-based deletion, storage class transitions, and object versioning cleanup.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to configure object expiration, storage class transitions, or retention policies for Google Cloud Storage buckets.'
Include natural keyword variations users might say, such as 'bucket lifecycle', 'object expiration', 'storage class transition', 'Cloud Storage retention', 'GCS TTL', and 'nearline/coldline/archive transition'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only names the topic 'GCS lifecycle policy' without describing what the skill actually does (e.g., create, modify, delete lifecycle rules, set age-based transitions, etc.). | 1 / 3 |
Completeness | The 'what' is essentially absent—there's no explanation of what the skill does beyond its name. The 'when' is only partially addressed via trigger terms but lacks an explicit 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | It includes 'gcs lifecycle policy' which is a relevant keyword, but the trigger terms are duplicated and miss common variations like 'bucket lifecycle', 'object expiration', 'storage class transition', 'GCS retention', or 'Cloud Storage lifecycle'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'GCS lifecycle policy' is somewhat specific to a niche area, but the lack of concrete actions and the vague 'GCP Skills' category could cause overlap with other GCP-related skills. | 2 / 3 |
Total | 6 / 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 shell with no actual technical content about GCS lifecycle policies. It consists entirely of generic boilerplate descriptions of what the skill could do, without providing any concrete guidance, code examples, commands, or configuration snippets. It would provide zero value to Claude when attempting to help a user with GCS lifecycle policy tasks.
Suggestions
Add concrete, executable examples of GCS lifecycle policy configurations (e.g., gsutil lifecycle set commands or JSON lifecycle rule definitions)
Include a clear workflow for creating and applying lifecycle policies, such as: define rules JSON → apply with gsutil/gcloud → verify with gsutil lifecycle get → validate behavior
Provide specific lifecycle rule examples covering common patterns like transitioning to Nearline/Coldline storage classes after N days, deleting objects after expiration, and handling versioned objects
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable technical content that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no actual technical content about GCS lifecycle policies, and wastes tokens on generic meta-descriptions like 'Provides step-by-step guidance' and 'Follows industry best practices' without any substance. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no configuration examples, no specific steps for creating or managing GCS lifecycle policies. The skill describes what it could do rather than providing any concrete guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill merely states it 'provides step-by-step guidance' without actually including any steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no meaningful organization of content. There are no bundle files to reference either, but the skill body itself lacks any useful structure. | 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.