pubsub-subscription-config
Pubsub Subscription Config - Auto-activating skill for GCP Skills. Triggers on: pubsub subscription config, pubsub subscription config Part of the GCP Skills skill category.
40
11%
Does it follow best practices?
Impact
92%
0.96xAverage 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-subscription-config/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 extremely minimal and template-like, providing almost no useful information about what the skill actually does. It names the domain (GCP Pub/Sub subscription configuration) but fails to list any concrete actions or provide explicit trigger guidance. The repeated trigger term and lack of a 'Use when...' clause make it poorly suited for skill selection among many options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, configures, and manages GCP Pub/Sub subscriptions including pull/push delivery, dead-letter policies, retry settings, and acknowledgment deadlines.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to create or modify Pub/Sub subscriptions, configure message delivery, set up dead-letter topics, or manage subscription settings in Google Cloud.'
Include natural keyword variations users might say, such as 'Cloud Pub/Sub', 'message subscription', 'pull subscription', 'push endpoint', 'ack deadline', and 'subscription IAM'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names the topic 'pubsub subscription config' without describing what it actually does (e.g., create, modify, list, delete subscriptions). | 1 / 3 |
Completeness | The 'what' is essentially absent—there are no described capabilities. The 'when' is only implied through trigger terms but not explicitly stated with a 'Use when...' clause. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | It includes 'pubsub subscription config' which is a relevant keyword, but it's repeated verbatim and misses natural variations users might say like 'Pub/Sub', 'subscription configuration', 'pull subscription', 'push subscription', 'message queue', 'GCP pubsub', or 'Cloud Pub/Sub'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'pubsub subscription config' provides some specificity within the GCP domain, but without describing concrete actions, it could overlap with other GCP Pub/Sub-related skills (e.g., topic config, general pubsub management). | 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 an empty boilerplate template with no actual technical content about Pub/Sub subscription configuration. It contains no executable code, no GCP-specific commands (e.g., gcloud, Terraform), no configuration examples, and no real guidance. It would provide zero value to Claude when attempting to help a user with Pub/Sub subscription configuration tasks.
Suggestions
Add concrete gcloud CLI commands and/or Terraform examples for creating and configuring Pub/Sub subscriptions (e.g., `gcloud pubsub subscriptions create`, push vs pull config, dead-letter topics, retry policies).
Include a clear workflow with validation steps, such as: create subscription → verify with `gcloud pubsub subscriptions describe` → test message delivery → check dead-letter queue configuration.
Provide specific configuration parameters and their recommended values (ack deadline, message retention, expiration policy, filter expressions) with executable examples.
Remove all generic boilerplate text ('This skill provides automated assistance...', 'Follows industry best practices...') and replace with actual technical content that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about Pub/Sub subscription configuration, and every section is generic template text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no Terraform/gcloud snippets, no specific parameters or settings. It only describes what the skill supposedly does in vague terms without actually doing any of it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is provided. Claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or error recovery instructions. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external documents, and the content itself is a flat, shallow template with no meaningful structure or navigation. The sections present contain no substantive content to organize. | 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.