gcs-lifecycle-policy
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill gcs-lifecycle-policyGcs Lifecycle Policy - Auto-activating skill for GCP Skills. Triggers on: gcs lifecycle policy, gcs lifecycle policy Part of the GCP Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It lacks any explanation of capabilities, concrete actions, or guidance on when to use it. The repeated trigger term and boilerplate category mention provide minimal value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, modifies, and validates GCS lifecycle policies for automatic object deletion, storage class transitions, and retention management.'
Include a 'Use when...' clause with explicit triggers, e.g., 'Use when the user needs to configure object expiration, set up storage class transitions, manage bucket retention policies, or automate GCS object cleanup.'
Expand trigger terms to include natural variations: 'object expiration', 'storage class transition', 'bucket retention', 'auto-delete', 'object lifecycle rules', 'TTL for objects'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain 'GCS lifecycle policy' but provides no concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'create', 'configure', 'manage', or 'analyze'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'gcs lifecycle policy' repeated twice. Missing natural variations users might say like 'storage lifecycle', 'bucket retention', 'object expiration', 'auto-delete objects', or 'GCS retention rules'. | 1 / 3 |
Distinctiveness Conflict Risk | Being part of 'GCP Skills' category and mentioning 'GCS lifecycle policy' provides some specificity, but without concrete actions it could overlap with other GCS or GCP storage-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actionable content. It describes what a GCS lifecycle policy skill should do but provides zero actual guidance, code examples, or specific instructions for working with GCS lifecycle policies. The entire content could be replaced with actual implementation details.
Suggestions
Add executable code examples showing how to create lifecycle policies using gsutil or gcloud CLI (e.g., `gsutil lifecycle set lifecycle.json gs://bucket-name`)
Include a concrete JSON example of a lifecycle policy configuration with common rules (delete after N days, transition to Nearline/Coldline)
Provide a clear workflow: 1) Create policy JSON, 2) Apply to bucket, 3) Verify with `gsutil lifecycle get`
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with specific GCS lifecycle policy information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about GCS lifecycle policies. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly but never shows how to actually create, configure, or manage GCS lifecycle policies. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences for implementing lifecycle policies. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed documentation, examples, or related files. No structure for navigating to more detailed information. | 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.