Agent skill

Supabase CI Integration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Configure Supabase continuous-integration and deployment pipelines with GitHub Actions: link projects, push migrations, deploy Edge Functions, generate types, and run tests against local Supabase…

MITAuto-check passedDevOps & Cloud

Install Supabase CI Integration

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-ci-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace supabase-ci-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/supabase-ci-integration .claude/skills/supabase-ci-integration && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "supabase-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/supabase-ci-integration into .claude/skills/supabase-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supabase-ci-integration", 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

$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/supabase-ci-integration

Type 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.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-ci-integration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace supabase-ci-integration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/supabase-ci-integration .agents/skills/supabase-ci-integration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "supabase-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/supabase-ci-integration into .agents/skills/supabase-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supabase-ci-integration", 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.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-ci-integration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace supabase-ci-integration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/supabase-ci-integration .cursor/skills/supabase-ci-integration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "supabase-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/supabase-ci-integration into .cursor/skills/supabase-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supabase-ci-integration", 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

$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/supabase-ci-integration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-ci-integration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace supabase-ci-integration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/supabase-ci-integration .gemini/skills/supabase-ci-integration && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "supabase-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/supabase-ci-integration into .gemini/skills/supabase-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supabase-ci-integration", 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.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace supabase-ci-integration

Installs 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).

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-ci-integration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/supabase-ci-integration .github/skills/supabase-ci-integration && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "supabase-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/supabase-ci-integration into .github/skills/supabase-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supabase-ci-integration", 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.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-ci-integration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace supabase-ci-integration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/supabase-ci-integration .opencode/skills/supabase-ci-integration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "supabase-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/supabase-ci-integration into .opencode/skills/supabase-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supabase-ci-integration", 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.

Facts

Skill name: supabase-ci-integration
GitHub stars: 2.8k
Token cost: ~2k tokens
SKILL.md length: 733 words
Files: 6 (incl. references)
Skills in repo: 3,342
Repo updated: Oct 10, 2026
First seen: Oct 8, 2026
Licence: MIT

At a glance

Configure Supabase continuous-integration and deployment pipelines with GitHub Actions: link projects, push migrations, deploy Edge Functions, generate types, and run tests against local Supabase…

Works in 3 steps: Configure GitHub Secrets and Link in CI → CI Workflow — Test, Validate Migrations,… → Deploy Migrations and Edge Functions on…
Setting up CI pipelines for Supabase
SKILL.md covers Overview, Prerequisites, Instructions and Preview Branches, plus 6 more sections
Calls npx, supabase and gh; needs SUPABASE_ACCESS_TOKEN and SUPABASE_DB_PASSWORD

What it does

Supabase CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Supabase continuous-integration and deployment pipelines with GitHub Actions: link projects, push migrations, deploy Edge Functions, generate types, and run tests against local Supabase instances. Use when setting up CI pipelines for Supabase, automating database migrations, deploying Edge Functions in CI, or running integration tests. Trigger with phrases like "supabase CI", "supabase GitHub Actions", "supabase deploy pipeline", "CI supabase migrations", "supabase preview branches".

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/ci-workflows.md`, `references/errors.md` and `references/examples.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering CI/CD. It works with Supabase, GitHub Actions and GitHub. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

Setting up CI pipelines for Supabase
Automating database migrations
Deploying Edge Functions in CI
Running integration tests

Example prompts

“supabase CI”
“supabase GitHub Actions”
“supabase deploy pipeline”
“/supabase-ci-integration”

Requirements

Node.js
Docker
A credential in SUPABASE_ACCESS_TOKEN
Compatibility (from SKILL.md): Designed for Claude Code
Pre-approved tools (allowed-tools): Write, Bash(npx:*), Bash(gh:*)

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Configure GitHub Secrets and Link in CI
CI Workflow — Test, Validate Migrations, and Generate Types
Deploy Migrations and Edge Functions on Merge

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Write
- Bash(npx:*)
- Bash(gh:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npx
- supabase
- gh
- npm
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- supabase.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- SUPABASE_ACCESS_TOKEN
- SUPABASE_DB_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.

Context cost

Supabase CI Integration loads about 2k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 131 tokens; SKILL.md has 733 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~131
When it runs · the whole SKILL.md, loaded when a task matches: ~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~4.5k

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.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated 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.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 733 words, ~2,031 tokens.

Download SKILL.mdSave it as .claude/skills/supabase-ci-integration/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.

name: supabase-ci-integration
description: Configure Supabase continuous-integration and deployment pipelines with GitHub Actions: link projects, push migrations, deploy Edge Functions, generate types, and run tests against local Supabase instances. Use when setting up CI pipelines for Supabase, automating database migrations, deploying Edge Functions in CI, or running integration tests. Trigger with phrases like "supabase CI", "supabase GitHub Actions", "supabase deploy pipeline", "CI supabase migrations", "supabase preview branches".
allowed-tools: Write, Bash(npx:*), Bash(gh:*)
compatibility: Designed for Claude Code
version: 1.54.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: saas, supabase, ci-cd, github-actions, devops

Supabase CI Integration

Overview

Build GitHub Actions workflows that automate the full Supabase lifecycle: link projects in CI, push migrations on merge, deploy Edge Functions, generate TypeScript types, run tests against a local Supabase instance, and create preview branches for pull requests. Every database change gets validated before it reaches production.

The pull-request CI pipeline runs these stages, all detailed in ci-workflows.md:

Start a local Supabase instance (unused services disabled for speed).
Apply every migration from scratch with npx supabase db reset.
Regenerate TypeScript types and fail the build on drift from the committed version.
Run pgTAP database tests and the application test suite against the local instance.
Stop Supabase (always, even on failure).

Prerequisites

GitHub repository with Actions enabled
Supabase project created at supabase.com/dashboard
Supabase CLI initialized locally (npx supabase init)
Node.js 18+ in your project
@supabase/supabase-js installed:

bash

npm install @supabase/supabase-js

Instructions

Step 1: Configure GitHub Secrets and Link in CI

Store credentials as GitHub repository secrets. The CI pipeline uses these to authenticate with your Supabase project without exposing tokens in code.

bash

# Set secrets via GitHub CLI
gh secret set SUPABASE_ACCESS_TOKEN --body "<your-access-token>"
gh secret set SUPABASE_DB_PASSWORD --body "<your-database-password>"
gh secret set SUPABASE_PROJECT_REF --body "<your-project-ref>"

Generate your access token at supabase.com/dashboard/account/tokens. Find your project ref in Project Settings > General.

Link the project in any CI job that needs remote access:

yaml

- name: Install Supabase CLI
  uses: supabase/setup-cli@v1
  with:
    version: latest

- name: Link Supabase project
  run: npx supabase link --project-ref ${{ secrets.SUPABASE_PROJECT_REF }}
  env:
    SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}

Step 2: CI Workflow — Test, Validate Migrations, and Generate Types

Add .github/workflows/supabase-ci.yml that runs on every pull request. It starts a local Supabase instance, runs db reset to apply all migrations from scratch, regenerates types and fails on drift (git diff --exit-code), then runs pgTAP and application tests. The default local dev keys are safe to commit — they only work against the local instance. Copy the complete workflow from ci-workflows.md.

Step 3: Deploy Migrations and Edge Functions on Merge

Add .github/workflows/supabase-deploy.yml, scoped with paths: to supabase/migrations/** and supabase/functions/** so it only runs when database or function code changes on main. It links the remote project, runs npx supabase db push, deploys Edge Functions, and regenerates types from the production schema. Full workflow in ci-workflows.md.

Preview Branches

Create isolated Supabase environments per pull request with npx supabase branches create, so reviewers test against real infrastructure with migrations applied. Preview branches require a Supabase Pro plan and incur compute costs while running. Workflow snippet in ci-workflows.md.

Testing in CI

Two test layers run inside the CI workflow:

pgTAP database tests in supabase/tests/ validate that RLS is enabled on public tables and that policies behave correctly. Run locally with npx supabase test db.
Application tests use createClient from @supabase/supabase-js pointed at http://127.0.0.1:54321 with the local anon key.

Both patterns — the pgTAP SQL and the TypeScript client setup — are in testing-patterns.md.

Show full SKILL.md (305 more words)Show less

Output

After implementing these workflows:

Pull requests run tests against a fresh local Supabase instance with all migrations applied
TypeScript type drift is detected automatically — stale types block the PR
Database migrations deploy to production only on merge to main
Edge Functions deploy alongside migration changes
pgTAP tests validate RLS policies and schema constraints in CI
Preview branches provide isolated environments for PR review (Pro plan)
GitHub secrets keep SUPABASE_ACCESS_TOKEN and SUPABASE_DB_PASSWORD out of code

Error Handling

Error	Cause	Solution
`supabase start` fails in CI	Docker not available	Use `ubuntu-latest` runner (includes Docker by default)
`supabase db push` returns "permission denied"	Invalid or expired access token	Regenerate token at supabase.com/dashboard/account/tokens
`supabase link` fails	Wrong project ref	Check project ref in Settings > General, must match `SUPABASE_PROJECT_REF` secret
Type drift detected in PR	Schema changed without regenerating types	Run `npx supabase gen types typescript --local > src/types/database.types.ts`
`supabase functions deploy` fails	Missing Deno types or syntax errors	Run `npx supabase functions serve` locally first to catch issues
pgTAP tests fail	Missing RLS policies or schema constraints	Add policies before merging — `npx supabase test db` runs locally
Preview branch creation fails	Free plan limitation	Preview branches require Supabase Pro plan
Migration conflict on push	Divergent migration history	Run `npx supabase db pull` to reconcile remote vs local migrations

Examples

Minimal CI for a new project — just migration validation and type checking:

yaml

name: Supabase CI
on: [pull_request]
jobs:
  validate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: supabase/setup-cli@v1
        with: { version: latest }
      - run: npx supabase start -x realtime,storage-api,imgproxy,inbucket,edge-runtime
      - run: npx supabase db reset
      - run: npx supabase gen types typescript --local > /tmp/types.ts && diff src/types/database.types.ts /tmp/types.ts
      - if: always()
        run: npx supabase stop

For the full CI + deploy + preview workflows and an Edge Function deploy-with-verification snippet, see ci-workflows.md.

Resources

Supabase CLI in CI/CD — official setup guide
Database Testing with pgTAP — writing and running database tests
Managing Environments — staging, production, preview branches
Edge Functions Deployment — deploying Deno functions
Type Generation — keeping TypeScript types in sync
Branching & Preview — per-PR database environments
@supabase/supabase-js Reference — client SDK documentation

Next Steps

For deploying Supabase-backed applications to hosting platforms, see supabase-deploy-integration. For configuring RLS policies, see supabase-rls-policies.

Files

SKILL.md and 5 other files (references) in skills/.curated/supabase-ci-integration of jeremylongshore/tons-of-skills-marketplace.

SKILL.md
references/ci-workflows.md
references/errors.md
references/examples.md
references/implementation.md
references/testing-patterns.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Supabase CI Integration 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.

Supabase CI Integration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Supabase CI Integration this skilljeremylongshore/tons-of-skills-marketplace	2.8k	—	~2k	Automated safety check: Pass	MIT	yesterday
Data Scraper Agentaffaan-m/ECC	277k	5 repos	~6.3k	Automated safety check: Notes	MIT	today
Data Scraper Agentaffaan-m/ECC	276k	1 repos	~5.2k	Automated safety check: Notes	MIT	yesterday
Data Scraper Agentaffaan-m/ECC	276k	—	~377	Automated safety check: Pass	MIT	yesterday
Nushellccusage/ccusage	19k	—	~938	Automated safety check: Pass	Custom licence	today
Make GitHub Actions Workflowdotnet/efcore	15k	—	~2.1k	Automated safety check: Pass	MIT	yesterday

Similar skills

Data Scraper Agent
affaan-m/ECC
Build a fully automated AI-powered data collection agent for any public source — job boards, prices, news, GitHub, sports, anything.
277k GitHub starsUsed in 5 repos~6.3k tokens
DevOps & CloudAuto-check: notes
Data Scraper Agent
affaan-m/ECC
构建一个全自动化的AI驱动数据收集代理，适用于任何公共来源——招聘网站、价格信息、新闻、GitHub、体育赛事等任何内容。按计划进行抓取，使用免费LLM（Gemini Flash）丰富数据，将结果存储在Notion/Sheets/Supabase中，并从用户反馈中学习。完全免费在GitHub Actions上运行。适用于用户希望自动监控、收集或跟踪任何公共数据的场景。
276k GitHub starsUsed in 1 repo~5.2k tokens
DevOps & CloudAuto-check: notes
Data Scraper Agent
affaan-m/ECC
任意のパブリックソース（ジョブボード、価格、ニュース、GitHub、スポーツなど）用の完全自動化されたAI搭載データ収集エージェントを構築します。スケジュールでスクレイプし、無料LLM（Gemini Flash）でデータを豊かにし、Notion/Sheets/Supabaseに結果を保存し、ユーザーフィードバックから学習します。GitHub…
276k GitHub stars~377 tokensUpdated yesterday
DevOps & CloudAuto-check passed
Nushell
ccusage/ccusage
Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.
19k GitHub stars~938 tokensUpdated today
DevOps & CloudAuto-check passed
Make GitHub Actions Workflow
dotnet/efcore
Official
Create GitHub Actions workflows for CI, automation, or PR management.
15k GitHub stars~2.1k tokensUpdated yesterday
DevOps & CloudAuto-check passed
AI News Radar
LearnPrompt/ai-news-radar
A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…
1.8k GitHub stars~2.5k tokensUpdated today
DevOps & CloudAuto-check: notes

Questions about Supabase CI Integration

What does Supabase CI Integration do?

Configure Supabase continuous-integration and deployment pipelines with GitHub Actions: link projects, push migrations, deploy Edge Functions, generate types, and run tests against local Supabase…. Supabase CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Supabase continuous-integration and deployment pipelines with GitHub Actions: link projects, push migrations, deploy Edge Functions, generate types, and run tests against local Supabase instances.

When should I use Supabase CI Integration?

Supabase CI Integration fits situations like: setting up CI pipelines for Supabase; automating database migrations; deploying Edge Functions in CI; running integration tests.

How do I install Supabase CI Integration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-ci-integration -a claude-code`. Or copy the skill folder (skills/.curated/supabase-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/supabase-ci-integration in your project. Claude Code loads it when a task matches its description.

How do I install Supabase CI Integration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-ci-integration -a codex`. Or copy the skill folder (skills/.curated/supabase-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/supabase-ci-integration in your project. Codex loads it when a task matches its description.

Can I use Supabase CI Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-ci-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/supabase-ci-integration, .gemini/skills/supabase-ci-integration, .github/skills/supabase-ci-integration and .opencode/skills/supabase-ci-integration in your project.

What does Supabase CI Integration need to run?

Going by SKILL.md and its folder, Supabase CI Integration needs the command-line tools its instructions call (npx, supabase, gh, npm and git) and credentials named SUPABASE_ACCESS_TOKEN and SUPABASE_DB_PASSWORD. Our summary lists: Node.js; Docker; A credential in SUPABASE_ACCESS_TOKEN. Its frontmatter pre-approves these tools: Write, Bash(npx:*), Bash(gh:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Supabase CI Integration access the network?

SKILL.md names 1 domain. As links in the text: supabase.com. This is read from the text; nothing was executed.

Is Supabase CI Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Supabase CI Integration use?

Supabase CI Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Supabase CI Integration use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.5k tokens, read only when the agent opens those files.

What are the alternatives to Supabase CI Integration?

Skills that share tags, products or a category with Supabase CI Integration: Data Scraper Agent (affaan-m/ECC, 277k stars), Data Scraper Agent (affaan-m/ECC, 276k stars), Data Scraper Agent (affaan-m/ECC, 276k stars) and Nushell (ccusage/ccusage, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Supabase CI Integration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Supabase CI Integration

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Supabase CI Integration

Overview

Prerequisites

Instructions

Step 1: Configure GitHub Secrets and Link in CI

Step 2: CI Workflow — Test, Validate Migrations, and Generate Types

Step 3: Deploy Migrations and Edge Functions on Merge

Preview Branches

Testing in CI

Output

Error Handling

Examples

Resources

Next Steps

Files

Compare with similar skills

Similar skills

More from jeremylongshore/tons-of-skills-marketplace

Related

Questions about Supabase CI Integration