Skip to content
Back to skills

Server Socket

ASecurity

Bind OwlMeans socket protocol declarations to Fastify WebSocket handlers.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
tools

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add owlmeans/common --skill server-socket --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Server Socket?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Server Socket
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/owlmeans-server-socket-common/badge)](https://www.skillsdirectory.com/skills/owlmeans-server-socket-common)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: server-socket
description: Bind OwlMeans socket protocol declarations to Fastify WebSocket handlers.
---
<!-- AUTO-GENERATED — do not edit. Regenerate via sync-agent-meta. -->

# Socket protocol handlers

**Install:** `bun add @owlmeans/server-socket@^0.1.18-rc.55`

Declare a socket route and its contract in the shared protocol package. Bind it on the server with
`connection()` and `bind()`.

```ts
import { bind } from '@owlmeans/server-entrypoint'
import { connection } from '@owlmeans/server-socket'

export const serverBindings = [
  bind(streamProtocols.watch, connection(streamProtocols.watch,
    async (connection, context, request) => {
      await connection.send({ type: 'ready' })
    }
  )),
]
```

The handler receives a typed connection, context, request and response boundary. Guards and gates
are inherited from the protocol tree and enforced before the WebSocket handler runs. Do not expose
Fastify request objects through a shared contract.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…