agentleFS
Sign inStart free
SupabaseKnown publishersupabase/evals/skills/spark/SKILL.md

spark

Skill151 starsChanged 7 months agoApache-2.0View on GitHub

Spark REST API for database schema, data, and email/password authentication.

  • Reads credentials

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use Forge.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ikennaokpalaSkill

    Forge

    Autonomous quality engineering swarm that forges production-ready code through continuous behavioral verification, exhaustive E2E testing, and self-healing fix loops. Combines DDD+ADR+TDD methodology with BDD/Gherkin specifications, 7 quality gates, defect prediction, chaos testing, and cross-context dependency awareness. Architecture-agnostic - works with monoliths, microservices, modular monoliths, and any bounded-context topology.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use Content-Type: application/json for JSON bodies.

    line 8
  2. Distinctive:

    No row-level security: publishable keys can read and write every row.

    line 47
  3. Very specific:

    No OpenAPI root (GET /rest/v1/), RPC, or views.

    line 48
  4. Distinctive:

    No OTP, magic links, OAuth, password recovery, or MFA.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Base URL: $SPARK_PROJECT_URL. Send the API key in the apikey header, not a query parameter. $SPARK_SECRET_KEY acts as service_role; $SPARK_PUBLISHABLE_KEY acts as anon. For a user session, also send Authorization: Bearer <access_token>. Keep keys and tokens out of output.

Use Content-Type: application/json for JSON bodies. Error responses contain diagnostic details in the body.

Schema and SQL

MethodPathRequest / behavior
GET/system/v1/migrationsApplied migrations, oldest first, including their SQL statements. Secret key required.
POST/system/v1/migrations{"version":"...","name":"...","sql":"..."}. Applies SQL and reloads the Data API schema cache. Use an unused version. Secret key required.
POST/database/query{"query":"SELECT ...","parameters":[]}. Read-only SQL inspection. Secret key required.

Apply DDL through migrations and DML through the Data API. SQL compatibility is partial: information_schema.tables and information_schema.columns are unavailable. Inspect schema through migration statements or SELECT * FROM pragma_table_info('<table>').

Data API

Tables in public are available at /rest/v1/<table>.

MethodBehavior
GET, HEADRead rows or headers. Supports select, filters such as id=eq.1, order, limit, and offset.
POSTInsert one JSON object or an array of rows.
PATCHUpdate rows selected by query-string filters.
DELETEDelete rows selected by query-string filters.

Prefer: return=representation returns inserted or updated rows. Prefer: count=exact requests a count. Accept: application/vnd.pgrst.object+json requests one row as an object.

Auth

Email/password only. Signup confirms the email immediately without sending mail. Signup and token requests return access_token, refresh_token, and user.

MethodPathRequest / behavior
POST/auth/v1/signup{"email":"...","password":"..."}. Creates a user and session.
POST/auth/v1/token?grant_type=password{"email":"...","password":"..."}. Signs in.
POST/auth/v1/token?grant_type=refresh_token{"refresh_token":"..."}. Refreshes a session.
GET/auth/v1/userCurrent user; requires the session bearer token.
POST/auth/v1/logoutEnds the session; requires the session bearer token.

Limits

  • No row-level security: publishable keys can read and write every row. RLS statements and policies are unsupported.
  • No OpenAPI root (GET /rest/v1/), RPC, or views.
  • Upsert and PUT on an existing row with an integer primary key are known to fail.
  • No OTP, magic links, OAuth, password recovery, or MFA. A project secret key does not act as an Auth admin session.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free