agentsclimarketplace
Sign in

Discover api

Skill kenantang/codex-and-claude-skills/collected-academic-research-skills/sources/rand__cc-polymath/skills/discover-api

Automatically discover API design skills when working with REST APIs, GraphQL schemas, API authentication, OAuth, JWT, rate limiting, API versioning, error handling, or endpoint design. Activates for backend API development tasks.From its SKILL.md

Install
npx -y skills add kenantang/codex-and-claude-skills --skill discover-api

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.0 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

API Skills Discovery

Provides automatic access to comprehensive API design, authentication, and implementation skills.

When This Skill Activates

This skill auto-activates when you're working with:

  • REST API design and implementation
  • GraphQL schema design
  • API authentication (JWT, OAuth 2.0, API keys, sessions)
  • API authorization (RBAC, ABAC, permissions)
  • Rate limiting and throttling
  • API versioning strategies
  • Error handling and validation
  • HTTP methods, status codes, endpoints

Available Skills

Quick Reference

The API category contains 8 specialized skills:

  1. rest-api-design - RESTful resource modeling, HTTP semantics, URL conventions
  2. graphql-schema-design - GraphQL types, resolvers, N+1 problem prevention
  3. api-authentication - JWT, OAuth 2.0, API keys, session management
  4. api-authorization - RBAC, ABAC, policy engines, permission systems
  5. api-rate-limiting - Token bucket, sliding window, rate limiting algorithms
  6. api-versioning - API versioning, deprecation, backward compatibility
  7. api-error-handling - RFC 7807 errors, validation, standardized responses
  8. api-design-rules - 35 opinionated rules for API design

Load Full Category Details

For complete descriptions and workflows:

Read ../api/INDEX.md

This loads the full API category index with:

  • Detailed skill descriptions
  • Usage triggers for each skill
  • Common workflow combinations
  • Cross-references to related skills

Load Specific Skills

Load individual skills as needed:

Core API design

Read ../api/rest-api-design.md Read ../api/graphql-schema-design.md

Security and access control

Read ../api/api-authentication.md Read ../api/api-authorization.md

Production hardening

Read ../api/api-rate-limiting.md Read ../api/api-error-handling.md Read ../api/api-versioning.md

Rules and best practices

Read ../api/api-design-rules.md

Common Workflows

New REST API

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

New GraphQL API

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

API Hardening

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

Complete API Stack

Full implementation from scratch:

1. Design phase

Read ../api/rest-api-design.md

2. Security phase

Read ../api/api-authentication.md Read ../api/api-authorization.md Read ../api/api-rate-limiting.md

3. Production readiness

Read ../api/api-error-handling.md Read ../api/api-versioning.md

Skill Selection Guide

Choose REST API skills when:

  • Building traditional web services
  • Need simple CRUD operations
  • Working with mobile apps or SPAs
  • Require caching and HTTP semantics

Choose GraphQL skills when:

  • Clients need flexible data fetching
  • Reducing over-fetching or under-fetching
  • Building aggregation layers
  • Need strong typing for APIs

Authentication vs Authorization:

  • Authentication (api-authentication.md): Who are you? (Login, JWT, OAuth)
  • Authorization (api-authorization.md): What can you do? (Permissions, RBAC)

Production considerations:

  • Always implement rate limiting for public APIs
  • Use versioning from day one
  • Standardize error responses early

Integration with Other Skills

API skills commonly combine with:

Database skills (discover-database):

  • API endpoints → Database queries
  • Connection pooling for API servers
  • Query optimization for API performance

Testing skills (discover-testing):

  • Integration tests for API endpoints
  • Contract testing for API consumers
  • Load testing for API performance

Frontend skills (discover-frontend):

  • API client libraries
  • Data fetching patterns
  • Error handling in UI

Infrastructure skills (discover-infra, discover-cloud):

  • API deployment strategies
  • Load balancing and scaling
  • API gateways and proxies

Usage Instructions

  1. Auto-activation: This skill loads automatically when Claude Code detects API-related work
  2. Browse skills: Run Read ../api/INDEX.md for full category overview
  3. Load specific skills: Use bash commands above to load individual skills
  4. Follow workflows: Use recommended sequences for common API patterns
  5. Combine skills: Load multiple skills for comprehensive coverage

Progressive Loading

This gateway skill (~200 lines, ~2K tokens) enables progressive loading:

  • Level 1: Gateway loads automatically (you're here now)
  • Level 2: Load category INDEX.md (~3K tokens) for full overview
  • Level 3: Load specific skills (~2-3K tokens each) as needed

Total context: 2K + 3K + skill(s) = 5-10K tokens vs 25K+ for entire index.

Quick Start Examples

"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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most apis services skills give in ~1.3k tokens

Counted across 448 of the 471 authors here whose files we hold, read 2026-09-06

  • Use HTTP status codes semanticallyin 25 of 448, across 11 files
  • Return 201 with a Location header on createin 24 of 448, across 9 files
  • Name resources plural, lowercase, kebab-casein 23 of 448, across 9 files
  • Configure rate limiting with limit headersin 22 of 448, across 8 files
  • Paginate list endpoints with cursor or offsetin 21 of 448, across 10 files
  • Version APIs in the URL pathin 21 of 448, across 11 files
  • Validate request input with a schemain 21 of 448, across 7 files
  • Add pagination to all list endpointsin 18 of 448, across 15 files
  • Match HTTP method to the operationin 12 of 448, across 6 files
  • Return 400 or 422 with field-level detailsin 12 of 448, across 2 files
  • Check ownership before returning resourcesin 12 of 448, across 2 files
  • Limit query depth and complexityin 12 of 448, across 7 files

Said here and by no other author read

  • Read the API category index for full details
  • Load individual skills as needed
  • Follow recommended sequences for common API workflows
  • Load multiple skills for comprehensive coverage
  • Use API versioning from the start

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.