pubsub-topic-setup
Pubsub Topic Setup - Auto-activating skill for GCP Skills. Triggers on: pubsub topic setup, pubsub topic 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 pubsub-topic-setupActivation
22%This description is severely underdeveloped, essentially just restating the skill name without explaining what actions it performs or providing meaningful trigger guidance. The duplicate trigger terms and lack of concrete capabilities make it difficult for Claude to know when to select this skill over others in a large skill library.
Suggestions
Add specific actions the skill performs, e.g., 'Creates GCP Pub/Sub topics, configures subscriptions, sets IAM permissions, and manages message retention policies.'
Add a proper 'Use when...' clause with natural trigger terms like 'Use when the user needs to create a Pub/Sub topic, set up message queues, configure GCP messaging, or work with Cloud Pub/Sub subscriptions.'
Include common variations of terminology users might use: 'pub/sub', 'Pub/Sub', 'message queue', 'event streaming', 'topic creation', 'GCP messaging'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Pubsub Topic Setup' without describing any concrete actions. It doesn't explain what setting up a pubsub topic involves (e.g., create topics, configure subscriptions, set permissions). | 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 | Contains 'pubsub topic setup' as a trigger term (duplicated), which is somewhat relevant but misses natural variations users might say like 'pub/sub', 'message queue', 'create topic', 'GCP messaging', or 'Cloud Pub/Sub'. | 2 / 3 |
Distinctiveness Conflict Risk | Being part of 'GCP Skills' category and mentioning 'pubsub' provides some distinctiveness, but the vague description could overlap with other GCP or messaging-related skills without clear boundaries. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill is entirely meta-content describing what a skill should do rather than providing any actual guidance for Pub/Sub topic setup. It contains no GCP-specific commands, no gcloud CLI examples, no Terraform configurations, and no actual technical content. The skill is essentially a placeholder template that would provide no value to Claude when attempting to help users with Pub/Sub topics.
Suggestions
Add concrete gcloud CLI commands for creating Pub/Sub topics (e.g., `gcloud pubsub topics create TOPIC_NAME`)
Include executable code examples for common configurations like subscriptions, IAM bindings, and dead-letter topics
Provide a clear workflow with validation steps: create topic -> verify creation -> configure subscriptions -> test with publish/subscribe
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual technical content. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no actual steps for setting up a Pub/Sub topic. The skill describes what it claims to do 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 Pub/Sub topic creation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. There are no references to detailed materials, examples, or related 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.