Replicate Automation
Automate Replicate AI model operations -- run predictions, upload files, inspect model schemas, list versions, and manage prediction history via the Composio MCP integration.
Get the complete skill folder, including its scripts and reference files.
This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.
When to use this skill
Use Replicate Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Replicate AI model operations -- run predictions, upload files, inspect model schemas, list versions, and manage prediction history via the Composio MCP integration.
When not to use it
Skip Replicate Automation when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/replicate-automation # Save SKILL.md to ~/.claude/skills/replicate-automation/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/replicate-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/replicate-automation/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Replicate Automation skill for this task: Use Replicate Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 80/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamainferred
The skill text mentions Llama or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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)*
Intended uses
- Use Replicate Automation when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.