IMPORTANT: This skill routes to the right skill — it does NOT implement the integration itself. Once you identify the right skill below, tell the user to invoke it and stop. Do not generate implementation code here.
Step 1: Determine what to build
If answers aren't already clear from context, ask one question at a time:
-
What are you building?
- New agent that needs to call third-party tools on behalf of users (Gmail, Slack, Salesforce, etc.)
- Existing agent — adding connector access or fixing auth
- MCP server that exposes AgentKit tools
-
What's your current state?
- Starting from scratch
- Have a Scalekit account and environment already
- Have AgentKit set up, stuck on a specific step
Step 2: Tell the user exactly which skill to invoke
Pick the best match and tell the user: "Run /agentkit:<skill> to get started."
| What you're building | Tell them to run |
|---|---|
| New agent calling third-party tools (Gmail, Slack, Salesforce…) on behalf of users | /agentkit:integrating-agentkit |
| Discover tools available for a connector, inspect schemas | /agentkit:discovering-connector-tools |
| Expose AgentKit tools over MCP for Claude Desktop, Cursor, VS Code | /agentkit:exposing-agentkit-via-mcp |
| Pre-launch checklist, going to production | /agentkit:production-readiness-agentkit |
| SDK errors, wrong imports, broken auth calls | /saaskit:scalekit-code-doctor |
After telling the user which skill to run, stop. The target skill handles implementation.
Step 3: Environment setup (if new project)
Before starting any skill, verify credentials exist:
SCALEKIT_ENVIRONMENT_URL=https://your-env.scalekit.com
SCALEKIT_CLIENT_ID=<from dashboard>
SCALEKIT_CLIENT_SECRET=<from dashboard>
Get these from app.scalekit.com → Developers → Settings → API Credentials.
The Scalekit MCP server (https://mcp.scalekit.com) is pre-configured in .mcp.json. Claude Code handles OAuth 2.1 auth automatically — no additional setup needed.
Core AgentKit concepts (30-second orientation)
| Concept | What it is |
|---|---|
| Connector | A third-party app (Gmail, Slack, Salesforce, GitHub, etc.) |
| Connection | Your app's agreement with a connector (configured in dashboard) |
| Connected account | A specific user's authorization to use a connection |
| Tool | An action the agent can take (send email, create issue, etc.) |
Flow: User authorizes → connected account created → agent discovers tools → agent executes tool calls using that account.
Dashboard setup note: Gmail works without extra configuration. All other connectors (Slack, Salesforce, GitHub, Google Calendar, etc.) must be enabled and configured in the Scalekit Dashboard before users can connect them.
When to switch skills
- Already know what you need? Skip this skill and invoke the target directly.
- SDK errors? Use
/saaskit:scalekit-code-doctor. - Want to add B2B auth (login, SSO, SCIM) to your app? Switch to the
saaskitplugin:/saaskit:setup.