cloud-sql-instance-setup
Cloud Sql Instance Setup - Auto-activating skill for GCP Skills. Triggers on: cloud sql instance setup, cloud sql instance setup Part of the GCP Skills skill category.
35
3%
Does it follow best practices?
Impact
94%
0.96xAverage 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-sql-instance-setup/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 essentially a placeholder that repeats the skill name without providing any meaningful detail about capabilities, actions, or usage triggers. It fails to describe what specific tasks the skill performs (e.g., creating instances, configuring settings, managing replicas) and provides no natural language triggers that users would actually use when needing this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures Google Cloud SQL instances, sets up database engines (MySQL, PostgreSQL, SQL Server), manages replicas, configures backups and maintenance windows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to create a Cloud SQL database, set up a GCP database instance, configure SQL database settings, or provision a managed database on Google Cloud.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'database setup', 'create SQL instance', 'GCP database', 'managed database', 'Cloud SQL configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'cloud sql instance setup' without listing any concrete actions like creating instances, configuring replicas, setting up backups, or managing connections. It's essentially just a name repeated. | 1 / 3 |
Completeness | The 'what' is extremely vague (just the skill name) and there is no explicit 'when' clause. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'cloud sql instance setup' repeated twice. Missing natural variations users would say like 'create database', 'SQL database', 'Cloud SQL', 'MySQL', 'PostgreSQL', 'database instance', or 'GCP database'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Cloud SQL' and 'GCP' provides some domain specificity that distinguishes it from generic database skills, but the lack of detail about specific capabilities could cause overlap with other GCP or database-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 actual content about Cloud SQL instance setup. It contains only auto-generated boilerplate sections that describe what the skill would do without providing any actionable guidance, commands, code, or configuration examples. It would be entirely useless to Claude when attempting to help a user set up a Cloud SQL instance.
Suggestions
Add concrete gcloud CLI commands for creating a Cloud SQL instance (e.g., `gcloud sql instances create ...` with key flags like --database-version, --tier, --region, --root-password).
Include a step-by-step workflow covering: instance creation, network configuration (private IP vs public), user/database setup, and connection testing, with validation checkpoints at each stage.
Add executable code examples for connecting to the instance from common runtimes (Python with Cloud SQL Connector, Node.js) and Terraform/IaC configuration snippets.
Reference detailed guides for advanced topics like high availability, read replicas, backups, and IAM database authentication via linked files or sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance on Cloud SQL instance setup. Every section restates the same vague idea. | 1 / 3 |
Actionability | There are zero concrete commands, code snippets, gcloud CLI examples, configuration files, or specific steps for setting up a Cloud SQL instance. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Setting up a Cloud SQL instance is a multi-step process (choosing instance type, configuring networking, setting up users, etc.) and none of these steps are mentioned, let alone sequenced with validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic boilerplate with no references to detailed guides, no links to configuration examples, and no structured navigation to deeper content. | 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
4dee593
- 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.