protocol-selector
Installation
SKILL.md
Protocol Selector Protocol
This skill prevents the "Golden Hammer" anti-pattern (where every problem is solved with GraphQL just because it's trendy, or REST just because it's familiar). It selects the correct transport layer based on the actual consumer needs.
Core assumption: There is no single "best" protocol. Picking gRPC for a public frontend is a disaster; picking REST for high-frequency microservice-to-microservice communication is inefficient.
1. Requirement Analysis (Static)
Analyze the system context based on user inputs:
- Clients: Web Browser? Mobile App? Internal Microservices? IoT Devices?
- Data Shape: Highly relational/graph-like? Binary files? Simple CRUD?
- Delivery Expectation: Request/Response? Server-to-Client Push? Bi-directional streams?