Supabase Development and Debugging
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
A skill your agent uses when making, reviewing, debugging, or scripting Runware API requests.
$ npx skills add LayrKits/Sprite-Pipeline --skill runware-api -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LayrKits/Sprite-Pipeline runware-api --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LayrKits/Sprite-Pipeline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/runware-api .claude/skills/runware-api && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "runware-api" agent skill from https://github.com/LayrKits/Sprite-Pipeline/tree/main/skills/runware-api into .claude/skills/runware-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runware-api", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LayrKits/Sprite-Pipeline/tree/main/skills/runware-apiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LayrKits/Sprite-Pipeline --skill runware-api -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LayrKits/Sprite-Pipeline runware-api --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LayrKits/Sprite-Pipeline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/runware-api .agents/skills/runware-api && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "runware-api" agent skill from https://github.com/LayrKits/Sprite-Pipeline/tree/main/skills/runware-api into .agents/skills/runware-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runware-api", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LayrKits/Sprite-Pipeline --skill runware-api -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LayrKits/Sprite-Pipeline runware-api --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LayrKits/Sprite-Pipeline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/runware-api .cursor/skills/runware-api && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "runware-api" agent skill from https://github.com/LayrKits/Sprite-Pipeline/tree/main/skills/runware-api into .cursor/skills/runware-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runware-api", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LayrKits/Sprite-Pipeline.git --path skills/runware-api--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LayrKits/Sprite-Pipeline --skill runware-api -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LayrKits/Sprite-Pipeline runware-api --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LayrKits/Sprite-Pipeline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/runware-api .gemini/skills/runware-api && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "runware-api" agent skill from https://github.com/LayrKits/Sprite-Pipeline/tree/main/skills/runware-api into .gemini/skills/runware-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runware-api", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LayrKits/Sprite-Pipeline runware-apiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LayrKits/Sprite-Pipeline --skill runware-api -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LayrKits/Sprite-Pipeline.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/runware-api .github/skills/runware-api && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "runware-api" agent skill from https://github.com/LayrKits/Sprite-Pipeline/tree/main/skills/runware-api into .github/skills/runware-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runware-api", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LayrKits/Sprite-Pipeline --skill runware-api -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LayrKits/Sprite-Pipeline runware-api --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LayrKits/Sprite-Pipeline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/runware-api .opencode/skills/runware-api && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "runware-api" agent skill from https://github.com/LayrKits/Sprite-Pipeline/tree/main/skills/runware-api into .opencode/skills/runware-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "runware-api", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
runware-apiA skill your agent uses when making, reviewing, debugging, or scripting Runware API requests.
Runware API is an agent skill from LayrKits/Sprite-Pipeline. Use when making, reviewing, debugging, or scripting Runware API requests. Follow Runware's raw REST/WebSocket request shape, authentication, UUID, async polling, error, retry, and model-selection rules.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Realtime and WebSockets. The repository describes itself as: 2D Sprite Sheet Creation Pipeline.
Read from SKILL.md and the folder at commit df08816. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
python3From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
runware.aiapi.runware.aiFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
RUNWARE_API_KEYAPI_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Runware API loads about 1.1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 466 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- Never commit API keys, `.env` files, generated request payloads containingAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Without a licence we can't republish the file, so here is its outline and opening line. It has 466 words (~1,093 tokens).
“Use this skill when working with Runware requests in this repo. Prefer the current Runware docs for model-specific parameters, because available models and capabilities change often.”
Just SKILL.md in skills/runware-api of LayrKits/Sprite-Pipeline.
Open the folder on GitHubat commit df08816
Runware API next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Runware API this skillLayrKits/Sprite-Pipeline | 594 | — | ~1.1k | Automated safety check: Notes | None | |
| Supabase Development and Debuggingsupabase/agent-skills | 2.7k | 3 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Gemini Live API Devgoogle-gemini/gemini-skills | 4.3k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Web3 PolymarketPolymarket/agent-skills | 191 | 2 repos | ~2k | Automated safety check: Pass | None | |
| GraphQL ArchitectJeffallan/claude-skills | 12k | 1 repos | ~1.3k | Automated safety check: Pass | MIT |
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
google-gemini/gemini-skills
A skill your agent uses when building real-time, bidirectional streaming applications with the Gemini Live API, or migrating legacy Live models (2.0/2.5/3.1) to Gemini 3.8 Live.
Polymarket/agent-skills
Polymarket integration for prediction market trading on Polygon.
Jeffallan/claude-skills
Designs GraphQL schemas and Apollo Federation graphs, with DataLoader resolvers, subscriptions, query complexity limits and caching.
marketcalls/openalgo
Integrate a new Indian broker into OpenAlgo, or modify an existing broker plugin.
LayrKits/Sprite-Pipeline
Guide an AI assistant through this repo's 2D animation sprite-sheet workflow.
Categories
A skill your agent uses when making, reviewing, debugging, or scripting Runware API requests. Runware API is an agent skill from LayrKits/Sprite-Pipeline. Use when making, reviewing, debugging, or scripting Runware API requests.
Runware API fits situations like: scripting Runware API requests; tasks that involve Realtime and WebSockets.
Run `npx skills add LayrKits/Sprite-Pipeline --skill runware-api -a claude-code`. Or copy the skill folder (skills/runware-api in LayrKits/Sprite-Pipeline) into .claude/skills/runware-api in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LayrKits/Sprite-Pipeline --skill runware-api -a codex`. Or copy the skill folder (skills/runware-api in LayrKits/Sprite-Pipeline) into .agents/skills/runware-api in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LayrKits/Sprite-Pipeline --skill runware-api -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/runware-api, .gemini/skills/runware-api, .github/skills/runware-api and .opencode/skills/runware-api in your project.
Going by SKILL.md and its folder, Runware API needs the command-line tools its instructions call (python3) and credentials named RUNWARE_API_KEY and API_KEY. Our summary lists: Python 3; A credential in API_KEY; A credential in RUNWARE_API_KEY.
SKILL.md names 2 domains. In commands or code: runware.ai and api.runware.ai; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
No licence was found for Runware API or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Runware API: Supabase Development and Debugging (supabase/agent-skills, 2.7k stars), Use Yaak (mountain-loop/yaak, 19k stars), Gemini Live API Dev (google-gemini/gemini-skills, 4.3k stars) and Web3 Polymarket (Polymarket/agent-skills, 191 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LayrKits (a GitHub user) maintains it in LayrKits/Sprite-Pipeline, which has 594 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on May 10, 2026.
Source: LayrKits/Sprite-Pipeline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.