Skip to content

fcakyon/claude-codex-settings / plugins/supabase-skills/skills/supabase-cli

supabase-cli

Flagged

This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.

FileKindSize
SKILL.mdskill md6.3 KB
references/commands/functions.mdmarkdown543 B
references/commands/gen.mdmarkdown594 B
references/commands/init.mdmarkdown682 B
references/commands/link.mdmarkdown626 B
references/commands/login.mdmarkdown695 B
references/commands/network-bans.mdmarkdown230 B
references/commands/projects.mdmarkdown477 B
references/commands/pull.mdmarkdown7.0 KB
references/commands/secrets.mdmarkdown476 B
references/commands/start.mdmarkdown850 B
references/commands/status.mdmarkdown432 B
references/commands/stop.mdmarkdown475 B
references/commands/vanity-subdomains.mdmarkdown149 B
references/config/diff.mdmarkdown2.3 KB
references/config/pull.mdmarkdown8.0 KB
references/config/push.mdmarkdown1.5 KB
references/db/advisors.mdmarkdown174 B
references/db/diff.mdmarkdown2.8 KB
references/db/dump.mdmarkdown926 B
references/db/lint.mdmarkdown1.0 KB
references/db/pull.mdmarkdown5.4 KB
references/db/push.mdmarkdown843 B
references/db/query.mdmarkdown337 B
references/db/reset.mdmarkdown1.3 KB
references/db/schema-declarative-generate.mdmarkdown1.5 KB
references/db/schema-declarative-sync.mdmarkdown413 B
references/domains/activate.mdmarkdown523 B
references/examples.yamlconfig16.1 KB
references/functions/new.mdmarkdown510 B
references/functions/serve.mdmarkdown1.9 KB
references/inspect/db-bloat.mdmarkdown1.3 KB
references/inspect/db-blocking.mdmarkdown1.2 KB
references/inspect/db-cache-hit.mdmarkdown1.3 KB
references/inspect/db-calls.mdmarkdown1.3 KB
references/inspect/db-index-sizes.mdmarkdown660 B
references/inspect/db-index-usage.mdmarkdown968 B
references/inspect/db-locks.mdmarkdown1.1 KB
references/inspect/db-long-running-queries.mdmarkdown1.0 KB
references/inspect/db-outliers.mdmarkdown1.9 KB
references/inspect/db-replication-slots.mdmarkdown1.3 KB
references/inspect/db-role-connections.mdmarkdown1.6 KB
references/inspect/db-seq-scans.mdmarkdown720 B
references/inspect/db-table-index-sizes.mdmarkdown627 B
references/inspect/db-table-record-counts.mdmarkdown636 B
references/inspect/db-table-sizes.mdmarkdown756 B
references/inspect/db-total-index-size.mdmarkdown272 B
references/inspect/db-total-table-sizes.mdmarkdown608 B
references/inspect/db-traffic-profile.mdmarkdown1.8 KB
references/inspect/db-unused-indexes.mdmarkdown923 B
references/inspect/db-vacuum-stats.mdmarkdown2.4 KB
references/migration/list.mdmarkdown722 B
references/migration/new.mdmarkdown376 B
references/migration/repair.mdmarkdown2.6 KB
references/migration/squash.mdmarkdown892 B
references/overview.mdmarkdown5.4 KB
references/test/db.mdmarkdown440 B

references/inspect/db-cache-hit.md

View on GitHub
# db-cache-hit

This command provides information on the efficiency of the buffer cache and how often your queries have to go hit the disk rather than reading from memory. Information on both index reads (`index hit rate`) as well as table reads (`table hit rate`) are shown. In general, databases with low cache hit rates perform worse as it is slower to go to disk than retrieve data from memory. If your table hit rate is low, this can indicate that you do not have enough RAM and you may benefit from upgrading to a larger compute addon with more memory. If your index hit rate is low, this may indicate that there is scope to add more appropriate indexes.

The hit rates are calculated as a ratio of number of table or index blocks fetched from the postgres buffer cache against the sum of cached blocks and uncached blocks read from disk.

On smaller compute plans (free, small, medium), a ratio of below 99% can indicate a problem. On larger plans the hit rates may be lower but performance will remain constant as the data may use the OS cache rather than Postgres buffer cache.

```
         NAME      │  RATIO
  ─────────────────┼───────────
    index hit rate │ 0.996621
    table hit rate │ 0.999341
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall