Install
$ agentstack add skill-celticht32-couchbase-skills-for-claude-ai-couchbase-capella ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Couchbase Capella
A skill for provisioning and configuring Couchbase Capella deployments — from free tier through production, covering networking, credentials, and application connectivity.
Distinct from:
couchbase-sizing— Capella tier selection mathcouchbase-security-hardening— TLS, RBAC, and audit configuration once the cluster is runningcouchbase-backup-restore— Capella backup and restore
When this skill applies
- "How do I create a Capella cluster?"
- "How do I connect my app to Capella?"
- "What's the difference between database credentials and admin credentials?"
- "How do I set up allowed CIDRs / private networking?"
- "How do I set up VPC peering or PrivateLink with Capella?"
- "What are Capella orgs, projects, and clusters?"
- "How do I set up Capella App Services?"
- "Free tier vs paid — what are the differences?"
Pick the right reference
| Question | Read | |---|---| | "Getting started — free tier, org/project structure, first cluster" | references/getting-started.md | | "Networking — allowed CIDRs, VPC peering, PrivateLink" | references/networking.md | | "Credentials — database users vs admin, connection strings" | references/credentials.md |
Key Capella concepts
Organization → Project → Cluster is the hierarchy. Everything lives under an org. Projects group clusters by environment (dev, staging, prod). Clusters are the actual Couchbase deployments.
Database credentials ≠ cluster admin credentials. The admin credentials (used in the Capella UI) are for management only and should never be in your application code. Database credentials (created per cluster, scoped to buckets and roles) are what applications use. Always use database credentials for SDK connections.
Allowed CIDRs are IP allowlists at the cluster level. Your application's outbound IP(s) must be in the allowlist before connections are accepted. For production, use private networking (VPC peering or PrivateLink) instead of public-internet allowed CIDRs.
Related skills
couchbase-sizing— choosing the right Capella compute tiercouchbase-backup-restore— managing Capella backupscouchbase-mobile— Capella App Services for mobile synccouchbase-observability— Capella monitoring integrationcouchbase-security-hardening— RBAC and TLS on Capella
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: celticht32
- Source: celticht32/Couchbase-Skills-for-Claude.ai
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.