alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB MCP tools for automated database operations including AI-powered search and vector capabilities.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 3.3w
- Forks
- 3.9k
01 前言 Front Matter
- name
- alloydb-basics
- metadata
- { "source": "google/skills (Apache 2.0)" }
- description
- Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB MCP tools for automated database operations including AI-powered search and vector capabilities.
02 资源文件 11
- 参考文档references/best_practices.md11.8 KB
- 参考文档references/cli-usage.md1.2 KB
- 参考文档references/client-library-usage.md5.4 KB
- 参考文档references/concatenation.md10.3 KB
- 参考文档references/core-concepts.md2.1 KB
- 参考文档references/data_structure.md8.5 KB
- 参考文档references/iac-usage.md3.2 KB
- 参考文档references/iam-security.md4.3 KB
- 参考文档references/io_operations.md9.2 KB
- 参考文档references/manipulation.md11.6 KB
- 参考文档references/mcp-usage.md1.3 KB
03 SKILL.md 正文
AlloyDB Basics
AlloyDB for PostgreSQL is a managed, PostgreSQL-compatible database service designed for enterprise-grade performance and availability. It utilizes a disaggregated compute and storage architecture to scale resources independently. It also provides AlloyDB AI, a collection of features that includes AI-powered search (vector, hybrid search, and AI functions), natural language capabilities, conversational analytics, and inference features like forecasting and model endpoint management to help developers build AI apps faster.
Quick Start
-
Enable the AlloyDB API:
gcloud services enable alloydb.googleapis.com --quiet -
Create a Cluster:
gcloud alloydb clusters create my-cluster --region=us-central1 \ --password=my-password --network=my-vpc \ --quietNote: For production, we recommend using IAM database authentication instead of passwords. If passwords must be used, use secure secret management (e.g., Secret Manager) instead of passing passwords in cleartext.
-
Create a Primary Instance:
gcloud alloydb instances create my-primary --cluster=my-cluster \ --region=us-central1 --instance-type=PRIMARY --cpu-count=2 \ --quiet
Reference Directory
-
Core Concepts: Architecture, disaggregated storage, and performance features.
-
CLI Usage: Essential
gcloud alloydbcommands for cluster and instance management. -
Client Libraries & Connectors: Connecting to AlloyDB using Python, Java, Node.js, and Go.
-
MCP Usage: Using the AlloyDB remote MCP server and Gemini CLI extension.
-
Infrastructure as Code: Terraform configuration and deployment examples.
-
IAM & Security: Predefined roles, service agents, and database authentication.
If you need product information not found in these references, use the
Developer Knowledge MCP server search_documents tool.
04 同仓库更多 Skills
wealthville-pool-scoring
Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.
technical-debt-auditor
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.
readonly-sql-guard
Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
discernment-nudge
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.