ericrisco/rsc-harness / skills/replicate
replicate
VerifiedUse when running, packaging, deploying or scaling a model on the Replicate platform from code — blocking run versus async predictions, handling FileOutput, deployments with warm private endpoints and autoscaling, packaging with Cog, verifying webhook signatures, and cutting GPU spend. NOT crafting image prompts and parameters or picking image model families (that is `replicate-images`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.3 KB |
| evals/README.md | markdown | 685 B |
| evals/cases.yaml | config | 3.0 KB |
| references/cog-packaging.md | markdown | 4.3 KB |
| references/deployments-api.md | markdown | 3.0 KB |
| references/webhooks-and-async.md | markdown | 4.0 KB |
| scripts/verify.shexecutable | script | 6.0 KB |
references/deployments-api.md
View on GitHub# Deployments API — full reference
Source: https://replicate.com/docs/topics/deployments (accessed 2026-06-02).
A deployment is a private, dedicated endpoint pointing at one model version. It autoscales from zero
to hundreds of instances, keeps a warm floor if you ask, caps spend with a ceiling, and lets you swap
hardware without touching `predict.py`. Updates roll out with no downtime.
## Config fields
| Field | Meaning | Cost/latency effect |
|---|---|---|
| `model` | `owner/model` the deployment serves | — |
| `version` | the immutable version SHA to run | pin it; bump via update |
| `hardware` | e.g. `gpu-t4`, `gpu-a100-large`, `gpu-h100` | bigger = faster + pricier |
| `min_instances` | warm floor (>=0) | >0 kills cold starts but bills idle 24/7 |
| `max_instances` | concurrency ceiling | the hard spend cap under spikes |
Start `min_instances: 0` (scale to zero) and only raise it when measured cold-start latency hurts
users. Set `max_instances` deliberately — it is your protection against a traffic spike becoming a
surprise bill.
## Create / update via HTTP API
```bash
# create
curl -s -X POST https://api.replicate.com/v1/deployments \
-H "Authorization: Bearer $REPLICATE_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "my-endpoint",
"model": "owner/model",
"version": "<version-sha>",
"hardware": "gpu-a100-large",
"min_instances": 1,
"max_instances": 5
}'
# update (rolling — bump version or rescale with no downtime)
curl -s -X PATCH https://api.replicate.com/v1/deployments/owner/my-endpoint \
-H "Authorization: Bearer $REPLICATE_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"version": "<new-version-sha>", "min_instances": 2}'
```
## Via the Python client
```python
client = replicate.Client()
client.deployments.create(
name="my-endpoint",
model="owner/model",
version="<version-sha>",
hardware="gpu-a100-large",
min_instances=1,
max_instances=5,
)
# scale or roll a new version
client.deployments.update("owner/my-endpoint", min_instances=2, version="<new-sha>")
```
## Calling a deployment
You call it like any model — the deployment just routes to your private instances:
```python
deployment = client.deployments.get("owner/my-endpoint")
prediction = deployment.predictions.create(input={"prompt": "..."})
prediction.reload()
```
Async + webhook works the same: pass `webhook=` / `webhook_events_filter=` to the deployment's
`predictions.create`.
## Rolling updates
Updating `version` rolls new instances in and drains old ones with no downtime. Because versions are
immutable SHAs, you can roll back by updating `version` to the previous SHA. Never depend on "latest" —
pin the SHA so a teammate's `cog push` does not silently change what the endpoint serves.
## Monitoring
The dashboard and API expose per-deployment **latency, throughput, error rate, and GPU memory**. Watch
GPU memory to right-size hardware, and error rate after every rolling update — a spike right after a
version bump means roll back to the prior SHA.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |