Integrate seatlayer
Skill seatlayer/seatlayer-ai-toolkit/skills/integrate-seatlayer
Add, review, diagnose, or verify SeatLayer integrations inside existing applications. Use for managed hosted booking, direct links, embeds, Organizer Websites, Buyer SDK installation, SeatPicker or SeatingChart, mobile SDKs, server SDKs, custom checkout, holds, private or partner sales, buyer access sessions, channels, workspaces, Embedded Designer or control room, webhooks, analytics, checkout recovery, go-live review, and SeatLayer-related code generation or troubleshooting.From its SKILL.md
npx -y skills add seatlayer/seatlayer-ai-toolkit --skill integrate-seatlayerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
7.3 KB, as published. Nobody here has run it
Integrate SeatLayer
Use the live SeatLayer Markdown documentation as the product source of truth. Adapt SeatLayer to the repository; do not generate a parallel demo application unless the user explicitly asks for one.
Start with repository discovery
-
Read repository agent instructions and contribution guidance.
-
Inspect the package manager, framework, routing, server/client boundary, authentication, tenant model, order/payment flow, environment validation, HTTP conventions, tests, analytics adapter, and deployment platform.
-
Determine whether SeatLayer managed ticketing or the host platform owns payment, commercial orders, tickets, refunds, and fulfilment.
-
Run the read-only doctor when Node.js is available:
node <skill-root>/scripts/doctor.mjs <repository-root> -
State the chosen commerce profile, SeatLayer surface, and discovered host locations before editing.
-
Ask only for business decisions that cannot be discovered safely.
Read references/integration-map.md to select the surface and documentation routes. Read references/safety-contract.md before changing checkout, credential, booking, inventory, or webhook code.
Load focused live documentation
Always begin with:
https://docs.seatlayer.io/llms.txt- the task-specific Markdown routes selected from
integration-map.md
Prefer /<page>/index.md routes. Use
https://docs.seatlayer.io/llms-full.txt only when the task genuinely spans
several product surfaces. Do not invent SDK methods, fields, endpoints, error
codes, or release status from memory.
If live documentation conflicts with this skill, follow the live documentation and report the discrepancy.
Choose the smallest complete integration
Choose the commerce profile first:
- Managed ticketing when SeatLayer owns hosted checkout, Orders, tickets, delivery, refunds, and Door. Use a Hosted Event Page, managed embed, or Organizer Website. Do not add a host booking endpoint.
- Platform/custom commerce when the host owns payment, orders, tickets,
refunds, and fulfilment. Use
SeatPickerfor checkout handoff orSeatingChartfor headless selection, then book from a trusted server. - Private or partner distribution when access is limited by allocation. Choose a hosted access link or an origin-bound buyer access session based on the live channel contract; private means no public link, not disabled inventory.
Then add only the required surface:
- Official mobile SDK for React Native, Flutter, iOS, or Android buyer apps.
- Official server SDK for the host backend language; prefer it over handwritten HTTP when it supports the required operation.
- Embedded Designer for organizer chart editing.
SeatManagerfor an embedded operator board.- Workspaces and server APIs for multi-tenant platforms.
- Designer MCP only for authorized chart authoring or review.
Do not choose a larger surface because it is easier to demonstrate.
Preserve the trust boundary
Implement the invariants for the selected profile:
- A chart is reusable geometry; each event has independent live inventory.
- Managed hosted checkout completes booking itself; never book the same buyer journey again from host code.
- In platform/custom commerce, the browser selects and holds while a trusted server inspects and books.
SEATLAYER_SECRET_KEYand every server SDK are server-only.- Browser prices are never trusted payment input in custom commerce.
- Use a stable host order id as
bookingRefand reuse it for retries. - Treat expired holds and HTTP
409inventory conflicts as normal recovery paths. - Define the payment-success/booking-failure recovery policy explicitly.
- Keep buyer access tokens in memory and bind them to the exact event and origin; never log, persist, or place them in URLs.
- Require a short audit reason for privileged channel overrides.
- Verify webhook signatures from the raw body and deduplicate occurrences.
Do not log or return secret keys, raw credentials, full authorization headers, or webhook secrets.
Implement in repository order
For managed hosted checkout:
- Confirm managed-event readiness, gateway mode, and the chosen distribution surface.
- Add the link, managed embed, or Website placement within the existing UI.
- Verify hosted payment, branded return, Orders, ticket delivery, loading, mobile, and accessibility behavior in test mode.
For platform/custom commerce:
- Add environment validation and the official server SDK server-side.
- Add hold inspection, trusted pricing, order coordination, and idempotent booking.
- Add the buyer SDK surface within the existing UI and design system.
- Add expired-hold, conflict, loading, empty, mobile, and keyboard behavior.
For private or partner access, additionally add entitlement, channel scope, short-lived token refresh or hosted-link lifecycle, exact-origin enforcement, revocation, and attribution. Add webhooks, analytics, or operator surfaces only when required by scope. Document production variable names without values.
Keep browser-to-server payloads small and typed. The opaque holdId and stable
host order identity should cross the boundary; trusted pricing and booking
authority should not.
Verify before handoff
Read references/verification.md, then run the repository's typecheck, unit tests, lint, production build, and relevant integration tests.
Prove only the behavior belonging to the selected profile. For managed hosted checkout, verify the hosted purchase and return journey without adding a host booking assertion. For custom commerce, verify select → hold → inspect → pay/order → book, expiry, conflicts, idempotent retry, and compensation. For private access, also verify wrong-origin, expired, revoked, and exhausted access without silently widening to public inventory.
Always prove no secret or server SDK enters a buyer bundle, buyer access tokens are not persisted or logged, and mobile and keyboard behavior remains operable.
Run the doctor again after implementation. Distinguish automated checks from manual verification and report skipped checks.
Use Designer MCP carefully
When the task involves chart authoring or review, read
references/designer-mcp.md. Begin with
get_capabilities, follow the staged semantic workflow, and never publish
without explicit user authorization.
Do not use Designer MCP for ordinary SDK or server integration work.
Hand off clearly
Return:
- changed files and why;
- selected SeatLayer surface;
- commands and results;
- assumptions and unresolved production configuration;
- environment-variable names without values;
- manual end-to-end steps; and
- follow-up work for webhooks, observability, deployment, or operations.
What ships with it: 6 files
22.5 KB alongside SKILL.md, 1 of them executable
agents/
- openai.yaml230 B
references/
- designer-mcp.md1.4 KB
- integration-map.md4.3 KB
- safety-contract.md2.3 KB
- verification.md2.2 KB
scripts/
- doctor.mjsruns12.1 KB
Gives 0 of the 12 instructions most debug triage skills give
Counted across 1,020 of the 1,639 authors here whose files we hold, read 2026-09-06
- Find root cause before attempting any fixin 134 of 1020, across 118 files
- Create a failing test case before implementing a fixin 109 of 1020, across 95 files
- Read error messages and stack traces completelyin 102 of 1020, across 88 files
- Reproduce the issue consistently before investigatingin 90 of 1020, across 77 files
- Make the smallest possible change to test a hypothesisin 90 of 1020, across 76 files
- Trace data flow backward to find the sourcein 84 of 1020, across 70 files
- Form a single hypothesis before testingin 78 of 1020, across 64 files
- Implement only one fix at a timein 76 of 1020, across 63 files
- Question the architecture if three fixes failin 73 of 1020, across 59 files
- Add diagnostic instrumentation at component boundariesin 68 of 1020, across 56 files
- Compare broken code against working examplesin 68 of 1020, across 57 files
- Write a regression test before applying the fixin 62 of 1020, across 55 files
Said here and by no other author read
- Use live documentation as the source of truth
- Adapt SeatLayer to the existing repository
- Read repository instructions and contribution guidance first
- State commerce profile and surface before editing
- Choose the smallest complete integration surface
- Implement invariants for the selected commerce profile
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.