Index of every page on this site: llms.txt
All skills
davila7 avatar

/alloydb-basics

@053feb2
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/alloydb-basics

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈52 tokens for metadata: the name and description. ≈543 when used: this file. ≈4.5k more on demand in 6 files.

Description uses 2.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈210 characters, or 2.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

  1. Enable the AlloyDB API:

    gcloud services enable alloydb.googleapis.com --quiet
  2. Create a Cluster:

    gcloud alloydb clusters create my-cluster --region=us-central1 \
        --password=my-password --network=my-vpc \
        --quiet

    Note: 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.

  3. 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

If you need product information not found in these references, use the Developer Knowledge MCP server search_documents tool.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert6d3 checks · Risk SAFE
  • Gen Agent Trust Hub6d

    The skill is a comprehensive documentation set and template collection for managing AlloyDB for PostgreSQL. It follows security best practices by providing explicit warnings against cleartext passwords and recommending IAM authentication. While it references external tools and presents a minor surface for indirect prompt injection through its command templates, these are standard characteristics of technical documentation.

  • Socket6d

    No alerts

  • Snyk6d

    Risk: CRITICAL · 2 issues

Signed by skilld at 053feb2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
metadata
{
  "source": "google/skills (Apache 2.0)"
}

README badge

README badge for davila7/claude-code-templates/alloydb-basics