base44-platform-integrations-sdk — Claude Code skill: install
base44-platform-integrations-sdk is a Claude Code skill for calling Base44 integrations through the SDK. It covers app features that need AI, email, file handling or analytics.
MIT 3,000 installs ★ 94 updated 2026-10-22
npx skills add base44/skills --skill base44-platform-integrations-sdk -a claude-codeWhat base44-platform-integrations-sdk does
The skill explains how to call Base44's built-in integrations: InvokeLLM, SendEmail, file uploads, signed URLs, data extraction, image generation and analytics events. It also includes input schemas for Core endpoints.
First identify the app profile, then use the matching reference. The profile can be fetched with GET /api/apps/{app_id}/agent-profile through Base44 MCP's execute_api tool or with a Base44 CLI token. Project files can help identify the app type if the profile is unavailable. File uploads and signed URLs use the client SDK; other Core integrations run in server code and require core-integration control for the app.
What it helps with
- call InvokeLLM from an app feature
- send email through SendEmail
- upload public or private files and create signed URLs
- extract data or generate images
- track analytics events in an app
Example prompts for the agent
- Connect InvokeLLM to the function that answers user questions.
- Add email delivery with SendEmail and show the input schema.
- Set up private file uploads and signed URL creation.
How to install base44-platform-integrations-sdk
1Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-integrations-sdk -a claude-code2Manually: put the files in place
~/.claude/skills/base44-platform-integrations-sdk/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/base44-platform-integrations-sdk/
1Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-integrations-sdk -a codex2Manually: put the files in place
.agents/skills/base44-platform-integrations-sdk/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-integrations-sdk -a cursor2Manually: put the files in place
.cursor/skills/base44-platform-integrations-sdk/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install base44/skills skills/base44-platform-integrations-sdk2Manually: put the files in place
.github/skills/base44-platform-integrations-sdk/SKILL.md1Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-integrations-sdk -a gemini-cli2Platform CLI
gemini skills install https://github.com/base44/skills --path skills/base44-platform-integrations-sdkManually: put the files in place
.devin/skills/base44-platform-integrations-sdk/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-integrations-sdk -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about base44-platform-integrations-sdk
How do I install base44-platform-integrations-sdk in Claude Code?
Run npx skills add base44/skills --skill base44-platform-integrations-sdk -a claude-code. The skill file is at ~/.claude/skills/base44-platform-integrations-sdk/SKILL.md.
What does base44-platform-integrations-sdk do?
It documents SDK calls for Base44's built-in AI, email, file, data extraction, image generation and analytics integrations. It also provides input schemas for Core endpoints.
What does base44-platform-integrations-sdk need to work?
Core integrations other than file uploads and signed URLs require core-integration control for the app. To fetch the app profile, use Base44 MCP with execute_api or a Base44 CLI token.
Source text
SKILL.md · MIT
---
name: base44-platform-integrations-sdk
description: "Base44 built-in integrations on the SDK client: InvokeLLM, SendEmail, file uploads (public and private), signed URLs, data extraction and image generation, with every Core endpoint's input schema, plus analytics event tracking. Use when a feature needs AI, email, files or analytics without a third-party service."
---
<!-- GENERATED FILE. DO NOT EDIT. Compiled from the Base44 builder's prompt sources; the
source commit is in /SOURCE_COMMIT at the repository root. Edits here are overwritten by
the next sync; change the source instead. -->
# Base44 integrations sdk
File uploads and signed URLs are called from the client SDK; every other Core integration runs in server code on an app with core-integration control, the default for new apps (profile `core_integrations: backend_functions_only`). The endpoint schemas below are the ones the platform serves today.
## Pick the reference for this app
Determine the app profile first. Call `GET /api/apps/{app_id}/agent-profile` (over the Base44 MCP `execute_api`
tool, or with your Base44 CLI token); it returns the framework, app type, runtime,
entitlements and the exact reference files to read. Without it, detect from the project files:
`src/routes/__root.*` and `src/routeTree.gen.ts` mean TanStack Start; `app/_layout.*` means a
native mobile (Expo) app; otherwise it is a Vite SPA.
| Profile | Read |
|---|---|
| Web app, Vite SPA (the default web template) | [Integrations and analytics SDK (Vite SPA)](references/web-spa.md) |
| Web app, TanStack Start | [Integrations and analytics SDK (TanStack Start)](references/web-tanstack.md) |
| Native mobile app (Expo, React Native) | [Integrations SDK (mobile apps)](references/mobile.md) |
© base44 · MIT · base44/skills