# Provision Backend Infrastructure with Cohesivity

Building an application often requires coordinating many backend providers, credentials, and consoles. This skill provisions Cohesivity services through one guarded workflow and API.

## Install

```bash
npx skillstore add cohesivity-org/cohesivity
```

## Metadata

- Status: approved
- Slug: cohesivity-org-cohesivity
- Version: 2923f0623a63
- Author version: 2923f0623a63
- Skillstore revision: r1
- Version status: invalid
- Tree hash: 623312a5aa280e6e477cf54e5e4caeef2539ea2aa32af7b99ea6ec27de707b89
- Author: cohesivity-org
- GitHub username: cohesivity-org
- License: MIT
- Repository: https://github.com/cohesivity-org/cohesivity-plugin/tree/357c8bdaa7d2204e714033f5de42befe1e6dbf48/skills/cohesivity
- Ref: 5526951beaeca22519572a471618555839b53b05
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/cohesivity-org-cohesivity
- Manifest: https://skillstore.pages.dev/api/skills/cohesivity-org-cohesivity/manifest

## Capabilities

- Creates or reuses Cohesivity project tenants through MCP tools or a version-pinned initializer.
- Provisions databases, storage, hosting, authentication, realtime, email, browser, and AI API resources.
- Guides authenticated server-side calls to Cohesivity control-plane and data-plane endpoints.
- Manages tenant status, claiming, billing, and upgrades behind explicit approval gates.
- Uses live resource documentation to obtain current endpoints, limits, pricing, and operational requirements.
- Keeps management and application keys outside browser, mobile, and client-side bundles.

## Use Cases

- Launch an Application Backend: Provision a database, authentication, storage, and hosting for a new application without managing separate provider consoles.
- Add Managed Services: Attach Redis, realtime messaging, email, vector storage, or model APIs to an existing project.
- Operate Project Infrastructure: Check tenant status, review quotas, claim temporary projects, and perform approved billing actions.

## Prompt Templates

### Create a Basic Backend

```
Create a Cohesivity backend for my project with Postgres and authentication. Explain the proposed tenant change and wait for required approval.
```

### Add a Managed Service

```
Inspect this project for an existing Cohesivity configuration. Add Redis using current service documentation and request approval before provisioning.
```

### Deploy a Server Application

```
Prepare this server application for Cohesivity hosting. Review deployment files, protect secrets, show expected costs, and request approval before upload.
```

### Design a Multi-Service Architecture

```
Design a Cohesivity architecture using Postgres, vector storage, inbox, realtime, and an AI gateway. Verify live limits and stage every mutation for approval.
```

## Limitations

- Requires network access to Cohesivity and may require an available Cohesivity MCP integration.
- Fresh tenants expire after 72 hours and have strict resource caps until claimed.
- Current APIs, limits, and pricing depend on mutable remote documentation.
- Durable state, paid actions, upgrades, and managed agents require explicit user approval.

## Best Practices

- Reuse an existing valid tenant and read credentials only from the protected project configuration.
- Fetch current resource documentation, summarize the planned effect, and obtain explicit authorization before every mutation.
- Keep all Cohesivity keys server-side and redact them from logs, screenshots, chat, and deployment output.

## Anti Patterns

- Do not create duplicate tenants when a valid project configuration or MCP tenant already exists.
- Do not send direct control-plane mutations that bypass MCP confirmation checks.
- Do not retry non-idempotent top-ups or cross billing and durable-state gates without explicit approval.

## Security Audit

- Audited at: 2026-09-12T00:41:48.825\+00:00
- Summary: Most external-command alerts are Markdown false positives. Two findings direct a version-pinned npx installer, while network access and local credential reuse are core behavior. Mutable live documentation can change operational instructions after marketplace review, creating a high-confidence remote instruction supply-chain risk.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0