PlugWiki

insforge skill (InsForge): write app code with the InsForge SDK

InsForge's own skill that has a coding agent add database, auth, storage, AI, realtime and payment features to an app with the @insforge/sdk.

Installs
62.6K
on skills.sh
Stars
47
on GitHub
Files
19
besides SKILL.md
Updated
Oct 2026
last repo commit

insforge makes your coding agent write app code against InsForge's backend with the @insforge/sdk. It covers database reads and writes, sign-in, file storage, edge functions, OpenRouter AI calls, realtime, email, and Stripe or Razorpay checkout.

It loads when you ask for things like add auth, fetch data, upload files or add checkout. It installs the SDK, writes your project's .env with the InsForge URL and anon key, and runs the InsForge CLI with npx. Infrastructure work such as SQL migrations goes to the insforge-cli skill.

Good for

  • Developers building an app on InsForge's Postgres-based backend
  • Teams adding sign-in, file uploads or Stripe and Razorpay checkout to an InsForge app
  • People moving existing S3 tooling to InsForge Storage

Install insforge

Claude Code

  1. 1

    Copy this prompt.

    Install the insforge skill in Claude Code. Run this command:
    
    /plugin marketplace add InsForge/insforge-skills
    /plugin install insforge@insforge
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Pick one route, not both. The skills CLI asks which skills to take: pick insforge and insforge-cli, because insforge links to files in insforge-cli's references folder. The plugin route installs all 4. The skills run the InsForge CLI with npx, which needs Node.js 18 or newer, and you need an InsForge account and project. The README lists /install-skills under Claude Code. It is not a documented Claude Code built-in and we have not confirmed it works, so prefer the plugin or the skills CLI.

Built from the package data we hold. Not yet tested by us. Source.

What's in the skill

When it loads

Use this skill when writing app code with InsForge or @insforge/sdk: database CRUD, auth, storage uploads/storage RLS, functions, OpenRouter AI, realtime, emails, Stripe or Razorpay payments, or pointing S3-compatible tooling (aws CLI, AWS SDKs, rclone, Terraform, boto3) at InsForge Storage. Trigger on requests like add auth, fetch data, upload files, make a bucket public, add checkout, sell subscriptions, or send email. For infrastructure, SQL migrations, CLI commands, or payment provider setup, use insforge-cli instead.

Sections in SKILL.md

  1. Quick Setup
  2. 1. Install the SDK
  3. 2. Set up environment variables
  4. 3. Initialize the client
  5. Module Reference
  6. What Each Module Covers
  7. Guides
  8. Building Payments for a New App
  9. Real-time Backend Setup
  10. Backend Configuration
  11. Risky backend changes? Use a branch first
  12. SDK Quick Reference
  13. Important Notes

Key facts

Installs on skills.sh
62,560 as of 2026-11-02
Last change to this skill
2026-08-29

What it includes

  • Installs the SDK, gets the URL and anon key, writes .env

    Runs npm install @insforge/sdk@latest, then npx -y @insforge/cli link or create, then secrets get ANON_KEY, and writes the values into .env or .env.local with the framework's prefix.

    Try: “Add InsForge auth and a todos table to this Next.js app.”

    Runs code · Quick setup

  • Create, read, update and delete rows, plus RPC calls

    SDK methods .from().select(), .insert(), .update(), .delete() and .rpc(). Inserts must be arrays. SKILL.md warns against unbounded select() polling.

    Delete · Database

  • Sign up, sign in, OAuth, sessions, password reset, SSR

    Covers signUp, signInWithPassword, signInWithOtp, signInWithOAuth, signOut and getCurrentUser, plus a guide for Next.js and other SSR setups.

    Write · Auth

  • Upload, download and delete files; S3 gateway; storage RLS

    Includes a fallback guide for pointing the aws CLI, AWS SDKs, rclone, Terraform or boto3 at InsForge Storage, which SKILL.md says needs InsForge 2.0.9 or newer.

    Delete · Storage

  • Invoke edge functions

    insforge.functions.invoke(slug). Deploying a function belongs to insforge-cli.

    Runs code · Functions

  • OpenRouter chat, images, video, audio, embeddings and RAG

    Seven guides. New AI features use OpenRouter with a key set up by npx -y @insforge/cli ai setup; the SDK's insforge.ai module is marked as a deprecated fallback.

    Network · AI

  • WebSocket events, presence, and transactional email

    Realtime connect, subscribe, publish and presence. insforge.emails.send() sends custom HTML email; SKILL.md says that ships on every paid plan.

    Write · Realtime and email

  • Stripe Checkout and Billing Portal; Razorpay orders and subscriptions

    Checks provider setup with payments stripe status or payments razorpay status first. Provider keys and catalog sync are done in insforge-cli.

    Write · Payments

  • Test risky schema or RLS changes on a branch

    For migrations, new RLS policies or OAuth changes it runs branch create, then branch merge --dry-run, then branch merge, and tells you to update env values and restart the dev server.

    Runs code · Backend branch first

  • Report InsForge-side bugs with the CLI

    npx -y @insforge/cli feedback files a bug, feature request or friction report. SKILL.md says PII is redacted locally and that it should never be used for bugs in your own app code.

    Runs code · Feedback

From the official docs

Permissions

Medium risk

The agent installs packages, writes your .env, and runs the InsForge CLI against a real project, so changes reach a live backend. Work on a backend branch for risky changes, and keep admin keys out of frontend code.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • The project API key is a full-access admin key

    SKILL.md says it is equivalent to a service role key. Use the anon key in browser code and keep the admin key in server-only env vars. github.com

  • Changes reach a live backend

    Config apply, branch merge and payments setup act on your real project. Use a branch first for schema, RLS or auth changes, as SKILL.md advises. github.com

  • Bug reports go to InsForge

    The feedback command sends a report to the InsForge team with local redaction that SKILL.md calls pattern-based. Keep user data out of the report text. github.com

  • The InsForge CLI sends usage events to PostHog

    The CLI source says each command emits one PostHog event with non-sensitive properties, and uses an anonymous ID when no project is linked. The skill runs the CLI through npx, so those events come with it. github.com

  • The plugin route installs all 4 skills

    The Claude and Codex plugin manifests cover the whole skills folder, which holds 4 skills, and the git tree has no hooks or MCP config. The Codex marketplace file sets authentication to ON_INSTALL. github.com

  • agents/openai.yaml holds interface settings

    Each skill folder includes an agents/openai.yaml with a display name, short description, brand color and a default prompt. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Talks toYour InsForge project URL and api.insforge.dev. npm registry (SDK and CLI downloads). OpenRouter, through the InsForge Model Gateway, when AI features run
Sign-in and keysThe CLI writes .insforge/project.json with the project ID, app key, region, API key and backend URL (per the insforge-cli SKILL.md). SKILL.md says the API key is a full-access admin key.
Data retentionNot stated in SKILL.md.
Scopes
  • Runs npm install @insforge/sdk@latest

  • Runs npx -y @insforge/cli (link, create, secrets get, config apply, branch, payments status, feedback)

  • Writes the InsForge URL and anon key to .env or .env.local

  • Reads .insforge/project.json, which holds the project ID and API key

Questions

What does the insforge skill do?

It guides your coding agent when it writes app code for InsForge: database, auth, storage, functions, AI, realtime, email and payments through @insforge/sdk. Backend setup such as migrations is left to the insforge-cli skill.

How do I install the insforge skill?

Use the install box at the top of this page. Install insforge together with insforge-cli, because SKILL.md links to guides in insforge-cli's references folder for backend setup. The plugin route installs all 4 InsForge skills; with the skills CLI, pick both.

Does it need an InsForge account or API key?

Yes, it needs an InsForge project. The skill gets the project URL and anon key through the InsForge CLI, which needs you to log in with a browser or a user API key.

insforge or insforge-cli?

insforge is for app code that calls InsForge with @insforge/sdk. insforge-cli is for the backend itself: projects, SQL migrations, functions, secrets, deployments and billing.

Is the insforge skill safe?

It can change a live backend and write keys to your .env, so use a branch for risky changes and read each command before you approve it. It uses your own InsForge account, so you decide which project it links to.

Is this the official InsForge skill?

Yes. It is in InsForge's own insforge-skills repo, and the plugin manifests name InsForge as author.

Does it work in the Claude app, Codex or Cursor?

The README documents a Codex plugin and a skills registry install; the Claude Code plugin comes from the repo's marketplace file. The skill runs npx commands and edits project files, so there is no Claude app upload option here. The README does not name Cursor.

Information

updated Nov 2, 2026

Folder
skills/insforge

insforge/insforge-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6
  1. marketplace.json · github.com
  2. README.md · github.com
  3. README.md · github.com
  4. plugin.json · github.com
  5. SKILL.md · github.com
  6. command-telemetry.ts · github.com

Updated Nov 2, 2026.