Automate Replicate AI model operations -- run predictions, upload files, inspect model schemas, list versions, and manage prediction history via the Composio MCP integration.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add thiagofernandes1987-create/APEX --skill replicate-automation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Replicate Automation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/thiagofernandes1987-create-replicate-automation)More formats (shields.io, HTML) on the badges page.
---
name: Replicate Automation
description: "Automate Replicate AI model operations -- run predictions, upload files, inspect model schemas, list versions, and manage prediction history via the Composio MCP integration."
requires:
mcp:
- rube
executor: HYBRID
skill_id: integrations.composio.replicate-automation
status: ADOPTED
security: {level: standard, pii: false, approval_required: false}
extends: integrations.composio.meta
toolkit: replicate-automation
# Phase3: This stub routes to the meta-skill. See skills/integrations/composio/SKILL.md for full protocol.
anchors:
- automation
- integration
- api
- workflow
tier: 3
input_schema:
- name: code_or_task
type: string
description: "Code snippet, script, or task description to process"
required: true
output_schema:
- name: result
type: object
description: "Result from the automated action"
- name: status
type: string
description: "Execution status: success | partial | failure"
what_if_fails: >
FALLBACK: If Replicate cannot complete, provide partial results with
explicit gaps noted. Never block workflow silently.
ESCALATE: If core capability is unavailable, suggest nearest alternative skill.
RULE: Always explain what failed and what manual steps can substitute.
---
# Replicate Automation
Automate your Replicate AI model workflows -- run predictions on any public model (image generation, LLMs, audio, video), upload input files, inspect model schemas and documentation, list model versions, and track prediction history.
**Toolkit docs:** [composio.dev/toolkits/replicate](https://composio.dev/toolkits/replicate)
---
## Setup
1. Add the Composio MCP server to your client: `https://rube.app/mcp`
2. Connect your Replicate account when prompted (API token authentication)
3. Start using the workflows below
---
## Core Workflows
### 1. Get Model Details and Schema
Use `REPLICATE_MODELS_GET` to inspect a model's input/output schema before running predictions.
```
Tool: REPLICATE_MODELS_GET
Inputs:
- model_owner: string (required) -- e.g., "meta", "black-forest-labs", "stability-ai"
- model_name: string (required) -- e.g., "meta-llama-3-8b-instruct", "flux-1.1-pro"
```
**Important:** Each model has unique input keys and types. Always check the `openapi_schema` from this response before constructing prediction inputs.
### 2. Run a Prediction
Use `REPLICATE_MODELS_PREDICTIONS_CREATE` to run inference on any model with optional synchronous waiting and webhooks.
```
Tool: REPLICATE_MODELS_PREDICTIONS_CREATE
Inputs:
- model_owner: string (required) -- e.g., "meta", "black-forest-labs"
- model_name: string (required) -- e.g., "flux-1.1-pro", "sdxl"
- input: object (required) -- model-specific inputs, e.g., { "prompt": "A sunset over mountains" }
- wait_for: integer (1-60 seconds, optional) -- synchronous wait for completion
- cancel_after: string (optional) -- max execution time, e.g., "300s", "5m"
- webhook: string (optional) -- HTTPS URL for async completion notifications
- webhook_events_filter: array (optional) -- ["start", "output", "logs", "completed"]
```
**Sync vs Async:** Use `wait_for` (1-60s) for fast models. For long-running jobs, omit it and use webhooks or poll via `REPLICATE_PREDICTIONS_LIST`.
### 3. Upload Files for Model Input
Use `REPLICATE_CREATE_FILE` to upload images, documents, or other binary inputs that models need.
```
Tool: REPLICATE_CREATE_FILE
Inputs:
- content: string (required) -- base64-encoded file content
- filename: string (required) -- e.g., "input.png", "audio.wav" (max 255 bytes UTF-8)
- content_type: string (default "application/octet-stream") -- MIME type
- metadata: object (optional) -- custom JSON metadata
```
### 4. Read Model Documentation
Use `REPLICATE_MODELS_README_GET` to access a model's README in Markdown format for detailed usage instructions.
```
Tool: REPLICATE_MODELS_README_GET
Inputs:
- model_owner: string (required)
- model_name: string (required)
```
### 5. List Model Versions
Use `REPLICATE_MODELS_VERSIONS_LIST` to see all available versions of a model, sorted newest first.
```
Tool: REPLICATE_MODELS_VERSIONS_LIST
Inputs:
- model_owner: string (required)
- model_name: string (required)
```
### 6. Track Prediction History and Files
Use `REPLICATE_PREDICTIONS_LIST` to retrieve prediction history, and `REPLICATE_FILES_GET`/`REPLICATE_FILES_LIST` to manage uploaded files.
```
Tool: REPLICATE_PREDICTIONS_LIST
- Lists all predictions for the authenticated user with pagination
Tool: REPLICATE_FILES_LIST
- Lists uploaded files, most recent first
Tool: REPLICATE_FILES_GET
- Get details of a specific file by ID
```
---
## Known Pitfalls
| Pitfall | Detail |
|---------|--------|
| Model-specific input keys | Each model has unique input keys and types. Using the wrong key causes validation errors. Always call `REPLICATE_MODELS_GET` first to check the `openapi_schema`. |
| File upload encoding | `REPLICATE_CREATE_FILE` requires base64-encoded content. Binary files treated as text (UTF-8) will fail with decode errors. |
| Public vs deployment paths | Public models must be run via `REPLICATE_MODELS_PREDICTIONS_CREATE`. Using deployment-oriented paths causes HTTP 404 failures. |
| Sync wait limits | `wait_for` supports 1-60 seconds only. Long-running jobs need async handling via webhooks or polling `REPLICATE_PREDICTIONS_LIST`. |
| Image model constraints | Image models like flux-1.1-pro have specific constraints (e.g., max width/height 1440px, valid aspect ratios). Check the model schema first. |
| Stale file references | Heavy usage creates many uploads. Routinely check `REPLICATE_FILES_LIST` to avoid using stale `file_id` references. |
---
## Quick Reference
| Tool Slug | Description |
|-----------|-------------|
| `REPLICATE_MODELS_GET` | Get model details, schema, and metadata |
| `REPLICATE_MODELS_PREDICTIONS_CREATE` | Run a prediction on a model |
| `REPLICATE_CREATE_FILE` | Upload a file for model input |
| `REPLICATE_MODELS_README_GET` | Get model README documentation |
| `REPLICATE_MODELS_VERSIONS_LIST` | List all versions of a model |
| `REPLICATE_PREDICTIONS_LIST` | List prediction history with pagination |
| `REPLICATE_FILES_LIST` | List uploaded files |
| `REPLICATE_FILES_GET` | Get file details by ID |
---
*Powered by [Composio](https://composio.dev)*
## Why This Skill Exists
Stub for the `replicate-automation` toolkit in the Composio integration ecosystem.
Extends `integrations.composio.meta` — see the meta-skill for full protocol.
## When to Use
Use when automating `replicate-automation` tasks via Rube MCP (Composio).
For generic Composio queries, use `integrations.composio.meta` directly.
## What If Fails
See `skills/integrations/composio/SKILL.md` (meta-skill) for full fallback protocol.
RULE: Never block workflow — always suggest manual alternative if automation fails.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!