Agent Skills

compare-models

researchreplicate1.7K installs

Compare Replicate models by cost, speed, quality, and capabilities.

Install

npx skills add https://github.com/replicate/skills --skill compare-models
SKILL.md

Docs

Workflow

  1. Search or browse collections to build a shortlist of candidate models.
  2. Fetch each model's schema to compare inputs, outputs, and capabilities.
  3. Check pricing from model metadata or the Replicate website.
  4. Run a small batch of test predictions to compare output quality.
  5. Pick the model that best fits your constraints (cost, latency, quality).

What to compare

  • Speed: Check metrics.predict_time on completed predictions for actual inference time. Official models are always warm. Community models can cold-boot.
  • Cost: Official models have predictable per-run pricing. Community models charge by compute time (GPU-seconds). Run a few predictions and check the metrics field for actual cost.
  • Quality: Run the same prompts through each model and compare outputs. Quality is subjective. Match it to your use case, not a leaderboard.
  • Capabilities: Compare input schemas for supported features (reference images, masks, aspect ratios, streaming, multi-image input). Check output formats.

Key tradeoffs

  • Lowest cost: smaller/distilled models. Accept slower inference and lower quality.
  • Lowest latency: official models or schnell/turbo variants. Accept higher cost per run.
  • Highest quality: pro/max/quality variants. Accept slower inference and higher cost.
  • Most control: models with ControlNet, masks, or reference images. Accept more complex input setup.

Official vs community models

  • Official models: always warm, stable APIs, predictable pricing, maintained by Replicate.
  • Community models: may cold-boot, require version pinning, maintained by the author.
  • If a community model meets your needs and an official model doesn't, consider creating a deployment for consistent uptime.

Prompting guidance

For prompting techniques and task-specific guidance:

Related skills

researchmattpocock575KInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.paper-context-resolverlllllllama451KRigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing Renv-and-assets-bootstraplllllllama450KRigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.ai-research-explorelllllllama311KRigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow c

Search skills and MCP servers

Fuzzy search across 23,137 skills and servers