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.
41
11%
Does it follow best practices?
Impact
100%
1.00xAverage 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/pubsub-topic-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 essentially a title repeated as a description with minimal useful information. It fails to explain what concrete actions the skill performs (e.g., creating topics, configuring subscriptions, setting IAM policies) and lacks an explicit 'Use when...' clause. The trigger terms are narrow and miss many natural variations users might employ.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures Google Cloud Pub/Sub topics, sets up subscriptions, configures message retention and dead-letter policies.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to create a Pub/Sub topic, set up GCP messaging, configure event streaming, or manage Google Cloud publish-subscribe infrastructure.'
Include common keyword variations like 'Pub/Sub', 'Google Cloud Pub/Sub', 'message topic', 'event topic', 'publish subscribe' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Pubsub Topic Setup' without describing any concrete actions like creating topics, configuring subscriptions, setting permissions, or managing message schemas. It's essentially just a name repeated. | 1 / 3 |
Completeness | The 'what' is extremely weak (just the skill name restated) and the 'when' is only implied through the trigger terms. There is no explicit 'Use when...' clause or meaningful explanation of what the skill does or when to invoke it. | 1 / 3 |
Trigger Term Quality | It includes 'pubsub topic setup' as a trigger term, which is somewhat relevant, but misses common variations users might say like 'Pub/Sub', 'create topic', 'GCP messaging', 'Google Cloud Pub/Sub', 'message queue', or 'event streaming'. | 2 / 3 |
Distinctiveness Conflict Risk | Being specific to 'pubsub topic setup' within GCP provides some distinctiveness, but the lack of detail about what exactly it does (vs. other GCP or pubsub-related skills) means it could overlap with broader GCP infrastructure or messaging skills. | 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 essentially a placeholder with no substantive content. It repeatedly describes itself in abstract terms ('provides automated assistance for pubsub topic setup') without ever delivering any actual guidance, code, commands, or concrete information about setting up Pub/Sub topics in GCP. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples such as `gcloud pubsub topics create` commands, Terraform resource blocks, or Python client library snippets for creating and configuring Pub/Sub topics.
Define a clear workflow with steps: e.g., 1) Create topic, 2) Configure IAM permissions, 3) Set up subscriptions, 4) Validate with a test publish/subscribe cycle.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') that describe the skill rather than teaching the task—replace with actionable content covering common configurations like dead-letter topics, message retention, and schema settings.
Include validation checkpoints such as verifying topic creation with `gcloud pubsub topics list` and testing message flow with `gcloud pubsub topics publish`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea—that it helps with 'pubsub topic setup'—without adding substance. | 1 / 3 |
Actionability | There are zero concrete instructions, commands, code snippets, or specific guidance. The skill describes rather than instructs—no gcloud commands, no Terraform configs, no API calls, no example topic configurations. Claude would gain nothing actionable from this. | 1 / 3 |
Workflow Clarity | There is no workflow whatsoever. The skill mentions 'step-by-step guidance' as a capability but never provides any steps. No sequence, no validation, no checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no layered content. There are no bundle files to reference either, but the content itself doesn't even organize what little it has. | 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
3a2d27d
- 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.