setting-up-a-custom-rest-source — Claude Code skill: setup guide
setting-up-a-custom-rest-source — a skill for Claude Code and Codex that links arbitrary REST APIs to the PostHog data warehouse using a JSON manifest. Activates when importing custom endpoints without native connectors.
no license 199 installs ★ 101 updated 2026-11-16
npx skills add PostHog/ai-plugin --skill setting-up-a-custom-rest-source -a claude-codeWhat setting-up-a-custom-rest-source does
This skill authors a RESTAPIConfig manifest for PostHog custom data warehouse sources without requiring bespoke backend scripts. It first runs external-data-sources-wizard to confirm that PostHog lacks an out-of-the-box connector for the targeted API. When no native connector exists, the skill builds the configuration covering auth modes, pagination strategies, JSONPath record extraction, and incremental update cursors.
The workflow validates credentials and resource schemas with external-data-sources-db-schema, then samples live rows via external-data-sources-preview-resource to confirm field mappings. Authentication secrets are never placed inside manifest_json: keys such as auth_token or auth_api_key are submitted in isolated payload fields and redacted by the platform.
Custom sources operate under beta limits: each manifest can specify at most 50 resources, with a ceiling of 5 custom sources per project. Drafting manifests automatically with external-data-sources-draft-custom-manifest requires the PostHog AI builder enabled for the organization.
What it helps with
- Ingest unsupported REST APIs into PostHog tables without Python glue code
- Generate valid RESTAPIConfig JSON structures from API documentation
- Test pagination and cursor paths against live records prior to source creation
- Configure incremental extraction cursors for custom API tables
Example prompts for the agent
- Import our internal billing API into PostHog data warehouse using its docs
- Draft a custom REST source manifest for this third-party endpoint
- Validate this RESTAPIConfig manifest and sample live rows before creating the source
How to install setting-up-a-custom-rest-source
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill setting-up-a-custom-rest-source -a claude-code2Manually: put the files in place
~/.claude/skills/setting-up-a-custom-rest-source/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/setting-up-a-custom-rest-source/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill setting-up-a-custom-rest-source -a codex2Manually: put the files in place
.agents/skills/setting-up-a-custom-rest-source/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill setting-up-a-custom-rest-source -a cursor2Manually: put the files in place
.cursor/skills/setting-up-a-custom-rest-source/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/ai-plugin skills/setting-up-a-custom-rest-source2Manually: put the files in place
.github/skills/setting-up-a-custom-rest-source/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill setting-up-a-custom-rest-source -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/ai-plugin --path skills/setting-up-a-custom-rest-sourceManually: put the files in place
.devin/skills/setting-up-a-custom-rest-source/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill setting-up-a-custom-rest-source -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 setting-up-a-custom-rest-source
How to install setting-up-a-custom-rest-source in Claude Code?
Run npx skills add PostHog/ai-plugin --skill setting-up-a-custom-rest-source -a claude-code.
What does setting-up-a-custom-rest-source do?
It drafts, validates, and samples a JSON manifest to sync arbitrary REST APIs into PostHog warehouse tables.
What are the constraints on custom REST sources?
The feature is in beta and caps usage at 50 resources per manifest and 5 custom sources per project.