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 severely underdeveloped. It essentially restates the skill name without describing any concrete capabilities or providing meaningful guidance on when to use it. The duplicate trigger term and lack of action verbs make it nearly useless for skill selection among a large set of skills.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates, configures, and manages GCS bucket lifecycle rules including object expiration, storage class transitions, and deletion policies.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to set up or modify lifecycle rules for Google Cloud Storage buckets, manage object expiration, or configure automatic storage class transitions.'
Expand trigger terms to include natural variations like 'bucket lifecycle rules', 'object expiration', 'storage class transition', 'GCS retention policy', 'Cloud Storage lifecycle configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only names itself ('Gcs Lifecycle Policy') and states it's an 'auto-activating skill for GCP Skills' without describing what it actually does (e.g., create, configure, manage lifecycle rules). | 1 / 3 |
Completeness | The 'what' is essentially missing—there's no explanation of what the skill does beyond its name. While trigger terms are listed, there's no explicit 'Use when...' clause explaining when Claude should select this skill, and the what is too weak to compensate. | 1 / 3 |
Trigger Term Quality | It includes 'gcs lifecycle policy' as a trigger term, which is a relevant keyword a user might say. However, it duplicates the same trigger term and misses common variations like 'storage lifecycle', 'object expiration', 'bucket lifecycle rules', 'GCS retention', or 'Cloud Storage lifecycle'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'gcs lifecycle policy' is somewhat specific to a niche GCP domain, which reduces conflict risk. However, the vague framing as part of 'GCP Skills' could overlap with other GCP-related skills without clearer differentiation of scope. | 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 template that provides zero actionable content about GCS lifecycle policies. It contains only auto-generated boilerplate that repeats the skill name in various phrasings without any actual instructions, code, commands, or domain-specific knowledge. It would be entirely useless to Claude in performing any GCS lifecycle policy task.
Suggestions
Add concrete, executable examples showing how to set GCS lifecycle policies using gsutil or Terraform, e.g., `gsutil lifecycle set lifecycle.json gs://my-bucket`
Include a sample lifecycle configuration JSON file with common patterns (e.g., delete objects after 90 days, transition to Nearline/Coldline storage)
Provide a clear workflow: 1) Define lifecycle rules in JSON, 2) Apply to bucket, 3) Verify with `gsutil lifecycle get`, with validation steps
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content about lifecycle policy options, conditions, and actions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no substantive information about GCS lifecycle policies. Every section restates the skill name without adding any actual knowledge or guidance Claude doesn't already have. | 1 / 3 |
Actionability | There are no concrete commands, code examples, API calls, or specific instructions for creating or managing GCS lifecycle policies. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow steps are provided whatsoever. There is no sequence of actions, no validation checkpoints, and no guidance on how to actually configure a GCS lifecycle policy. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain only generic filler text. There are no references to detailed documentation, no links to examples, and no meaningful content organization. | 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
3e83543
- 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.