Help us improve
Share bugs, ideas, or general feedback.
From cc-polymath
Discovers and loads 8 specialized skills for REST/GraphQL API design, authentication (OAuth/JWT/API keys), authorization, rate limiting, versioning, error handling in backend tasks.
npx claudepluginhub rand/cc-polymath --plugin cc-polymathHow this skill is triggered — by the user, by Claude, or both
Slash command
/cc-polymath:discover-apiThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Provides automatic access to comprehensive API design, authentication, and implementation skills.
Provides structured guidance on REST and GraphQL API design, including resource modeling, versioning strategies, and pagination patterns. Use when designing or reviewing API specifications.
Provides API design principles, comparisons, and best practices for REST, GraphQL, gRPC including resource naming, schema design, documentation with OpenAPI, versioning, and error handling.
Guides REST and GraphQL API design principles including resource-oriented architecture, HTTP methods, schema-first development, versioning strategies, pagination, and filtering patterns. Use for new API design, spec reviews, refactoring, and team standards.
Share bugs, ideas, or general feedback.
Provides automatic access to comprehensive API design, authentication, and implementation skills.
This skill auto-activates when you're working with:
The API category contains 8 specialized skills:
For complete descriptions and workflows:
Read ../api/INDEX.md
This loads the full API category index with:
Load individual skills as needed:
Read ../api/rest-api-design.md Read ../api/graphql-schema-design.md
Read ../api/api-authentication.md Read ../api/api-authorization.md
Read ../api/api-rate-limiting.md Read ../api/api-error-handling.md Read ../api/api-versioning.md
Read ../api/api-design-rules.md
Sequence: REST design → Authentication → Authorization
Read ../api/rest-api-design.md # Resource modeling, HTTP methods Read ../api/api-authentication.md # User authentication Read ../api/api-authorization.md # Access control
Sequence: GraphQL schema → Authentication → Authorization
Read ../api/graphql-schema-design.md # Schema design, resolvers Read ../api/api-authentication.md # User authentication Read ../api/api-authorization.md # Field-level permissions
Sequence: Rate limiting → Error handling → Versioning
Read ../api/api-rate-limiting.md # Prevent abuse Read ../api/api-error-handling.md # Standardized errors Read ../api/api-versioning.md # Manage evolution
Full implementation from scratch:
Read ../api/rest-api-design.md
Read ../api/api-authentication.md Read ../api/api-authorization.md Read ../api/api-rate-limiting.md
Read ../api/api-error-handling.md Read ../api/api-versioning.md
Choose REST API skills when:
Choose GraphQL skills when:
Authentication vs Authorization:
Production considerations:
API skills commonly combine with:
Database skills (discover-database):
Testing skills (discover-testing):
Frontend skills (discover-frontend):
Infrastructure skills (discover-infra, discover-cloud):
Read ../api/INDEX.md for full category overviewThis gateway skill (~200 lines, ~2K tokens) enables progressive loading:
Total context: 2K + 3K + skill(s) = 5-10K tokens vs 25K+ for entire index.
"Design a REST API for a blog": Read ../api/rest-api-design.md
"Add OAuth authentication to my API": Read ../api/api-authentication.md
"Implement role-based access control": Read ../api/api-authorization.md
"Prevent API abuse": Read ../api/api-rate-limiting.md
"Design an API versioning strategy": Read ../api/api-versioning.md
Next Steps: Run Read ../api/INDEX.md to see full category details, or load specific skills using the bash commands above.