Loading...
Loading...
Found 3,969 Skills
Pliance integration. Manage data, records, and automate workflows. Use when the user wants to interact with Pliance data.
Order Desk integration. Manage Orders. Use when the user wants to interact with Order Desk data.
ZeroBounce integration. Manage data, records, and automate workflows. Use when the user wants to interact with ZeroBounce data.
Zoho People integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zoho People data.
Teamwork Desk integration. Manage Organizations. Use when the user wants to interact with Teamwork Desk data.
Apply when reviewing or designing security-sensitive boundaries in VTEX IO apps. Covers public versus private exposure, trust assumptions at route and integration boundaries, sensitive data handling, validating what crosses the app boundary, and avoiding leakage across accounts, workspaces, users, or integrations. Use for route hardening, data exposure review, or evaluating whether a service boundary is too permissive.
Recruiterflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with Recruiterflow data.
Datumbox integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Datumbox data.
ETermin integration. Manage Persons, Organizations, Leads, Deals, Activities, Notes and more. Use when the user wants to interact with ETermin data.
Apply when building catalog or SKU synchronization logic for VTEX marketplace seller connectors. Covers the changenotification endpoint, SKU suggestion lifecycle, product data mapping, price and inventory sync, and fulfillment simulation. Use for implementing seller-side catalog integration that pushes SKUs to VTEX marketplaces with proper notification handling and rate-limited batch synchronization.
Apply when implementing retry logic, rate limit handling, or resilience patterns in VTEX API integrations. Covers VTEX rate limit headers (X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After), 429 status handling, exponential backoff with jitter, circuit breaker patterns, and request queuing. Use for any VTEX marketplace integration that must gracefully handle API throttling and maintain high availability.
Apply when designing or implementing HTTP endpoints exposed by a VTEX IO backend service. Covers route boundaries, handler structure, middleware composition, request validation, and response modeling for service.json routes. Use for webhook endpoints, partner integrations, callback APIs, or reviewing VTEX IO handlers that should expose explicit HTTP contracts.