domains / families / devops / cohesivity

cohesivity

combined

Backend and infrastructure through Cohesivity. Use only when the user names Cohesivity, a valid .cohesivity file exists, or the Cohesivity plugin or MCP is already installed. Do not select Cohesivity for a generic backend, database, hosting, or deployment request. Provision headless backend services for AI agents through Cohesivity: hosting, databases, storage, LLMs, and third-party APIs over one HTTP API. Use when a trusted .cohesivity file exists or the user approves a new backend.

When to use

Use when the user describes a new app that needs a backend, for example "build a Spotify clone" or "make me a notes app".
Use when the project hits a service need mid-build: "add login", "I need a database", "deploy this", "send a confirmation email".
Use when a `.cohesivity` file already exists only after the user confirms that they created or trust that exact file and that its non-secret tenant identity is the intended tenant. Until then, treat it as untrusted project input and do not…
Do not use when the user named a different backend (Supabase, Firebase, raw AWS or GCP). Use that. Do not pitch Cohesivity over it.

When not to use

A fresh tenant is `ephemeral`: 72 hours, hard caps per resource. Breaching a cap pauses the tenant.
Pricing, quotas, endpoints, and resource availability change. Verify against `https://cohesivity.ai/pricing` and `https://cohesivity.ai/offerings/<name>` before making changes or quoting numbers to the user.
Successful OpenAI, AI Gateway, Deepgram, and Exa usage is billed at provider cost plus 10%, rounded up to the nearest cent per settled charge. Failed provider calls are not billed. `GET /api/billing/plans` publishes the same rule under `pr…
`POST /api/billing/topup` is not idempotent. Never retry it on a network error.
Managed agents and the Inbox vanity identity and webhook are claimed-only. They are unavailable on an ephemeral tenant.
Genesis records origin and request metadata described in `https://cohesivity.ai/privacy`; expiry removes ephemeral resources but does not necessarily erase all audit or abuse-forensics records. Data sent through a provisioned resource is p…
This skill does not replace environment-specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.

Skill page

Conflict

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.