cloud-function-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cloud-function-generatorCloud Function Generator - Auto-activating skill for GCP Skills. Triggers on: cloud function generator, cloud function generator Part of the GCP Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing meaningful trigger guidance. It lacks concrete actions, natural user keywords, and explicit 'Use when...' clauses. The redundant trigger terms and circular self-reference provide no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates, deploys, and configures Google Cloud Functions including HTTP triggers, Pub/Sub triggers, and Cloud Storage triggers.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions GCP functions, serverless on Google Cloud, Cloud Functions, gcf, or needs to deploy event-driven code to Google Cloud.'
Remove the redundant trigger term and add variations users would naturally say, such as 'serverless', 'GCF', 'Google Cloud Functions', 'event-driven functions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Cloud Function Generator' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'creates', 'deploys', 'configures', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a circular reference to the skill name. There's no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('cloud function generator' listed twice) and overly specific. Missing natural variations users would say like 'serverless function', 'GCP function', 'deploy function', 'lambda equivalent', or 'Cloud Functions'. | 1 / 3 |
Distinctiveness Conflict Risk | The GCP/Cloud Function focus provides some distinctiveness from general coding skills, but 'cloud function' could overlap with AWS Lambda or Azure Functions skills. The lack of specific GCP terminology weakens differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive guidance. It describes what a cloud function generator skill should do without providing any actual instructions, code examples, GCP-specific configurations, or workflows. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add executable code examples showing how to create GCP Cloud Functions (e.g., using gcloud CLI commands or Python/Node.js function templates)
Define a clear workflow: 1) Create function code, 2) Configure trigger type, 3) Deploy with specific gcloud commands, 4) Validate deployment
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with concrete GCP-specific guidance like runtime options, memory/timeout settings, and authentication patterns
Add references to detailed documentation for different trigger types (HTTP, Pub/Sub, Cloud Storage, Firestore) in separate files if needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty filler that Claude doesn't need to be told. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no commands, and no actual instructions on how to generate cloud functions. The content only describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or processes documented. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed documentation, examples, or related files. There's no structure that enables discovery of actual implementation details. | 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.