cloud-run-service-config
Cloud Run Service Config - Auto-activating skill for GCP Skills. Triggers on: cloud run service config, cloud run service config Part of the GCP Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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-run-service-config/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 severely underdeveloped, essentially just naming the skill without explaining what it does or when to use it. The redundant trigger terms and lack of concrete actions make it nearly useless for skill selection among multiple options. It reads more like a placeholder than a functional skill description.
Suggestions
Add specific actions the skill performs, e.g., 'Configures Cloud Run services including memory limits, CPU allocation, scaling parameters, environment variables, and traffic splitting.'
Add a 'Use when...' clause with natural trigger terms like 'deploy container to GCP', 'cloud run configuration', 'serverless deployment', 'container scaling', or 'GCP service yaml'.
Remove the duplicate trigger term and expand with variations users would naturally say when needing Cloud Run configuration help.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain 'Cloud Run Service Config' but provides no concrete actions. There are no verbs describing what the skill actually does (e.g., deploy, configure, scale, manage). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('cloud run service config' listed twice) and overly technical. Missing natural variations users might say like 'deploy to cloud run', 'GCP container service', 'serverless containers', or 'cloud run yaml'. | 1 / 3 |
Distinctiveness Conflict Risk | Being part of 'GCP Skills' category and mentioning 'Cloud Run' provides some specificity, but without describing actual capabilities, it could conflict with other GCP-related skills or general cloud deployment skills. | 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 an empty template with no actual content about Cloud Run service configuration. It contains only generic boilerplate text that could apply to any skill topic, providing no executable guidance, no code examples, no configuration patterns, and no GCP-specific information whatsoever.
Suggestions
Add concrete Cloud Run service configuration examples (service.yaml, gcloud run deploy commands with common flags)
Include specific configuration patterns: CPU/memory allocation, concurrency settings, environment variables, secrets mounting, VPC connectors
Provide a clear workflow for deploying and validating a Cloud Run service with explicit steps and validation checkpoints
Add references to related documentation or example files for advanced topics like traffic splitting, custom domains, or IAM configuration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Cloud Run service configuration. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no configuration snippets, no actual Cloud Run service.yaml examples or gcloud commands. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for configuring a Cloud Run service, no validation checkpoints, and no sequence of operations. The skill provides no procedural guidance whatsoever. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed resources. No references to configuration examples, API documentation, or related guides are provided. | 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
b8a3b3e
- 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.