sk-actions-custom-provider
Custom Provider
Use this skill for Scalekit custom providers, also called connectors.
This skill is only for proxy-only connectors.
Execution Policy
- The skill must ask whether the target Scalekit environment is
DevorProductionbefore doing anything else. - In
Dev, the skill may run the token curl to generateenv_access_token. - In
Dev, the skill may run the read-only list providers curl to check existing custom providers. - In
Dev, the skill may run the create curl only after explicit user approval. - In
Dev, the skill may run the update curl only after the required diff review and explicit user confirmation. - In
Production, the skill may run the token curl to generateenv_access_token. - In
Production, the skill may run read-only list providers curls. - In
Production, the skill must never run create, update, or delete curls. - In
Production, the skill may give the user resolved curls to run themselves after review. - The skill must never run the delete curl. It should only print the resolved delete command and ask the user to run it from their terminal.
- Whenever the skill executes a curl, label the result with
✅for success or❌for failure.
More from scalekit-inc/skills
setup-scalekit
Use when a developer is new to Scalekit and needs guidance on where to start, doesn't know which auth plugin or skill to choose, wants to connect an AI agent or agentic workflow to third-party services (Gmail, Slack, Notion, Google Calendar), needs OAuth or tool-calling auth for agents, wants to add authentication to a project but hasn't chosen an approach yet, or needs to install the Scalekit plugin for their AI coding tool (Claude Code, Codex, Copilot CLI, Cursor, or other agents).
11integrating-agent-auth
Integrates Scalekit Agent Auth into a project to handle OAuth flows, token storage, and automatic refresh for third-party services (Gmail, Slack, Notion, Calendar). Use when a user needs to connect to an external service, authorize OAuth access, fetch access or refresh tokens, or execute API calls on behalf of a user.
5implementing-scalekit-fsa
Implements Scalekit full-stack authentication (FSA) including sign-up, login, logout, and secure session management using JWT tokens. Use when building or integrating user authentication with the Scalekit SDK across Node.js, Python, Go, or Java — or when the user asks about auth flows, OAuth callbacks, token refresh, or session handling with Scalekit.
4adding-mcp-oauth
Guides users through adding OAuth 2.1 authorization to Model Context Protocol (MCP) servers using Scalekit. Use when setting up MCP servers, implementing authentication for AI hosts like Claude Desktop, Cursor, or VS Code, or when users mention MCP security, OAuth, or Scalekit integration.
3modular-sso
Implements complete SSO and authentication flows using Scalekit. Handles modular SSO, IdP-initiated login, user session management, and enterprise customer onboarding. Use when adding authentication, SSO, SAML, OIDC, or user login to applications.
3implementing-fsa-logout
Implements a complete logout flow for Scalekit FSA integrations by clearing application session cookies and redirecting the browser to Scalekit’s /oidc/logout endpoint to invalidate the Scalekit session. Use when adding or fixing logout in Node.js, Python, Go, or Java web apps that use Scalekit OIDC.
2