Skills for Connector Authors
The skills that walk Claude through building a connector on the SDK, from an empty package to a submission, with the manifest, the ports, the data rules, the fakes and the conformance kit at hand.
The connector skills carry the Connector SDK reference as procedure: what a connector is and what the core does for it, every block of connector.json, every port with when the core calls it and what it must return, the Core API contracts, the five data rules, the fakes and the conformance kit, and the road to review. Claude builds against the SDK's own words rather than a memory of them.
connector-data-rules
Used when the user is writing a migration or a model for a Subscriby connector, asks which tables a connector may create or alter, how its rows relate to the core's rows, what storage_ref is, or what disconnect, uninstall, reinstall and purge do to data.
Rests on /sdk/v1/building/data.
connector-manifest
Used when the user is writing or fixing a connector.json manifest for a Subscriby connector, asks about one of its blocks or the eighteen capabilities, the JSON Schema, a loader error naming a dotted path, or what the registry refuses at boot.
Rests on /sdk/v1/manifest.
connector-ports
Used when the user is implementing a port of a Subscriby connector (the lifecycle, identity, inbound, failure, renderer, settings, slots, messenger, access, relay or recovery ports), asks when the core calls a method or what it must return, or needs a Core API contract.
Rests on /sdk/v1/ports, /sdk/v1/core-api.
connector-publishing
Used when the user is preparing a Subscriby connector for release, asks how to version it or pin the SDK, write the listing and marketing words, pass review, submit a package, update it after first publish, or what the lanes, badges, pausing and retiring mean.
Rests on /sdk/v1/building/publishing, /sdk/v1/building/listing.
connector-sdk
Used when the user wants to build a Subscriby connector for a platform, asks what a connector is, how to start a package on subscriby/connector-sdk, which ports every connector binds, or how the package, the provider and the Connector class fit together.
Rests on /sdk/v1, /sdk/v1/building.
connector-testing
Used when the user is testing a Subscriby connector, asks about the SDK's fake connector or port fakes and their assertions, how to run the conformance kit with TestRegistry or inside Subscriby's suite, what the kit's rules check, or what only the platform can prove.
Rests on /sdk/v1/building/testing, /sdk/v1/conformance.
From an empty directory to a submission
Start the package
connector-sdk: the layout, composer.json, the service provider at src/, a Connector class that binds the seven required ports, and the fake connector to copy from.
Write the manifest
connector-manifest: identity, the install mode and fields, the resource kinds with their grant modes, the capabilities the platform can perform, the platform's message limits and pacing, the commands, relay modes and recovery flags, the listing. Validated against the published schema as it is written.
Implement the ports
connector-ports: the required seven, then the ports each capability binds, with the value objects, the failure kinds and the Core API contracts, and the rules every port shares (refs in, results out; refusals classified, never thrown; idempotent by design).
Keep the data inside the rules
connector-data-rules: tables prefixed with the key, never a core table altered, foreign keys pointing inward with storage_ref pointing back, additive migrations after first publish, explicit tenant filtering.
Test it
connector-testing: the port fakes with their triggers and assertions, what the package's own suite covers, the conformance kit run with the SDK's test registry and no Subscriby checkout, and what only a sandbox installation on the platform can prove.
Publish it
connector-publishing: version and pin the SDK, translate every string into the ten locales, write the listing, pass the review checklist, submit, and update additively after first publish.
The kit holds the shape, review holds the behaviour
A capability the platform cannot perform passes the conformance kit and fails review. The skills say so at every declaration, and the testing skill ends with the one thing no fake can prove: a real bot adding a real member to a real place.
Each skill, with the prompts that start it
The reference the skills rest on
Connectors for developers
What a connector is, what the core provides, and how a package on the SDK becomes a connector on the marketplace.
The manifest
Every block of connector.json, one page each, with the published JSON Schema.
Ports
One page per port: what the core asks of it, when it is called, and what the kit checks.
Core API
The contracts a connector calls into the core, one page each.
Conformance kit
The rules every connector passes, one by one, and what review adds.
Tutorial: a forum connector
From an empty directory to a package that passes the kit, chapter by chapter.
How is this guide?
Last updated on
Skills for Developers
The skills that let Claude integrate Subscriby into whatever you are building, from a verified webhook receiver and the right events to tokens, retries, the Zapier and n8n nodes, OpenAPI toolkits, your own agent and every MCP client.
Slash Commands
The commands the kit adds to Claude Code, what each reads or writes, and what its answer looks like, from the sign-in check to the webhook verifier.