← ClaudeAtlas

rs2listed

This skill should be used when the user asks to inspect, call, or configure an RS2 server (Restspace 2, the Rust runtime); wants to manage tenant mounts or hot-reload tenant configuration; needs to author, store, or debug an RS2 pipeline spec (typed or string DSL), stored query, JSONata transform, or JSX template (the `template` service rendering data to HTML); asks about RS2 authentication, role specs, idempotency keys, retry policies, or effect classes; wants to read, query, or configure RS2 structured logs (the `log` service, OTel/OTLP records, boundary logging, the `logging` sink config); mentions the `rs2` CLI, `rs2 new`, `rs2 dev`, `rs2 deploy`, `rs2 migrate`, `serverConfig.json`, a `tenants/<name>.json`, or a `code:<name>@<version>` mount; wants to write or deploy a custom sandboxed service (JS bundle or Wasm component) with capability grants; needs the agent surface or OpenAPI under `/.well-known/rs2/`; or is migrating a v1 Restspace `services.json` to RS2.
restspace/rs2-skill · ★ 0 · Data & Documents · score 70
Install: claude install-skill restspace/rs2-skill
# RS2 (Restspace 2) An RS2 server is a Rust runtime hosting composable HTTP services, each mounted on a root path per tenant. Custom code runs sandboxed (V8 isolates for JS, Wasmtime components for Rust/Wasm) with default-deny capabilities and hard resource limits. Example tenant: ``` /files File store (streamed) /data Schema-validated JSON store /auth Authentication + RBAC /orders Pipeline (composition over other mounts) /q Stored queries /render JSX templates rendered to HTML /services Self-configuration API /pay code:stripe-wrapper@a1b2c3 (sandboxed custom service) ``` The `rs2` CLI covers the developer loop — scaffold, run a local node, validate, deploy bundles, migrate v1 configs — plus a few admin/ops commands that drive a running server: `login`, `send` (PUT a local file to a path), `service add` (add a mount via the self-config API), and `run` (a script of `rs2` lines). These read a saved server identity from `rsconfig.json`. For anything they don't cover, interact with a tenant over **plain HTTP** (curl, `Invoke-RestMethod`). See `references/cli.md`. ## Orient First 1. `GET /.well-known/rs2/services` — every mount the caller may read, with its `pattern` (`store` | `store-view` | `transform` | `api`) and `facets`. Patterns are the polymorphism contract: one client codepath drives every mount sharing a pattern — `file` and `data` are both `store` and obey one normative shape (`references/services.md`); feature-detect facets, neve