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.
41
11%
Does it follow best practices?
Impact
99%
0.99xAverage 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/cloud-tasks-queue-setup/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, essentially just restating the skill name without explaining what actions it performs or when Claude should select it. The duplicate trigger term and boilerplate 'Part of GCP Skills' text add no value. It fails to help Claude distinguish this skill from others or understand its specific capabilities.
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 an explicit 'Use when...' clause with natural trigger terms like 'Use when setting up task queues, configuring async job processing, or working with Google Cloud Tasks.'
Include natural keyword variations users might say: 'task queue', 'background jobs', 'async processing', 'Google Cloud Tasks', 'job scheduling'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says '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 'what' is extremely weak (just 'setup' with no details), and there is no explicit 'when' clause. The triggers listed are just the skill name repeated, not meaningful usage guidance. | 1 / 3 |
Trigger Term Quality | Contains 'cloud tasks queue setup' as a trigger term (duplicated), and 'GCP' is mentioned. However, it's missing natural variations users might say like 'task queue', 'job queue', 'async tasks', 'background jobs', or 'Google Cloud Tasks'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Cloud Tasks Queue' is specific to a GCP service, which provides some distinctiveness. However, it could overlap with other GCP skills or general queue/task management skills due to lack of specific capability details. | 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 content is a template placeholder with zero actionable information about Cloud Tasks queue setup. It describes what the skill claims to do but provides no actual guidance, code examples, gcloud commands, or configuration snippets. Claude already knows what Cloud Tasks are - this skill adds no value.
Suggestions
Add concrete gcloud commands for queue creation: `gcloud tasks queues create QUEUE_NAME --location=LOCATION`
Include a complete workflow: enable API -> create queue -> configure retry policy -> verify setup
Provide executable code examples for common patterns (HTTP targets, App Engine targets, rate limiting)
Add validation steps to verify queue creation and configuration (e.g., `gcloud tasks queues describe`)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual technical information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-descriptions rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The content only describes what the skill 'can do' without showing how to actually set up a Cloud Tasks queue - no gcloud commands, no Terraform configs, no API examples. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite Cloud Tasks queue setup being a multi-step process (enable API, create queue, configure retry policies, etc.), no steps or sequence are provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no structure for actual learning. No references to detailed documentation, no links to examples or advanced configurations, just empty promises of capabilities. | 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.