Loading...
Loading...
Found 6 Skills
Use for custom storefronts requiring direct GraphQL queries/mutations for data fetching and cart operations. Choose this when you need full control over data fetching and rendering your own UI. NOT for Web Components - if the prompt mentions HTML tags like <shopify-store>, <shopify-cart>, use storefront-web-components instead.
Query resource usage metrics for Railway services. Use when user asks about resource usage, CPU, memory, network, disk, or service performance like "how much memory is my service using" or "is my service slow".
This skill should be used when the user asks about resource usage, CPU, memory, network, disk, or service performance. Covers questions like "how much memory is my service using" or "is my service slow".
API integration patterns including REST, GraphQL, WebSocket, and tRPC. Use when designing APIs, implementing data fetching, or building real-time features.
Use The Graph Subgraph MCP through UXC via native SSE with a fixed linked command for subgraph discovery, schema retrieval, deployment selection, and GraphQL query execution with help-first inspection and explicit auth handling.
Use when the user wants to query the Codex Supergraph but $CODEX_API_KEY is not set. Pays per query via the MPP 402 challenge flow. Only supports queries, not mutations or subscriptions.