bigtable-basics
Assists in provisioning instances/tables, designing performant schemas, and querying data in Bigtable. Use when designing Bigtable row keys, configuring column families, writing SQL queries or client library code (Java, Go, Python) for Bigtable, or diagnosing performance/hotspotting issues. Also use when provisioning Bigtable clusters using gcloud or cbt CLIs. Don't use for generic Cloud SQL administration.
Security Assessment
About bigtable-basics
Bigtable Basics is a cloud database administration and development skill providing core workflows for provisioning, schema design, querying, and performance diagnosis on Google Bigtable. It solves the recurring challenges of a NoSQL wide-column store: designing performant row keys, configuring column families, choosing the right query API, and avoiding hotspotting and expensive full-table scans.
The skill establishes a clear control-plane vs data-plane split (gcloud for instances, clusters, app profiles, backups, IAM, and view/table creation; the cbt CLI for table/column-family updates and reading/writing data), and emphasizes performance-first design tied to row-key structure, prefer Java or Go clients for production, and observability through Key Visualizer, the hot-tablets tool, and table stats. It includes a prominent safety rule requiring explicit user confirmation before any non-emulator database change, and reminding the operator to surface that requirement whenever proposing structure- or data-modifying commands. Reference files cover infrastructure management (provisioning, backup/restore, emulator use), CLI data access (lookups, ranges, SQL reads, writes, deletes), schema design and hotspotting, structured row keys via SQL, high-performance Go/Java/Python client patterns, and Dataplex catalog discovery. It also recommends Terraform for production schema changes to prevent accidental data loss.
It targets cloud engineers, backend developers, and data platform teams building on or operating Bigtable. While it documents commands that create, modify, and delete instances, tables, and rows, these are standard administrative operations gated behind an explicit confirmation safety rule and directed at the user's own resources.
FAQ
When should I use gcloud vs cbt?
Use gcloud for control-plane operations (instances, clusters, app profiles, backups, IAM, and creating tables/views). Use the cbt CLI for data-plane operations (updating tables and column families, and reading/writing data).
How does it help with performance?
It centers design on row-key structure to avoid hotspotting and unbounded scans, recommends exact/prefix/range predicates on the key, and points to Key Visualizer, hot-tablets, and table stats for diagnosing slow queries.
Does it guard against destructive changes?
Yes. It states an explicit safety rule that you must obtain user confirmation before non-emulator database changes, and must mention that requirement when providing commands that modify structure or data. It also recommends Terraform for production schema changes.
Which client languages are recommended?
For production, prefer Java or Go for their performance and feature coverage; the skill also provides Python patterns. A reference file covers high-performance client-library patterns.
Can I develop locally?
Yes. The skill documents the Bigtable emulator (gcloud beta emulators bigtable start) and how to point cbt and client libraries at it, noting the emulator does not yet support Bigtable GoogleSQL.
All Files
8 filesInstall bigtable-basics
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
google/skills