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 fails to communicate what the skill actually does beyond naming its domain. It lacks any concrete actions, has no explicit 'Use when...' guidance, and repeats the same trigger term twice without adding variations. It would be very difficult for Claude to confidently select this skill from a large pool based on this description alone.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, configures, and manages GCP Pub/Sub subscriptions including pull/push delivery, acknowledgment deadlines, retry policies, and dead letter topics.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to create, modify, or troubleshoot Google Cloud Pub/Sub subscriptions or subscription-related configurations.'
Expand trigger terms to include natural variations users would say: 'Pub/Sub', 'pubsub subscriber', 'subscription configuration', 'pull subscription', 'push subscription', 'ack deadline', 'message retention', '.tf pubsub'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names the domain ('pubsub subscription config') without describing what the skill actually does—no verbs like 'create', 'configure', 'manage', or 'troubleshoot' are present. | 1 / 3 |
Completeness | The 'what does this do' is essentially absent—there are no described capabilities. The 'when' is only implied through trigger terms but lacks an explicit '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 identically and misses natural variations users might say like 'Pub/Sub', 'subscription configuration', 'pull subscription', 'push subscription', 'dead letter queue', 'ack deadline', or 'GCP pubsub'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'pubsub subscription config' provides some specificity within GCP, but without describing concrete actions, it could overlap with other GCP Pub/Sub-related skills (e.g., topic config, general Pub/Sub management). The niche is somewhat defined but not clearly delineated. | 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 a hollow placeholder that provides no actual content about Pub/Sub subscription configuration. It contains only meta-descriptions of what it claims to do without any concrete instructions, code, commands, or examples. It fails on every dimension of the rubric.
Suggestions
Add concrete gcloud CLI commands and/or Terraform configurations for creating and configuring Pub/Sub subscriptions (e.g., `gcloud pubsub subscriptions create ...` with key flags like --ack-deadline, --push-endpoint, --dead-letter-topic).
Include a clear workflow with steps: create topic → create subscription → configure settings → validate with `gcloud pubsub subscriptions describe` → test with a publish/pull cycle.
Add specific configuration examples covering common subscription types (pull vs push, dead-letter policies, retry policies, exactly-once delivery) with copy-paste ready code.
Remove all the meta-description sections ('Purpose', 'When to Use', 'Example Triggers') that provide no actionable value and replace with actual technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, commands, or configurations for Pub/Sub subscription setup. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no Terraform/gcloud commands, no code snippets, no configuration examples, no specific parameters. The content only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. Claims to provide 'step-by-step guidance' but none is actually present. There are no sequences, validation checkpoints, or error recovery instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no meaningful organization. There are no references to detailed files, no quick-start section with real content, and no navigation to deeper resources. | 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
3e83543
- 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.