[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVC50M4SWH89FZMCMM6E5X":3,"skill-same:01M7EVC50M4SWH89FZMCMM6E5X":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EVC50M4SWH89FZMCMM6E5X","platform-api-integration",null,"Integrate with SaaS platform APIs — authentication, rate limits, webhooks, SDK patterns, and robust client design.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-platform-api-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: platform-api-integration\ndescription: Integrate with SaaS platform APIs — authentication, rate limits, webhooks, SDK patterns, and robust client design.\ncategory: curviate\n---\n\n## Overview\n\nIntegrating with a SaaS platform's API means: authenticating securely, handling rate limits, processing webhooks, and building clients that survive real-world failures. This skill covers general API integration patterns for SaaS platforms — vendor-neutral principles applicable to any REST\u002FGraphQL API.\n\n\nIntegrating with SaaS platform APIs connects your product to the ecosystems where customers work: syncing data, embedding workflows, and extending capabilities.\nGood integrations feel native; bad ones feel bolted-on.\nThis skill covers API integration strategy, implementation patterns, and the operational discipline of maintaining integrations over time.\n## When to use\n\n- Integrating with a third-party SaaS API\n- Designing API clients\n- Handling OAuth flows\n- Debugging rate limit issues\n- Building webhook receivers\n- Planning API version upgrades\n\n- Building native integrations with popular SaaS tools\n- Syncing data bidirectionally between platforms\n- Embedding third-party functionality via APIs\n- Designing integration marketplaces or app directories\n## Core concepts\n\n**Authentication.** API keys (simple, server-to-server — store securely, rotate regularly), OAuth 2.0 (user-delegated access — authorization code flow for web, PKCE for mobile\u002FSPA), and token management (secure storage, refresh before expiry, handle revocation). Never expose secrets client-side.\n\n**Rate limits.** Understand: limits per window, per endpoint, per token. Handle 429s with exponential backoff + jitter, respect Retry-After headers, implement client-side throttling (token buckets), and batch requests where the API supports it. Design for limits from day one — retrofitting is painful.\n\n**Pagination.** Cursor-based (preferred for large\u002Fchanging datasets), offset-based (simple, breaks with concurrent writes), and page-size tuning. Always handle \"more pages\" loops defensively (max iterations, progress logging).\n\n**Error handling.** Retry transient errors (5xx, 429, timeouts) with backoff; don't retry client errors (4xx — fix the request); parse error bodies for actionable codes; implement circuit breakers for cascading failures; and log request IDs for support.\n\n**Webhooks.** Verify signatures, respond fast (2xx immediately, process async), dedupe on event IDs (at-least-once delivery), handle out-of-order events (idempotent processing), and build replay tooling. See webhook-patterns for depth.\n\n**Versioning and change management.** Pin API versions, monitor deprecation notices, test against beta\u002Fsandbox before upgrades, and abstract version differences behind your client layer. Subscribe to API changelogs — breaking changes announced there first.\n\n\n**Integration patterns.** Polling (simple, delayed, API-heavy) → webhooks (real-time, requires receiver infrastructure) → streaming (high-volume, ordered) → batch sync (large datasets, scheduled).\nChoose by freshness requirements and volume — webhooks for real-time needs, batch for analytics.\nMost integrations combine patterns: webhooks for events, batch for backfill.\n**Authentication.** OAuth 2.0 (user-delegated, standard for SaaS), API keys (server-to-server, simple), webhooks signatures (verify sender).\nImplement OAuth properly: secure token storage, refresh handling, scope minimization, and graceful re-auth flows.\nToken expiry mid-workflow is a top integration failure — handle refresh transparently.\n**Rate limits and quotas.** Every API throttles: understand limits (requests\u002Fminute, daily caps), implement backoff with jitter, queue and batch requests, cache aggressively.\nDesign for the limit from day one — retrofitting throttling under load causes outages.\n**Data mapping.** Field-level mapping between systems with transformation rules, conflict resolution (last-write-wins? source priority?), and handling of custom fields.\nDocument mappings explicitly; implicit mappings break silently when either API changes.\n## Practical workflow\n\n1. **Read the docs.** Authentication, rate limits, pagination, webhooks, error codes, versioning policy. Build a mental model before writing code.\n2. **Design the client.** Wrapper library with: auth handling, retry\u002Fbackoff, rate-limit awareness, pagination helpers, error translation (API errors → domain exceptions), and request logging. One client, used everywhere — no ad-hoc HTTP calls scattered around.\n3. **Implement auth.** Secure credential storage (vaults, not env files in repos), token refresh logic, and scope minimization (request only needed permissions).\n4. **Build defensively.** Timeouts on every call, retries with backoff, circuit breakers, idempotency keys for writes, and graceful degradation (what happens when the API is down?).\n5. **Handle data sync.** Decide: real-time (webhooks), polling (for APIs without webhooks — respect intervals), or hybrid. Reconcile periodically (webhooks get missed; nightly syncs catch drift).\n6. **Operate.** Monitor: error rates, latency, rate-limit hits, webhook delivery. Alert on anomalies. Review API changelogs monthly; test version upgrades in sandbox first.\n\n**Client checklist:** auth + refresh → retries with backoff → rate-limit handling → pagination helpers → timeout per call → error translation → request logging → idempotent writes → webhook verification.\n\n\n**Integration development:** study API docs and changelog → prototype auth flow → map data models → build happy path → handle errors and edge cases → implement webhooks → build sync engine (initial + incremental) → test with real accounts → beta with design partners → launch with monitoring.\nBudget 40% of time for edge cases and error handling — happy paths are the easy part.\n**Maintenance program:** monitor API changelogs → track deprecation timelines → maintain version compatibility → handle credential expiry proactively → audit sync health daily.\nAPIs change constantly; integrations are living systems, not shipped features.\n## Common pitfalls\n\n- **Secrets in code.** API keys committed to repos. Vaults + rotation, always.\n- **No retry logic.** Single attempt, fail loudly. Transient failures are normal — retry intelligently.\n- **Ignoring rate limits.** Hammering until banned. Backoff, throttle, batch.\n- **Sync without reconciliation.** Trusting webhooks alone. Periodic full syncs catch missed events.\n- **No timeouts.** Hanging requests consuming resources. Timeout everything.\n- **Version drift.** Running against deprecated versions until forced migration. Track versions proactively.\n- **Scattered integration code.** Ad-hoc API calls across the codebase. Centralize behind one client.\n- **Underestimating API quality variance.** Some APIs are excellent; others are buggy, slow, or poorly documented. Prototype early to discover reality before committing roadmaps.\n- **No sync observability.** Silent sync failures corrupting data for weeks. Monitor sync lag, error rates, and data consistency continuously.\n- **Ignoring API terms.** Rate limit violations, prohibited use cases, or data storage restrictions. Read the terms; violations get API access revoked.\n- **Building on undocumented endpoints.** They change without notice. Use public APIs only — or accept the maintenance burden explicitly.\n","## Overview\n\nIntegrating with a SaaS platform's API means: authenticating securely, handling rate limits, processing webhooks, and building clients that survive real-world failures. This skill covers general API integration patterns for SaaS platforms — vendor-neutral principles applicable to any REST\u002FGraphQL API.\n\n\nIntegrating with SaaS platform APIs connects your product to the ecosystems where customers work: syncing data, embedding workflows, and extending capabilities.\nGood integrations feel native; bad ones feel bolted-on.\nThis skill covers API integration strategy, implementation patterns, and the operational discipline of maintaining integrations over time.\n## When to use\n\n- Integrating with a third-party SaaS API\n- Designing API clients\n- Handling OAuth flows\n- Debugging rate limit issues\n- Building webhook receivers\n- Planning API version upgrades\n\n- Building native integrations with popular SaaS tools\n- Syncing data bidirectionally between platforms\n- Embedding third-party functionality via APIs\n- Designing integration marketplaces or app directories\n## Core concepts\n\n**Authentication.** API keys (simple, server-to-server — store securely, rotate regularly), OAuth 2.0 (user-delegated access — authorization code flow for web, PKCE for mobile\u002FSPA), and token management (secure storage, refresh before expiry, handle revocation). Never expose secrets client-side.\n\n**Rate limits.** Understand: limits per window, per endpoint, per token. Handle 429s with exponential backoff + jitter, respect Retry-After headers, implement client-side throttling (token buckets), and batch requests where the API supports it. Design for limits from day one — retrofitting is painful.\n\n**Pagination.** Cursor-based (preferred for large\u002Fchanging datasets), offset-based (simple, breaks with concurrent writes), and page-size tuning. Always handle \"more pages\" loops defensively (max iterations, progress logging).\n\n**Error handling.** Retry transient errors (5xx, 429, timeouts) with backoff; don't retry client errors (4xx — fix the request); parse error bodies for actionable codes; implement circuit breakers for cascading failures; and log request IDs for support.\n\n**Webhooks.** Verify signatures, respond fast (2xx immediately, process async), dedupe on event IDs (at-least-once delivery), handle out-of-order events (idempotent processing), and build replay tooling. See webhook-patterns for depth.\n\n**Versioning and change management.** Pin API versions, monitor deprecation notices, test against beta\u002Fsandbox before upgrades, and abstract version differences behind your client layer. Subscribe to API changelogs — breaking changes announced there first.\n\n\n**Integration patterns.** Polling (simple, delayed, API-heavy) → webhooks (real-time, requires receiver infrastructure) → streaming (high-volume, ordered) → batch sync (large datasets, scheduled).\nChoose by freshness requirements and volume — webhooks for real-time needs, batch for analytics.\nMost integrations combine patterns: webhooks for events, batch for backfill.\n**Authentication.** OAuth 2.0 (user-delegated, standard for SaaS), API keys (server-to-server, simple), webhooks signatures (verify sender).\nImplement OAuth properly: secure token storage, refresh handling, scope minimization, and graceful re-auth flows.\nToken expiry mid-workflow is a top integration failure — handle refresh transparently.\n**Rate limits and quotas.** Every API throttles: understand limits (requests\u002Fminute, daily caps), implement backoff with jitter, queue and batch requests, cache aggressively.\nDesign for the limit from day one — retrofitting throttling under load causes outages.\n**Data mapping.** Field-level mapping between systems with transformation rules, conflict resolution (last-write-wins? source priority?), and handling of custom fields.\nDocument mappings explicitly; implicit mappings break silently when either API changes.\n## Practical workflow\n\n1. **Read the docs.** Authentication, rate limits, pagination, webhooks, error codes, versioning policy. Build a mental model before writing code.\n2. **Design the client.** Wrapper library with: auth handling, retry\u002Fbackoff, rate-limit awareness, pagination helpers, error translation (API errors → domain exceptions), and request logging. One client, used everywhere — no ad-hoc HTTP calls scattered around.\n3. **Implement auth.** Secure credential storage (vaults, not env files in repos), token refresh logic, and scope minimization (request only needed permissions).\n4. **Build defensively.** Timeouts on every call, retries with backoff, circuit breakers, idempotency keys for writes, and graceful degradation (what happens when the API is down?).\n5. **Handle data sync.** Decide: real-time (webhooks), polling (for APIs without webhooks — respect intervals), or hybrid. Reconcile periodically (webhooks get missed; nightly syncs catch drift).\n6. **Operate.** Monitor: error rates, latency, rate-limit hits, webhook delivery. Alert on anomalies. Review API changelogs monthly; test version upgrades in sandbox first.\n\n**Client checklist:** auth + refresh → retries with backoff → rate-limit handling → pagination helpers → timeout per call → error translation → request logging → idempotent writes → webhook verification.\n\n\n**Integration development:** study API docs and changelog → prototype auth flow → map data models → build happy path → handle errors and edge cases → implement webhooks → build sync engine (initial + incremental) → test with real accounts → beta with design partners → launch with monitoring.\nBudget 40% of time for edge cases and error handling — happy paths are the easy part.\n**Maintenance program:** monitor API changelogs → track deprecation timelines → maintain version compatibility → handle credential expiry proactively → audit sync health daily.\nAPIs change constantly; integrations are living systems, not shipped features.\n## Common pitfalls\n\n- **Secrets in code.** API keys committed to repos. Vaults + rotation, always.\n- **No retry logic.** Single attempt, fail loudly. Transient failures are normal — retry intelligently.\n- **Ignoring rate limits.** Hammering until banned. Backoff, throttle, batch.\n- **Sync without reconciliation.** Trusting webhooks alone. Periodic full syncs catch missed events.\n- **No timeouts.** Hanging requests consuming resources. Timeout everything.\n- **Version drift.** Running against deprecated versions until forced migration. Track versions proactively.\n- **Scattered integration code.** Ad-hoc API calls across the codebase. Centralize behind one client.\n- **Underestimating API quality variance.** Some APIs are excellent; others are buggy, slow, or poorly documented. Prototype early to discover reality before committing roadmaps.\n- **No sync observability.** Silent sync failures corrupting data for weeks. Monitor sync lag, error rates, and data consistency continuously.\n- **Ignoring API terms.** Rate limit violations, prohibited use cases, or data storage restrictions. Read the terms; violations get API access revoked.\n- **Building on undocumented endpoints.** They change without notice. Use public APIs only — or accept the maintenance burden explicitly.\n",{"name":5,"category":24,"description":7},"curviate","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-platform-api-integration",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill platform-api-integration",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill platform-api-integration",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill platform-api-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-platform-api-integration\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]