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 extremely weak across all dimensions. It is essentially a label rather than a functional description - it names the topic ('Cloud Run Service Config') but provides zero information about what actions the skill performs, what problems it solves, or when it should be triggered. The duplicate trigger term adds no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures Cloud Run services including setting environment variables, scaling parameters, memory/CPU limits, traffic splitting, and revision management.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to configure, deploy, or modify Google Cloud Run services, service.yaml files, or container deployment settings on GCP.'
Diversify trigger terms to include natural variations users would say: 'Cloud Run', 'GCP container deployment', 'service.yaml', 'Cloud Run scaling', 'Cloud Run environment variables', 'serverless container config'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It merely names 'Cloud Run Service Config' without describing what it actually does - no verbs like 'configure', 'deploy', 'manage', or any specific capabilities are listed. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the description only states it's an 'auto-activating skill' without explaining what it accomplishes or under what circumstances it should be selected. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'cloud run service config' repeated twice identically. Missing natural variations users would say like 'deploy cloud run', 'GCP container service', 'Cloud Run YAML', 'service configuration', 'Cloud Run deployment settings', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Cloud Run Service Config' and 'GCP' provides some domain specificity that narrows it to Google Cloud Platform's Cloud Run service, but without describing specific actions it could easily overlap with other GCP or Cloud Run related 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 substantive content about Cloud Run service configuration. It contains only generic boilerplate headings and placeholder text that provide zero actionable guidance. It needs to be completely rewritten with actual Cloud Run configuration content, examples, and commands.
Suggestions
Add concrete, executable examples such as gcloud CLI commands for deploying/configuring Cloud Run services (e.g., `gcloud run deploy`, `gcloud run services update`) and example service.yaml configurations.
Include a clear workflow for common Cloud Run service config tasks (e.g., setting env vars, configuring concurrency, memory/CPU limits, scaling) with validation steps like `gcloud run services describe`.
Remove all generic filler text ('Provides step-by-step guidance', 'Follows industry best practices') and replace with specific Cloud Run configuration patterns, constraints, and gotchas.
Add references to related configuration topics (e.g., IAM permissions, VPC connectors, custom domains) either inline or via linked files for progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about Cloud Run service configuration, and every section is generic template text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no YAML snippets, no gcloud CLI usage. Every bullet point is vague and abstract (e.g., 'Provides step-by-step guidance' without actually providing any). | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured navigation, and no bundle files exist. The content is a shallow placeholder with no depth or organization beyond generic headings. | 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.