Syntage Skills

Agent Skills for building reliable integrations with Syntage.

These skills guide an AI coding agent through Syntage integration work. The canonical product and API contract remains docs.syntage.com; the skills tell the agent which documentation to consult and which safety checks to apply.

Install

Agent Skills clients

Install the repository with a compatible Agent Skills client:

npx skills add syntagecom/skills

Select the skills relevant to your integration when prompted.

Claude Code

Add the Syntage marketplace and install its skill bundle from Claude Code:

/plugin marketplace add syntagecom/skills
/plugin install syntage-skills@syntage

Client metadata

SKILL.md contains the portable instructions and discovery metadata shared by Agent Skills clients. Optional client adapters enhance supported products without changing those instructions:

• agents/openai.yaml supplies OpenAI clients such as Codex with display names, short descriptions, and suggested prompts.
• .claude-plugin/marketplace.json makes all four skills installable as a Claude Code plugin bundle.

Clients that do not recognize an adapter continue to use SKILL.md.

Available skills

Skill	Use it for
syntage-api	API environment selection, authentication, entities, collections, pagination, filters, rate limits, and integration architecture
syntage-entity-onboarding	Embedded entity onboarding, onboarding events, CSP, and sandbox testing
syntage-extractions	Starting, tracking, scheduling, and troubleshooting asynchronous extractions
syntage-webhooks	Webhook endpoint design, signature verification, idempotent event processing, and reconciliation

Invoke a skill explicitly when asking your agent for help:

Use $syntage-api to add a sandbox Syntage client to this application.

Safety defaults

All skills follow the same baseline:

• Start development and testing in Syntage's sandbox, where returned data is simulated.
• Do not send production requests, mutate production integration configuration, or open a live onboarding flow without the user's explicit confirmation.
• Keep environment-specific API keys, signing secrets, datasource credentials, and authorizations outside source code, prompts, logs, and generated examples.
• Verify endpoints, fields, filters, extractor options, and event types against the current documentation instead of guessing.
• Prefer stable entity IDs and use Entity in product-facing language. In API contracts, the same concept may appear as Link or link; preserve documented names exactly.

Start with the developer overview, environment guide, and API reference.