api-integration
/api-integration
Pomaga konsumować zewnętrzne API i integrować usługi zewnętrzne: typowane klienty API, przepływy uwierzytelniania i specyfikacje OpenAPI, GraphQL i REST, głównie w TypeScript.
- Autor
- srstomp ↗
- Repozytorium
- pokayokay ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 28.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 14
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 28.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pomaga konsumować zewnętrzne API i integrować usługi zewnętrzne: typowane klienty API, przepływy uwierzytelniania i specyfikacje OpenAPI, GraphQL i REST, głównie w TypeScript.
Oryginalny opis (EN)
Use when consuming external APIs, integrating third-party services, generating type-safe API clients, implementing authentication flows, or working with OpenAPI/Swagger, GraphQL, or REST specs. TypeScript-primary with language-agnostic patterns.
Jak działa
- Key Principles
- When NOT to Use
- Quick Start Checklist
- References
Podgląd SKILL.md
--- name: api-integration description: Use when consuming external APIs, integrating third-party services, generating type-safe API clients, implementing authentication flows, or working with OpenAPI/Swagger, GraphQL, or REST specs. TypeScript-primary with language-agnostic patterns. --- # API Integration Build robust, type-safe API clients from specs and documentation. ## Key Principles - **Type everything** — Runtime-validated types for all requests and responses - **Fail explicitly** — No silent failures; throw typed errors with context - **Auth is first-class** — Handle auth in the client layer, not scattered in calls - **Retry intelligently** — Only idempotent methods, only transient failures, with backoff - **Isolate the boundary** — Transform API shapes at the integration layer, not in app code ## When NOT to Use - **Designing your own APIs** — Use `api-design` for building endpoints others will consume - **Writing API test suites** — Use `testing-strategy` for test architecture, contract tests, mocking - **Building SDKs for your API** — Use `sdk-development` for packaging your own API as a client library ## Quick Start Checklist 1. Obtain API credentials and locate documentation (spec, docs, or examples) 2. Analyze inputs: extract base URL, auth scheme, endpoints, error formats 3. Choose architecture: typed wrapper (1-5 endpoints), service class (5-20), or generated client (20+) 4. Implement types, client, auth handling, and error classification 5. Add retry logic for transient failures and rate limit handling 6. Write tests with mocked responses and error scenarios ## References | Reference | Description | |-----------|-------------| | [openapi-specs-types.md](references/openapi-specs-types.md) | Parsing OpenAPI specs, type generation strategies | | [openapi-patterns-codegen.md](references/openapi-patterns-codegen.md) | Common patterns, client generation, GraphQL, informal docs | | [client-base-service-layer.md](references/client-base-service-layer.md) | Base client, interceptors, service layer pattern | | [client-request-response-caching.md](references/client-request-response-caching.md) | Request config, response parsing, caching, logging | | [error-classification.md](references/error-classification.md) | Error type hierarchy, classification, response conversion | | [error-retry-circuit-breaker.md](references/error-retry-circuit-breaker.md) | Retry with backoff, rate limits, circuit breaker | | [error-fallback-patterns.md](references/error-fallback-patterns.md) | Fallback strategies, Result type, error boundaries, reporting | | [auth-api-keys-bearer.md](references/auth-api-keys-bearer.md) | API key and bearer token authentication | | [auth-oauth2.md](references/auth-oauth2.md) | OAuth 2.0 authorization code, PKCE, client credentials | | [auth-jwt-hmac-storage.md](references/auth-jwt-hmac-storage.md) | JWT handling, HMAC signatures, secure token storage | | [testing-mocking-fixtures.md](references/testing-mocking-fixtures.md) | HTTP mocking (MSW, Nock), test fixtures | | [testing-unit-integration.md](references/testing-unit-integration.md) | Unit tests for transformers, integration tests for services | | [testing-contract-e2e-config.md](references/testing-contract-e2e-config.md) | Contract testing, E2E tests, Jest configuration |
Pliki w paczce (14)
- SKILL.md 3 KB
- references/auth-api-keys-bearer.md 5 KB
- references/auth-jwt-hmac-storage.md 8 KB
- references/auth-oauth2.md 6 KB
- references/client-base-service-layer.md 9 KB
- references/client-request-response-caching.md 8 KB
- references/error-classification.md 5 KB
- references/error-fallback-patterns.md 6 KB
- references/error-retry-circuit-breaker.md 6 KB
- references/openapi-patterns-codegen.md 8 KB
- references/openapi-specs-types.md 4 KB
- references/testing-contract-e2e-config.md 3 KB
- references/testing-mocking-fixtures.md 8 KB
- references/testing-unit-integration.md 8 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · srstomp/pokayokay | 100 | MIT |
| facebook/agentic-tools | 100 | MIT |
| mhmdelgazzar/agentex | 100 | MIT |
| AutumnsGrove/Lattice | 100 | AGPL-3.0 |
| ajyadav013/claude-kit | 100 | MIT |
| ajyadav013/claude-kit | 100 | MIT |
| seb1n/awesome-ai-agent-skills | 100 | MIT |
| shurikentrade/shuriken-skills | 100 | MIT |
| LambdaTest/agent-skills | 95 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 2c7fab0b6bd5 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90api-contract-design
Podpowiada wzorce projektowania API REST i GraphQL, specyfikacje OpenAPI/Swagger, strategie wersjonowania i uwierzytelniania. - 100openapi-codegen
Generuje typowane klienty API z OpenAPI przy użyciu openapi-typescript, openapi-generator-cli, swagger-typescript-api i trpc-openapi. - 100api-integrate
Generuje typowane klienty API i DTO z OpenAPI lub Swagger przy integracji API. - 100api-documenter
Dokumentuje API REST i GraphQL, specjalizując się w specyfikacjach OpenAPI i Swagger. - 95api-documentation-generator
Generuje specyfikacje OpenAPI i Swagger oraz dokumentację API z kodu albo projektu. - 100api-design
Podaje dobre praktyki projektowania API REST i GraphQL, w tym specyfikacje OpenAPI i dokumentowanie endpointów.