rw-check-compatibility

Included with Lifetime

$97 forever

Analyze a user's codebase to verify it can use Runway's public API (server-side requirement)

Backend & APIs

What this skill does


# Check Compatibility

Analyze the user's project to determine whether it is compatible with Runway's public API.

## Why This Matters

Runway's public API **requires server-side invocation**. The API key must never be exposed in client-side code. Projects that are purely frontend (static HTML/JS, client-only SPAs without a backend) cannot safely call the API.

## Analysis Steps

### Step 1: Identify the Project Type

Search the project root for these files to determine the stack:

| File | Indicates |
|------|-----------|
| `package.json` | Node.js project |
| `requirements.txt`, `pyproject.toml`, `Pipfile`, `setup.py` | Python project |
| `go.mod` | Go project |
| `Cargo.toml` | Rust project |
| `pom.xml`, `build.gradle` | Java/Kotlin project |
| `Gemfile` | Ruby project |
| `composer.json` | PHP project |

If none of these exist, flag the project as **unknown** and ask the user what language/runtime they're using.

### Step 2: Check for Server-Side Capability

Look for indicators of a server/backend:

**Node.js projects — check `package.json` dependencies for:**
- `express`, `fastify`, `koa`, `hapi`, `nest`, `hono` → HTTP server framework
- `next` → Next.js (has API routes — compatible)
- `nuxt` → Nuxt.js (has server routes — compatible)
- `remix` → Remix (has loaders/actions — compatible)
- `@sveltejs/kit` → SvelteKit (has server routes — compatible)
- `astro` → Astro (has API endpoints if SSR enabled)

**Python projects — check for:**
- `flask`, `django`, `fastapi`, `starlette`, `tornado`, `aiohttp`, `sanic` → web server framework
- `streamlit`, `gradio` → can make server-side calls

**Red flags (frontend-only):**
- `package.json` with only `react`, `vue`, `svelte`, `angular` and NO server framework
- `vite.config.ts` or `webpack.config.js` with no server/SSR configuration
- Static site generators without server routes (e.g., plain Gatsby, plain Eleventy)
- `index.html` as the only entry point with inline `<script>` tags

### Step 3: Check for Existing Runway SDK

Search for existing Runway SDK installations:

**Node.js:**
- Check `package.json` for `@runwayml/sdk`
- Search for `import RunwayML` or `require('@runwayml/sdk')` in source files

**Python:**
- Check `requirements.txt` / `pyproject.toml` for `runwayml`
- Search for `from runwayml import RunwayML` or `import runwayml` in source files

### Step 4: Check Runtime Version

**Node.js:** Must be version 18 or higher (`node --version`)
**Python:** Must be version 3.8 or higher (`python3 --version`)

### Step 5: Check for Environment Variable Support

Look for `.env` file, `.env.example`, `.env.local`, or dotenv configuration:
- Node.js: `dotenv` in dependencies, or framework-native env support (Next.js, etc.)
- Python: `python-dotenv` in dependencies, or framework-native support

## Report Format

After analysis, provide a clear report:

```
## Runway API Compatibility Report

**Project type:** [Node.js / Python / etc.]
**Server-side capable:** [Yes / No / Partial]
**Runtime version:** [version] — [Compatible / Needs upgrade]
**Runway SDK installed:** [Yes / No]
**Environment variable support:** [Yes / No / Needs setup]

### Verdict: [COMPATIBLE / NEEDS CHANGES / INCOMPATIBLE]

[If COMPATIBLE]
Your project is ready for Runway API integration. Proceed with API key setup.

[If NEEDS CHANGES]
Your project needs the following changes:
1. [List specific changes needed]

[If INCOMPATIBLE]
Your project is frontend-only and cannot safely call Runway's API. Options:
1. **Add a backend** — Add an Express/FastAPI server or use a framework with server routes (Next.js, SvelteKit, etc.)
2. **Use a serverless function** — Add API routes via Vercel Functions, AWS Lambda, Cloudflare Workers, etc.
3. **Create a separate backend** — Build a thin API proxy that your frontend calls
```

## Important Notes

- **Never suggest embedding the API key in client-side code.** This is a security risk.
- If the project uses Next.js, Remix, SvelteKit, Nuxt, or Astro with SSR, it IS compatible — the server-side route handlers can call the API.
- Serverless platforms (Vercel, Netlify, AWS Lambda, Cloudflare Workers) are compatible.
- Docker/containerized apps are compatible if they run a server process.

## After Compatibility Check

If the project is compatible, suggest the user proceed with `+rw-setup-api-key` to configure their API credentials.

Files: 1

Size: 4.6 KB

Complexity: 12/100

Category: Backend & APIs

Source: https://github.com/runwayml/skills/tree/main/skills/rw-check-compatibility

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts