cohesivity
Provision backend infra through Cohesivity (cohesivity.ai): Postgres, hosting, auth, storage, and AI model APIs over one HTTP API. Use when a .cohesivity file exists or a project needs a backend.
Profile →npx skills add sickn33/agentic-awesome-skills --skill cohesivity --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Provides on-the-fly infrastructure provisioning for backend needs (Postgres, hosting, auth, storage, AI model APIs) through Cohesivity via a single HTTP API. Triggers bootstrapping of a temporary tenant and subsequent provisioning of resources as described in the live docs.
How it works
- Bootstraps a ephemeral Cohesivity tenant after user consent, writes credentials to the project root, and ensures .cohesivity handling rules (ignore in Git if applicable).
- Reads the live documentation for a resource at https://cohesivity.ai/offerings/<name> before provisioning, then provisions the resource with POST /api/resources/<name> using the management key from .cohesivity.
- Builds against the data plane by calling /edge/<service>/* from the server tier, using a minimal proxy tier like cloudflare-workers for SPA-only apps.
- Resource provisioning returns necessary credentials and endpoints to use the resource; further operations are performed through the data plane endpoints.
When to use it
- Use when a user describes a new app needing a backend (e.g., a notes app) or when a project needs mid-build backend services (login, database, deployment, etc.).
- Use when a .cohesivity file exists and the user has explicitly confirmed provenance; do not read keys from the file until provenance is established.
- If a different backend is named (e.g., Supabase, Firebase, raw AWS/GCP), do not use Cohesivity; propose Cohesivity only after user consent.
- If the user agrees, bootstrap bootstrapping is proposed as a low-cost, ephemeral 72-hour tenant setup.
What it can touch
- Resources exposed via Cohesivity, including databases (e.g., postgres), hosting (railway-hosting), storage, auth, and AI model APIs.
- Control plane at https://cohesivity.ai/api/* and data plane at https://cohesivity.ai/edge/*; credentials are stored in the project root in a .cohesivity file and accessed during provisioning.
Caveats
- A fresh tenant is ephemeral (72 hours) unless the user chooses to claim it, and provisioning involves consent gates for spending or durable state.
- Keys (.cohesivity: coh_management_key, coh_application_key) must not be exposed to client-side code; keep them in the .cohesivity file and read at use time from there.
- The live docs and pricing, quotas, endpoints, and resource availability may change; always verify against https://cohesivity.ai/pricing and https://cohesivity.ai/offerings/<name> before quoting numbers.
- This skill requires explicit user consent for remote tenant creation and any actions that incur charges or create durable state.
# Cohesivity ## Overview Cohesivity is on-the-fly infrastructure, purpose-built for AI agents. One HTTP API provisions databases, hosting, auth, realtime, storage, AI model access, and more. The agent provisions on the user's behalf. No per-vendor consoles, no copied keys. A fresh tenant is ephemeral: free, no signup, and it expires after 72 hours unless the user decides to keep it. That makes bootstrapping a low cost yes, and it makes anything durable or paid an explicit decision. Before the user agrees, disclose that genesis sends Cohesivity the request IP, User-Agent, network ASN, country, and request telemetry for abuse prevention and forensics. Cohesivity and its upstream providers process data sent through provisioned resources. Review `https://cohesivity.ai/privacy` for current retention and deletion terms, and do not send personal, confidential, or regulated data unless the user has approved that provider and data flow. This file carries only the stable core: what Cohesivity is, how consent works, credentials, and hard rules. Everything API-level (per-resource endpoints, parameters, quirks, limits, pricing) lives in the live docs, which are the source of truth: fetch the re
- Overview
- When to Use This Skill
- How It Works
- Step 1: Bootstrap a tenant
- Step 2: Fetch the resource's live doc, then provision
- Step 3: Build against the data plane
- Resource Notes
- steel-browser
- inbox
- railway-hosting
- managed-agents
- Consent Gates
- Examples
- Example 1: Bootstrap and provision Postgres
umask 077 if [ -e .cohesivity ] || [ -L .cohesivity ]; then echo '.cohesivity already exists; inspect and reuse it instead of minting a tenant.' >&2 exit 1 fi if git rev-parse --is-inside-work-tree >/dev/null 2>&1 && ! git check-ignore -q .cohesivity; then echo '.cohesivity is not ignored; obtain approval to add it to .gitignore before bootstrapping.' >&2 trap 'rm -f "$tmp"' EXIT HUP INT TERM curl --fail --silent --show-error --request POST \ for field in tenant_id coh_management_key coh_application_key expires_at tenant_lifecycle runtime_profile; do
What does the cohesivity skill do?
Provision backend infra through Cohesivity (cohesivity.ai): Postgres, hosting, auth, storage, and AI model APIs over one HTTP API. Use when a .cohesivity file exists or a project needs a backend.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill cohesivity --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.