Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Api Designer K1lgorUse this when designing APIs (REST or GraphQL), defining routes, request/response schemas, or writing OpenAPI/Swagger specs.Votes: 0GitHub stars: 42
- Api DesignDesign RESTful APIs following conventions with proper errorVotes: 0GitHub stars: 27
- Api Designer Always FurtherActivates when user needs help designing REST APIs, GraphQL schemas, or API architecture. Triggers on "design API", "REST endpoint", "GraphQL schema", "API structure", "endpoint naming", "API versioning", "request/response format", or API design questions.Votes: 0GitHub stars: 42
- Api DesignUse when rEST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Triggers on \"api-design\", \"api design\", \"design\".Votes: 0GitHub stars: 2
- Api DesignExpert at designing clean, consistent, and developer-friendly APIs. Covers RESTful conventions, versioning strategies, error handling, pagination, rate limiting, and OpenAPI documentation. Designs APIs that are intuitive to use and easy to evolve. Use when "API design, REST API, RESTful, API versioning, API documentation, OpenAPI, Swagger, API error handling, pagination, rate limiting, api, rest, http, versioning, pagination, openapi, swagger" mentioned.Votes: 0GitHub stars: 137
- Api Design 14Use this skill when designing or implementing REST APIs, endpoints, routes, or controllers.Votes: 0GitHub stars: 2
- Api Design Restful Autohandai Community Skills 3RESTful API design patterns, error handling, and documentationVotes: 0GitHub stars: 364
- Api DesignUse when designing APIs or interfaces — REST/GraphQL contracts, request/response shapes, versioning, error models, and interface ergonomics. Triggers on "design API", "REST contract", "GraphQL schema", "接口设计", "API 契约", "API 设计".Votes: 0GitHub stars: 3
- Api Design ReviewAPI Design ReviewerVotes: 0GitHub stars: 19
- Api Designer Daffy0208 Ai Dev StandardsDesign REST and GraphQL APIs. Use when creating backend APIs, defining API contracts, or integrating third-party services. Covers endpoint design, authentication, versioning, documentation, and best practices.Votes: 0GitHub stars: 364
- Api Integration SpecialistExpert in integrating third-party APIs with proper authentication, error handling, rate limiting, and retry logic. Use when integrating REST APIs, GraphQL endpoints, webhooks, or external services. Specializes in OAuth flows, API key management, request/response transformation, and building robust API clients.Votes: 0GitHub stars: 416
- Api Design NeversightREST and GraphQL API design best practices including OpenAPI specs. Use when designing APIs, documenting endpoints, or reviewing API architecture.Votes: 0GitHub stars: 42
- Api Design Reviewer**Tier:** POWERFUL **Category:** Engineering / Architecture **Maintainer:** Claude Skills TeamVotes: 0GitHub stars: 6
- Api Design ReviewerAPI Design ReviewerVotes: 0GitHub stars: 33
- Common Api DesignApply REST API conventions — HTTP semantics, status codes, versioning, pagination, and OpenAPI standards for any framework. Use when designing endpoints, choosing HTTP methods, implementing pagination, or writing OpenAPI specs.Votes: 0GitHub stars: 549
- Common Api DesignApply REST API conventions — HTTP semantics, status codes, versioning, pagination, and OpenAPI standards for any framework. Use when designing endpoints, choosing HTTP methods, implementing pagination, or writing OpenAPI specs.Votes: 0GitHub stars: 571
- Api Design ReviewerAPI Design ReviewerVotes: 0GitHub stars: 2
- Common Api DesignStart with a resource-oriented contract and make the HTTP behavior predictable: 1. **Model resources in URLs.** Use lowercase, kebab-case, plural nouns such as `/v1/user-profiles` and `/v1/orders`. Avoid verbs in the base path. Keep nesting shallow; `/v1/users/{userId}/orders` is reasonable, while deeply nested item paths are difficult to document and maintain. 2. **Match methods to their semantics.** Use `GET` for read-only, idempotent reads; `POST` to create a resource or trigger an explici...Votes: 0GitHub stars: 549
- Api DesignerAPI design specialist for REST, GraphQL, gRPC, versioning strategies, and developer experienceUse when "api design, rest, graphql, grpc, openapi, swagger, versioning, pagination, rate limiting, endpoint, api, rest, graphql, grpc, openapi, swagger, versioning, pagination, rate-limiting, ml-memory" mentioned.Votes: 0GitHub stars: 137
- Api Design ReviewerAPI Design ReviewerVotes: 0GitHub stars: 6