Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cwinvestments/memstack-automation-api-integration
Use this skill when the user says 'API integration', 'connect APIs', 'sync data', 'data mapping', 'rate limiting', or needs system-to-system connectors with authentication, rate limit handling, and error recovery. Generates API integration code with authentication (OAuth, API key, JWT), request/response mapping, rate limit handling, error recovery with circuit breakers, and sync monitoring.
Passed 15 of 22 test cases with the skill, and 11 of 22 without it.
and 5 more in the full report
5 fixed10 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are looking to connect APIs between HubSpot CRM and our custom backend service to sync data for contacts and deals. Could you provide a technical integration blueprint for this connector? I need it structured into an Overview, Authentication strategy, Rate Limiting approach, Data Mapping schema with field transformations, Pagination loop, Sync State & Recovery tracking, and a Production Checklist to ensure we don't lose data during sync failures.
| Checked | Without skill | With skill |
|---|---|---|
| Uses async generator iterator pattern for fetching paginated records | Missed | Passed |
| Implements periodic checkpoint updates during record processing loop | Missed | Passed |
| Defines declarative mapping objects with source and target paths | Missed | Passed |
The instructions your model reads when the skill loads.
Develops system-to-system connectors with REST/GraphQL patterns, authentication flows, rate limit handling, data mapping, error recovery, and SDK wrapper generation.
When this skill activates, output:
API Integration: Building system connector...
Then execute the protocol below.
| Context | Status |
|---|---|
| User says "API integration", "connect APIs", "sync data" | ACTIVE |
| User says "data mapping" or "rate limiting" | ACTIVE |
| User needs to build a connector between two systems | ACTIVE |
| User wants a visual n8n workflow | DORMANT: use n8n Workflow Builder |
| User wants to receive webhooks | DORMANT: use Webhook Designer |
| Mistake | Why It's Wrong |
|---|---|
| "Ignore rate limits" | Getting blocked by the API wastes hours of debugging. Implement rate limiting from day one. |
| "No retry logic" | APIs have transient failures. Without retry + backoff, your sync silently drops data. |
| "Store tokens in code" | Use environment variables or a secrets manager. Tokens in code end up in git history. |
| "Map fields manually every time" | Build a reusable mapping layer. Manual field-by-field transforms are fragile and hard to update. |
| "No pagination handling" | Most APIs return paginated results. If you only read page 1, you're missing data. |
If the user hasn't provided details, ask:
- Source system: where does the data come from? (API name, docs URL)
- Destination: where does it go? (your DB, another API, file)
- Data: what entities are synced? (users, orders, products, events)
test cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.