agentleFS
Sign inStart free
pilotmainpilotmain/AethOS/skills/provision-supabase/SKILL.md

provision-supabase

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Provision or connect a Supabase project/database and wire it to a service.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read existing Supabase projects to avoid duplicates.

    line 16
  2. Distinctive:

    Create a governed provision/connect preflight: project/region for new projects, or the connection string wiring for existing ones (values …

    line 17
  3. Distinctive:

    Verify connectivity (read-only) and report.

    line 21
  4. Distinctive:

    create supabase provision/connect preflight (governed)

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

When to use

The operator asks to create a Supabase project, add a database, or connect Supabase to a service ("provision a Supabase db for aethos-api").

Steps

  1. Confirm the Supabase credential is present in the vault (management token / access token). If missing, ask the operator to add it in Connections — never request it in chat.
  2. Read existing Supabase projects to avoid duplicates.
  3. Create a governed provision/connect preflight: project/region for new projects, or the connection string wiring for existing ones (values masked).
  4. Operator approves; on execution, store the connection secret in the vault and wire it to the target service as an env var via the set-env governed flow.
  5. Verify connectivity (read-only) and report.

Mutation tools

  • create supabase provision/connect preflight (governed)
  • set-env preflight (to wire the connection string)

Governance

Mutation. Vault-only credentials, masked values, preflight → approve → execute → verify.

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