insforge-integrations
This skill provides integration guides for connecting third-party authentication providers and payment facilitators to InsForge. It covers JWT-based row-level security for auth providers and x402 HTTP payment protocols for onchain billing.
Is insforge-integrations safe to install?
Safe to install: our audit of insforge-integrations's source files found 1 shell command, 0 external URLs, no file writes (none risk). Every command and URL listed appears verbatim in the skill's source. The skill provides documentation and configuration patterns. It does not execute code or perform network requests directly, though it references CLI commands for secret management.
How we audit skills: our security review methodology.
Who is this skill for?
Developers building applications on InsForge who need to integrate external authentication services or onchain payment systems.
What can you do with it?
- Configuring JWT-based row-level security with Clerk, Auth0, WorkOS, Kinde, Stytch, or Better Auth.
- Implementing onchain pay-per-use billing via the OKX x402 payment facilitator.
- Setting up database schemas and RLS policies for third-party auth providers.
- Managing payment settlement records and realtime triggers for onchain transactions.
How good is this skill?
Quality score: 5/10. The skill documentation is clear, well-structured, and provides specific actionable advice for common integration pitfalls.
What does the skill file contain?
# InsForge Integrations This skill covers integrating **third-party providers** with InsForge. Currently two categories are supported: **auth providers** (RLS via JWT claims) and **payment facilitators** (x402 HTTP payment protocol). Each provider has its own guide under this directory. ## Auth Providers | Provider | Guide | When to use | |----------|-------|-------------| | [Clerk](references/clerk.md) | Clerk JWT Templates + InsForge RLS | Clerk signs tokens directly via JWT Template — no server-side signing needed | | [Auth0](references/auth0.md) | Auth0 Actions + InsForge RLS | Auth0 us...
Frequently asked questions
Which auth providers does this skill support?
It supports Clerk, Auth0, WorkOS, Kinde, Stytch, and Better Auth.
How do I handle user IDs from third-party auth providers?
Use TEXT columns for user_id fields, as all supported providers use string-format IDs rather than UUIDs.
What payment facilitator is supported for onchain billing?
The skill supports the OKX x402 facilitator for USDG payments on the X Layer.
Should I use auth.uid() for RLS policies with these providers?
No, use the requesting_user_id() function instead to accommodate string-based IDs.
Related skills
supabase
153.8KDevelopers building applications with Supabase who require assistance with database schema design, security policy implementation, CLI operations, and integration troubleshooting
The Supabase skill provides guidance for developing with the Supabase platform, including database management, authentication, RLS policies, CLI usage, and MCP server integration. It emphasizes verifying implementation against current documentation, following security checklists, and using specific CLI commands for schema migrations.
firebase-auth-basics
98.6KDevelopers building applications with Firebase who need to implement user sign-in, management, or secure data access
This skill provides guidance for configuring and managing Firebase Authentication, including user identity providers, token handling, and deployment of authentication settings via the Firebase CLI.
firebase-basics
97.4KDevelopers using AI agents to manage Firebase projects via the command line
Provides foundational Firebase CLI workflows including authentication, project management, and configuration file retrieval.
convex-setup-auth
80.1KDevelopers building applications on the Convex platform who need to integrate authentication providers like Clerk, Auth0, WorkOS, or Convex Auth
This skill provides a structured workflow for implementing authentication, identity mapping, and access control within Convex applications. It guides the agent to identify the appropriate auth provider, consult official documentation, and apply secure patterns for protecting backend functions.