node-auth
Authentication seam for Plaited nodes. Use when wiring the current server auth boundary, choosing among WebAuthn, platform JWT, enterprise OIDC, or dev-mode auth, or supplying auth facts to module research lanes.
What this skill does
# Node Auth
## Purpose
This skill is a slim implementation-context reference for the current server
auth seam.
Use it to decide which auth mode applies and how to wire the existing auth
boundary in code. Treat bundle-level auth policy as research work for
the issue-backed kernel backlog listed in `dev-research/README.md`.
**Use when:**
- wiring `createServer` with `validateSession`
- choosing among sovereign/local, platform, enterprise, or dev auth modes
- generating or reviewing auth routes for a concrete deployment context
- supplying stable auth facts to A2A or three-axis module research
**Not for:** deciding the full default auth-aware module bundle. That belongs
in the issue-backed kernel backlog listed in `dev-research/README.md`.
## The Seam
The framework's only auth surface is one optional parameter on `createServer`:
```typescript
createServer({
trigger,
routes: { ...authRoutes, ...appRoutes },
validateSession: (sessionId: string) => boolean, // ← the seam
})
```
`validateSession` is the stable seam. WebSocket upgrades are rejected with
`session_invalid` (401) if it returns `false` for the `sid` cookie value. For
dev mode, pass `() => true`.
## Decision: Deployment Context
Before generating auth code, determine the deployment context:
| Who connects to this node? | Strategy | Reference |
|---------------------------|----------|-----------|
| **User directly** (sovereign node, local dev server) | WebAuthn passkeys | [webauthn-sovereign.md](references/webauthn-sovereign.md) |
| **Control plane** (hosted platform, cloud sandbox) | JWT verification | [platform-jwt.md](references/platform-jwt.md) |
| **SSO gateway** (enterprise private network) | OIDC token verification | [oidc-enterprise.md](references/oidc-enterprise.md) |
| **Developer on localhost** (development/testing) | Auto-session or no auth | [dev-mode.md](references/dev-mode.md) |
If the context is unclear, ask the user.
## Common Contract
All auth strategies return the same shape:
```typescript
type AuthStrategy = {
routes: ServeRoutes
isValidSession: (sessionId: string) => boolean
destroy: () => void
}
```
Wire into `createServer`:
```typescript
const auth = await createAuth(options) // strategy-specific module
const server = createServer({
trigger,
routes: { ...auth.routes, ...appRoutes },
validateSession: auth.isValidSession,
})
```
`destroy()` cleans up timers and in-memory stores. Call it on server shutdown.
## Reference Implementations
Full working implementations are in `assets/`:
- **[assets/webauthn-auth.ts](assets/webauthn-auth.ts)** — Complete WebAuthn passkey auth (registration + login flows)
- **[assets/webauthn-schemas.ts](assets/webauthn-schemas.ts)** — Zod schemas for credential storage
- **[assets/webauthn-auth-spec.reference.ts](assets/webauthn-auth-spec.reference.ts)** — Integration tests with mock verification
These are reference code the agent should **adapt** to the project, not import directly. The agent copies and modifies what's needed.
## Related Skills
- **modnet-modules** — node/A2A/module composition context for current
module-era architecture
- **behavioral-core** — BP engine the server bridges to
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.