cloud-tasks-queue-setup
Cloud Tasks Queue Setup - Auto-activating skill for GCP Skills. Triggers on: cloud tasks queue setup, cloud tasks queue setup Part of the GCP Skills skill category.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cloud-tasks-queue-setupActivation
22%This description is essentially a title repeated with minimal useful information. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should select this skill. The description reads like auto-generated boilerplate rather than a thoughtful skill description.
Suggestions
Add specific actions the skill performs, e.g., 'Creates and configures Cloud Tasks queues, sets retry policies, defines rate limits, and manages queue permissions.'
Add a proper 'Use when...' clause with natural trigger terms: 'Use when the user needs to set up task queues, configure async job processing, or work with Google Cloud Tasks.'
Include natural keyword variations users might say: 'task queues', 'background jobs', 'async processing', 'Google Cloud Tasks', 'GCP task scheduling'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Cloud Tasks Queue Setup' without describing any concrete actions. It doesn't explain what setting up a queue involves (e.g., creating queues, configuring retry policies, setting rate limits). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. No explicit 'Use when...' clause with actionable triggers. | 1 / 3 |
Trigger Term Quality | Includes 'cloud tasks queue setup' as a trigger term (duplicated), and 'GCP' is mentioned. However, it misses natural variations users might say like 'task queue', 'job queue', 'async tasks', 'background jobs', or 'Google Cloud Tasks'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Cloud Tasks' and 'GCP' terms provide some specificity to Google Cloud's task queue service, but 'queue setup' is generic enough to potentially conflict with other queue-related skills (e.g., Pub/Sub, message queues). | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill content is entirely meta-description with no actual instructional value. It describes what a skill should do without providing any concrete guidance on Cloud Tasks queue setup - no gcloud commands, no Python client library examples, no queue configuration parameters, and no workflow for creating and managing queues.
Suggestions
Add executable gcloud commands for creating Cloud Tasks queues (e.g., `gcloud tasks queues create QUEUE_ID --location=LOCATION`)
Include a concrete workflow with steps: 1) Enable API, 2) Create queue with specific config, 3) Verify queue creation, 4) Set up IAM permissions
Provide code examples for queue configuration options (rate limits, retry config, routing) using both gcloud CLI and Python client library
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual technical instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are filler with no actual information about Cloud Tasks queue setup. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no actual steps for setting up Cloud Tasks queues. The content describes what the skill supposedly does rather than providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for queue setup operations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual implementation details. There are no references to detailed materials, examples, or API documentation. | 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.