Add a WorldMonitor JSON API endpoint as a sebuf RPC — proto definition, make generate, handler, gateway, client wrapper, and contract checks. Use when adding or changing an RPC method or service, or when tempted to add a standalone api/*.js or api/*.ts data endpoint.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Full walkthrough with examples: docs/adding-endpoints.mdx. Framework notes: CONTRIBUTING.md#working-with-sebuf-rpc-framework.
api/*.js or api/*.ts data endpoints. npm run lint:api-contract rejects any api/ file that is neither a sebuf gateway nor listed in api/api-route-exceptions.json; that manifest is only for OAuth callbacks, binary responses, upstream proxies, and operator plumbing, and is CODEOWNERS-pinned.src/generated/ or docs/api/. Edit the proto and regenerate.int64 Unix epoch milliseconds with [(sebuf.http.int64_encoding) = INT64_ENCODING_NUMBER], not google.protobuf.Timestamp.option (sebuf.http.config) = { path: "...", method: HTTP_METHOD_POST } (or HTTP_METHOD_GET, matching the neighbouring RPCs).proto/worldmonitor/{domain}/v1/.make generate (needs Go, buf, and sebuf plugins pinned by SEBUF_VERSION in the Makefile; make install-buf install-plugins). If the toolchain is unavailable, say so; CI's proto job appends a chore(proto): update generated artifacts commit for same-repo branches.server/worldmonitor/{domain}/v1/. Read seeded data from Redis with getCachedJson(key, true) (server/_shared/redis.ts); use cachedFetchJson() for on-demand upstream fetches, with every request-varying parameter in the cache key.api/{domain}/v1/[rpc].ts and the dev-server handler import in vite.config.ts.src/services/{domain}/.PREMIUM_RPC_PATHS (src/shared/premium-paths.ts), unauthenticated ones in PUBLIC_NO_AUTH_RPC_PATHS (server/gateway.ts), anonymous CDN-shared ones in PUBLIC_SHARED_RPC_PATHS (src/shared/public-rpc-cache.ts).make lint and make breaking for proto changes.npm run lint:api-contract, npm run typecheck:api, a focused handler test, then npm run test:related.koala73/worldmonitor
329b04c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.