domains / devops / backend-provisioning / cohesivity

cohesivity

Skill card

combined

The two skills describe the same service (Cohesivity) but have fundamentally different activation logic and security procedures. The first skill (davepoon) is a 'plugin-first' skill that relies on MCP servers for bootstrap and explicitly forbids manual HTTP calls to the genesis endpoint, while the second skill (sickn33) is a 'direct-API' skill that provides a specific bash script for manual bootstrap and includes strict privacy/telemetry disclosures and file-permission checks that the first lacks. Because they disagree on the core bootstrap mechanism (MCP vs. direct HTTP) and the second contains critical safety steps (privacy disclosure, gitignore checks, umask) absent from the first, neither is a simple reproduction of the other.

Repositories

Other copies

Combined skill

---
name: cohesivity
description: Provision headless backend services for AI agents through Cohesivity. Use when the user names Cohesivity, a trusted .cohesivity file exists, or the user approves a new backend.
category: infrastructure-cloud
---

# Cohesivity

## Overview
Cohesivity is on-the-fly infrastructure for AI agents. One HTTP API provisions databases, hosting, auth, and more.

## Activation & Consent
1. **Triggers:** Activate if the user names Cohesivity, a valid `.cohesivity` file exists (after user confirmation of provenance), or the user explicitly approves using Cohesivity for a new backend.
2. **Privacy Disclosure:** Before bootstrapping, disclose that Cohesivity collects IP, User-Agent, and telemetry for abuse prevention. Do not send regulated data without explicit approval.
3. **Consent Gates:** Ephemeral bootstrap (72h) is low-cost. Durable state, paid actions, or plan upgrades require explicit user approval.

## Bootstrap Procedure
**Option A: MCP Available (Preferred for Claude Code)**
If the Cohesivity MCP is installed, use the `create_tenant` tool. Do not hand-roll HTTP calls.

**Option B: Direct API (Manual)**
If MCP is unavailable, use the following secure bootstrap script. Ensure `.cohesivity` is in `.gitignore`.

```bash
umask 077
if [ -e .cohesivity ]; then echo 'Exists'; exit 1; fi
if git rev-parse --is-inside-work-tree >/dev/null 2>&1 && ! git check-ignore -q .cohesivity; then echo 'Not ignored'; exit 1; fi
tmp="$(mktemp .cohesivity.tmp.XXXXXX)"
curl --fail --silent --show-error --request POST \
  --header 'User-Agent: agentic-awesome-skills:claude-code' \
  --output "$tmp" https://cohesivity.ai/api/genesis
# Validate fields: tenant_id, coh_management_key, coh_application_key, expires_at, tenant_lifecycle, runtime_profile
mv "$tmp" .cohesivity
```

## Architecture
- **Control Plane:** `https://cohesivity.ai/api/*` (Auth: `Bearer <coh_management_key>`)
- **Data Plane:** `https://cohesivity.ai/edge/*` (Auth: `?key=<coh_application_key>`)

## Hard Rules
- **Secrets:** Never expose `coh_management_key` or `coh_application_key` in client-side code.
- **User-Agent:** Always send a non-default User-Agent to avoid WAF 403 errors.
- **Docs:** Fetch live docs at `https://cohesivity.ai/offerings/<name>` for specific resource parameters.