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 extremely minimal and essentially just restates the skill name without providing any meaningful detail about capabilities, use cases, or trigger scenarios. It reads as auto-generated boilerplate rather than a crafted description that would help Claude select the right skill from a large pool. It needs substantial improvement across all dimensions.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures Google Cloud SQL instances, sets up MySQL/PostgreSQL/SQL Server databases, configures networking and access, manages replicas and backups.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about setting up a Cloud SQL database, creating a GCP database instance, configuring MySQL or PostgreSQL on Google Cloud, or managing Cloud SQL networking and permissions.'
Include common user-facing keywords and variations such as 'Google Cloud SQL', 'GCP database', 'MySQL instance', 'PostgreSQL instance', 'SQL Server on GCP', 'database setup', and 'cloud database provisioning'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Cloud Sql Instance Setup' repeated in the trigger line. It does not describe any concrete actions like creating instances, configuring replicas, setting up connections, or managing databases. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with 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 Cloud SQL database', 'set up MySQL/PostgreSQL on GCP', 'provision SQL instance', or 'Google Cloud 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 what specific setup tasks it covers 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 generic auto-generated boilerplate that provides zero actionable guidance—no gcloud commands, no Terraform configurations, no networking setup, no validation steps. 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, --availability-type).
Include a step-by-step workflow covering: instance creation, network configuration (private IP/authorized networks), user setup, database creation, and connection testing with explicit validation at each step.
Add production-ready configuration examples (Terraform or gcloud) covering common patterns like HA setup, private IP with VPC peering, automated backups, and maintenance windows.
Replace the generic 'Example Triggers' and 'Capabilities' sections with actual technical content such as instance tier recommendations, connection string formats, and IAM configuration.
| 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. 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, configuration examples, or related documentation. There is no meaningful structure or navigation. | 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
933cf26
- 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.