cloud-function-generator
Cloud Function Generator - Auto-activating skill for GCP Skills. Triggers on: cloud function generator, cloud function generator Part of the GCP Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.01xAverage 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/cloud-function-generator/SKILL.mdQuality
Discovery
7%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 weak across all dimensions. It essentially just restates the skill name without describing any concrete capabilities, lacks natural trigger terms users would use, and provides no explicit guidance on when Claude should select this skill. It reads more like a placeholder than a functional skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates GCP Cloud Function boilerplate code, configures HTTP and event-driven triggers, sets up deployment configurations, and creates IAM permissions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Google Cloud Function, deploy a serverless function on GCP, set up a Cloud Functions trigger, or generate function boilerplate for Google Cloud Platform.'
Remove the duplicate trigger term ('cloud function generator' is listed twice) and expand with varied natural phrases users might say, such as 'GCF', 'serverless GCP', 'Cloud Functions Gen 2', 'Google Cloud function'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Cloud Function Generator' but does not list any concrete actions like 'creates functions', 'deploys endpoints', 'configures triggers', etc. It merely names itself without describing what it actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'cloud function generator' repeated twice. It misses natural user phrases like 'GCP function', 'serverless function', 'Cloud Functions', 'deploy function', 'HTTP trigger', or 'Google Cloud Functions'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'GCP' and 'Cloud Function' provides some domain specificity that narrows it to Google Cloud Platform serverless functions, but the lack of detail about what exactly it generates or how it differs from other GCP-related skills creates potential overlap. | 2 / 3 |
Total | 5 / 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 describes what it would do in abstract terms but provides no actual instructions, code, commands, or workflows for generating cloud functions on GCP. It fails on every dimension because it contains zero actionable information.
Suggestions
Add concrete, executable code examples showing how to create and deploy a GCP Cloud Function (e.g., `gcloud functions deploy` commands, sample function code in Python/Node.js, and `cloudfunctions.json` configuration).
Define a clear multi-step workflow: scaffold function → write handler → test locally → deploy → validate deployment, with explicit validation checkpoints at each stage.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching Claude how to perform the task.
Include specific GCP patterns such as HTTP triggers vs. Pub/Sub triggers, environment variable configuration, IAM permissions, and common pitfalls with concrete examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous. The entire file explains what the skill is rather than providing any actual instructions or knowledge. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code snippets, no commands, no specific configurations, no actual steps for generating cloud functions. The content only describes the skill abstractly without instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | No bundle files exist and no references are provided. The content is a monolithic block of meta-description with no structure pointing to detailed materials or examples. | 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.