Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

couchbase-capella

Estrelas4

Forks1

Atualizado28 de maio de 2026 às 04:35

Provision, configure, and manage Couchbase Capella deployments. Use whenever the user asks about Capella cluster setup, Capella free tier, Capella trial, creating a Capella cluster, Capella pricing tiers, Capella compute tiers, database credentials, Capella allowed CIDRs, Capella VPC peering, Capella AWS PrivateLink, Azure Private Endpoint, Capella App Services setup, Capella networking, Capella database users vs cluster admin, Capella organizations, Capella projects, Capella connection strings, or 'how do I get started with Capella / set up Capella for production.' Distinct from couchbase-sizing (which has a Capella tier reference) and couchbase-security-hardening (which covers TLS and RBAC). This skill covers Capella as a product — provisioning, networking, credentials, and connecting your application to it.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

celticht32

celticht32/Couchbase-Skills-for-Claude.ai

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

Explorador de arquivos

4 arquivos

SKILL.md

readonly

name	couchbase-capella
description	Provision, configure, and manage Couchbase Capella deployments. Use whenever the user asks about Capella cluster setup, Capella free tier, Capella trial, creating a Capella cluster, Capella pricing tiers, Capella compute tiers, database credentials, Capella allowed CIDRs, Capella VPC peering, Capella AWS PrivateLink, Azure Private Endpoint, Capella App Services setup, Capella networking, Capella database users vs cluster admin, Capella organizations, Capella projects, Capella connection strings, or 'how do I get started with Capella / set up Capella for production.' Distinct from couchbase-sizing (which has a Capella tier reference) and couchbase-security-hardening (which covers TLS and RBAC). This skill covers Capella as a product — provisioning, networking, credentials, and connecting your application to it.
license	MIT

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 math
couchbase-security-hardening — TLS, RBAC, and audit configuration once the cluster is running
couchbase-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 tier
couchbase-backup-restore — managing Capella backups
couchbase-mobile — Capella App Services for mobile sync
couchbase-observability — Capella monitoring integration
couchbase-security-hardening — RBAC and TLS on Capella

Mais deste repositório

mesmo repositório

couchbase-ai-applications

celticht32/Couchbase-Skills-for-Claude.ai

Design and build AI-powered applications on Couchbase, including RAG pipelines, vector search architecture, embedding strategies, and AI agent data patterns. Use whenever the user asks about RAG, retrieval-augmented generation, vector search for AI, Hyperscale Vector Index (HVI), Composite Vector Index (CVI), Search Vector Index (SVI), embedding pipelines, semantic search, AI agent memory, grounding LLMs with Couchbase, agentic data patterns, billion-scale vector search, multi-vector search, AI application architecture, or 'how do I build an AI app with Couchbase.' Distinct from couchbase-fts (which covers FTS index mechanics and query syntax) — this skill is about end-to-end AI application design: the data model, embedding pipeline, index type selection, retrieval strategy, and integration with LLM frameworks. Use proactively when the user is building AI features or has a use case involving language models, embeddings, or semantic retrieval.

2026-07-044

couchbase-coding-standards

celticht32/Couchbase-Skills-for-Claude.ai

Apply coding standards and a style guide for writing production application code against Couchbase, combining general software-engineering best practices (naming, functions, error handling, testing, docstrings, version control, code review, secrets hygiene) with Couchbase-specific conventions (SDK idioms, document-key naming, exception and retry handling, durability, parameterized SQL++, connection lifecycle). Use whenever the user asks about coding standards, code style, a style guide, clean code, naming conventions, structuring Couchbase application code, idiomatic SDK usage, how to write or review Couchbase code, code-review checklists, linting, formatting, testing Couchbase code, or best practices for writing Couchbase apps. Distinct from couchbase-app-integration (SDK mechanics: pooling, durability, scan consistency) and couchbase-data-modeling (document design) — this is the how-to-write-and-review-the-code layer on top of them. Use proactively when reviewing or authoring code that touches Couchbase.

2026-07-044

couchbase-columnar

celticht32/Couchbase-Skills-for-Claude.ai

Design and use Couchbase Capella Analytics (formerly Capella Columnar), the standalone columnar analytics database service on Capella. Use whenever the user asks about Capella Analytics, Capella Columnar, columnar analytics, an Analytics instance, Capella Analytics vs the operational Analytics Service, Analytics collections, links to operational data, Analytics SQL++, pricing, when to use standalone Capella Analytics vs the embedded Analytics Service, or 'I need to run analytical queries on my Couchbase data.' Distinct from the cb-analytics-* skills (which cover the Couchbase Analytics Service embedded in Couchbase Server / Capella operational clusters) — Capella Analytics is a separate, standalone columnar database product on Capella. Use proactively when the user needs OLAP-scale analytics, BI tool integration, or columnar storage for analytical workloads.

2026-07-044

couchbase-eventing

celticht32/Couchbase-Skills-for-Claude.ai

Design, deploy, and troubleshoot Couchbase Eventing functions. Use whenever the user asks about Eventing, eventing functions, JavaScript functions on document mutations, source bucket, metadata bucket, source keyspace, metadata keyspace, OnUpdate, OnDelete, cron triggers, curl() in eventing, N1QL in eventing, eventing deployment state (deployed / undeployed / paused), eventing worker count, DCP feed, Eventing service, admin_eventing_* tools, or 'how do I run code when a document changes.' Distinct from couchbase-mcp (calling the tools) and couchbase-app-integration (SDK-based change notification via DCP/Kafka). Use proactively when the user has a change-driven processing need: cache warming, audit logging, cross-collection sync, event publishing, or derived document generation.

2026-07-044

couchbase-fts

celticht32/Couchbase-Skills-for-Claude.ai

Design, build, and tune Couchbase Full Text Search (FTS) and vector search indexes. Use whenever the user asks about FTS indexes, Search service, text search, full-text search, fuzzy search, phrase search, wildcard search, regex search, geo search, geo-distance, geo-bounding-box, facets, scoring, boosting, analyzers, tokenizers, custom analyzers, language analyzers, type mappings, dynamic mappings, child mappings, FTS index design, FTS synonyms (8.x), vector search, kNN search, vector index, embedding search, hybrid search (FTS + vector), cb_fts_search, admin_fts_*, BLEVE, or 'how do I search text in Couchbase.' Distinct from couchbase-sqlpp-tuning (SQL++ index design) and couchbase-mcp (operating the tools). Use proactively when the user has a search use case — text relevance, semantic similarity, geo-proximity, or faceted navigation.

2026-07-044

couchbase-magma

celticht32/Couchbase-Skills-for-Claude.ai

Understand and tune the Magma storage engine in Couchbase. Use whenever the user asks about Magma, Magma storage engine, Couchbase storage backend, couchstore vs Magma, 128 vBuckets vs 1024 vBuckets, Magma compaction, Magma memory requirements, Magma disk layout, storage engine selection, when to use Magma vs couchstore, storageBackend bucket setting, numVBuckets bucket setting, or 'which storage engine should I use.' Distinct from couchbase-sizing (which has a brief Magma section in disk.md) — this skill covers Magma behavior, tradeoffs, and tuning in depth. Use proactively when the user is creating new buckets on 8.0 or is investigating storage-related performance issues.

2026-07-044

name	couchbase-capella
description	Provision, configure, and manage Couchbase Capella deployments. Use whenever the user asks about Capella cluster setup, Capella free tier, Capella trial, creating a Capella cluster, Capella pricing tiers, Capella compute tiers, database credentials, Capella allowed CIDRs, Capella VPC peering, Capella AWS PrivateLink, Azure Private Endpoint, Capella App Services setup, Capella networking, Capella database users vs cluster admin, Capella organizations, Capella projects, Capella connection strings, or 'how do I get started with Capella / set up Capella for production.' Distinct from couchbase-sizing (which has a Capella tier reference) and couchbase-security-hardening (which covers TLS and RBAC). This skill covers Capella as a product — provisioning, networking, credentials, and connecting your application to it.
license	MIT

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 math
couchbase-security-hardening — TLS, RBAC, and audit configuration once the cluster is running
couchbase-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.

Related skills

couchbase-sizing — choosing the right Capella compute tier
couchbase-backup-restore — managing Capella backups
couchbase-mobile — Capella App Services for mobile sync
couchbase-observability — Capella monitoring integration
couchbase-security-hardening — RBAC and TLS on Capella