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.
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-subscription-configActivation
22%This description is severely underdeveloped, functioning more as a label than a useful skill description. It lacks any concrete actions, has no explicit usage triggers, and repeats the same trigger term twice without adding meaningful keywords. The description would leave Claude unable to determine when to select this skill over others.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, configures, and manages GCP Pub/Sub subscriptions including push/pull settings, acknowledgment deadlines, and retry policies.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when configuring Pub/Sub subscribers, setting up message delivery, managing subscription settings, or working with GCP messaging queues.'
Include common keyword variations users might say: 'Pub/Sub', 'pubsub', 'subscription', 'subscriber', 'message queue', 'push subscription', 'pull subscription', '.tf files for pubsub'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('pubsub subscription config') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'create', 'configure', 'manage', 'deploy', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions listed) and 'when should Claude use it' (no explicit 'Use when...' clause). The trigger terms are redundantly repeated without adding value. | 1 / 3 |
Trigger Term Quality | Contains 'pubsub subscription config' which is a relevant technical term, but lacks natural variations users might say like 'Pub/Sub', 'subscription settings', 'message queue', 'subscriber', or 'GCP messaging'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'pubsub subscription config' term is fairly specific to GCP Pub/Sub, but without describing specific capabilities, it could overlap with other GCP or messaging-related skills. The category mention helps somewhat. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about GCP Pub/Sub subscription configuration. It contains only meta-descriptions of what a skill should do without any concrete guidance, code examples, configuration snippets, or technical information. The skill provides zero value as it teaches Claude nothing about the actual task.
Suggestions
Add concrete code examples showing how to create and configure Pub/Sub subscriptions using gcloud CLI or Terraform
Include specific configuration options (ack deadline, retention, dead letter topics, push vs pull) with example values
Provide a clear workflow for common subscription configuration tasks with validation steps
Replace generic capability descriptions with actual technical guidance and best practices for Pub/Sub subscriptions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about pubsub subscription configuration. Every section describes what the skill does abstractly rather than providing concrete guidance. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The content only describes capabilities in vague terms like 'provides step-by-step guidance' without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for configuring pubsub subscriptions. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, no links to related files, and no structured navigation. The content is a shallow placeholder with no depth or organization of actual technical content. | 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.