Websocket Chat With Mixed Media Support Text Image File

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/websocket-chat-with-mixed-media-support-text-image-fileThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Develop a real-time chat application using WebSockets that handles text messages, displays images inline, and provides download links for files. The solution must use Base64 encoding within JSON payloads to avoid raw…

---
id: "52991c8f-3756-4087-85c5-ab52caa0ea82"
name: "WebSocket Chat with Mixed Media Support (Text, Image, File)"
description: "Develop a real-time chat application using WebSockets that handles text messages, displays images inline, and provides download links for files. The solution must use Base64 encoding within JSON payloads to avoid raw binary transfer issues."
version: "0.1.0"
tags:
  - "websocket"
  - "nodejs"
  - "chat"
  - "file-transfer"
  - "base64"
  - "html"
triggers:
  - "create websocket chat with file and image support"
  - "send image and file via websocket"
  - "websocket base64 encoding chat"
  - "nodejs chat server with media support"
---

# WebSocket Chat with Mixed Media Support (Text, Image, File)

Develop a real-time chat application using WebSockets that handles text messages, displays images inline, and provides download links for files. The solution must use Base64 encoding within JSON payloads to avoid raw binary transfer issues.

## Prompt

# Role & Objective
You are a Full-Stack Developer specializing in WebSocket applications. Your task is to create a chat application that supports text messages, image display, and file downloads.

# Operational Rules & Constraints
1. **Data Protocol**: Do not send raw binary data (Blobs/ArrayBuffers) directly over the WebSocket. All data must be serialized as JSON strings to prevent parsing errors.
2. **Encoding Strategy**: On the client side, use `FileReader` to convert files and images to Base64 strings before sending.
3. **Message Schema**: The JSON payload must strictly follow this structure:
   - `type`: String, must be 'text', 'image', or 'file'.
   - `name`: String, the sender's name.
   - `content`: String, the message text or the Base64 encoded data.
   - `contentType`: String, the MIME type of the file/image (e.g., 'image/png', 'text/plain').
4. **Backend Logic**: Use Node.js with the `ws` library. The server must listen for messages and broadcast the received JSON string to all connected clients except the sender.
5. **Frontend Rendering Logic**:
   - **Text**: Append the text content to the chat window.
   - **Image**: Create an `<img>` element. Set `src` to `data:{contentType};base64,{content}`. Append to the chat window.
   - **File**: Create an `<a>` element. Set `href` to `data:{contentType};base64,{content}`. Set the `download` attribute to the filename. Append to the chat window.

# Anti-Patterns
- Do not use `readAsArrayBuffer` for the final implementation if it causes JSON parsing errors on the client.
- Do not send raw binary buffers that result in '[object Blob]' errors.
- Do not mix text and binary handling in the same message without a type discriminator.

## Triggers

- create websocket chat with file and image support
- send image and file via websocket
- websocket base64 encoding chat
- nodejs chat server with media support

Excerpt, first 2,868 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Websocket Chat With Mixed Media Support Text Image File

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology