insforge-skills_skill

Overview

This skill provides a command-line interface to create and manage InsForge Backend-as-a-Service projects. It handles authentication, project linking, database schema and backups, edge functions, storage, deployments, schedules, logs, and secrets management. Use it to automate common operational and deployment tasks from CI/CD or your terminal.

How this skill works

The CLI inspects your local directory for a linked project file (.insforge/project.json) or lets you create/link projects. It invokes InsForge APIs to run database queries, deploy and invoke edge functions, manage storage buckets and objects, create deployments, and manage secrets and schedules. Exit codes and environment variables enable scripting and non-interactive CI usage.

When to use it

• Set up or link an InsForge project from your terminal or CI pipeline
• Perform schema changes, export/import backups, or run raw SQL queries
• Deploy, update, or invoke edge functions and monitor execution logs
• Manage storage buckets, upload/download objects, and perform destructive deletes
• Create cron schedules that call functions or external endpoints
• Store, retrieve, and rotate secrets safely for deployments and schedules

Best practices

• Always run insforge whoami and insforge current at session start to confirm auth and project linkage
• Build frontend artifacts locally before insforge deployments deploy to avoid wasting server resources
• Store sensitive values as secrets and reference them as ${{secrets.KEY\_NAME}} in schedules and headers
• Use 5-field cron expressions only (minute hour day month day-of-week); 6-field with seconds is unsupported
• Do not commit .insforge/project.json to version control; use environment variables or CI secrets for non-interactive workflows

Example use cases

• CI: run non-interactive login, link project, export DB schema, and upload to artifact storage
• Dev: create a posts table with RLS policies and test auth.uid()-based policies via insforge db query
• Ops: deploy an edge function and invoke it with test payloads, then inspect function.logs
• Backup: insforge db export --output backup.sql and later restore with insforge db import backup.sql
• Scheduler: create a cron job that POSTs to an edge function using secrets for Authorization headers