json-render-slacklisted
Install: claude install-skill SergeyGalaxyOrsik/json-render-slack
# json-render → Slack (Incoming Webhook, no bot)
json-render's chat renderer (`@json-render/chat`) was built for the Vercel Chat SDK, whose docs assume a Slack **bot** (`SLACK_BOT_TOKEN`, signing secret, `thread.post`). Most "send a report to a channel" jobs only have an **Incoming Webhook URL**. You don't need the bot: the two pure functions in the middle of that pipeline work on their own.
```
Spec (JSON) ──toCard()──▶ CardElement ──cardToSlackBlocks()──▶ Block Kit ──POST──▶ webhook
@json-render/chat @chat-adapter/slack/blocks { text, blocks }
```
Neither function talks to Slack or needs credentials, and both are side-effect free, so they are easy to unit-test.
## Install
```bash
bun add @json-render/core @json-render/chat @chat-adapter/slack chat zod
# or npm i / pnpm add the same list
```
`chat` is only a peer dependency, used for the `CardElement` type; nothing from it runs. Verified with `@json-render/chat@0.22.0`, `@chat-adapter/slack@4.45.0`, `chat@4.45.0`. If the installed versions differ a lot, run `scripts/spec-to-blocks.ts` on a sample spec before relying on the mapping below.
## The core code
```ts
import type { Spec } from "@json-render/core";
import { toCard } from "@json-render/chat";
import { cardToSlackBlocks, cardToSlackFallbackText, type SlackBlock, type SlackCardElement } from "@chat-adapter/slack/blocks";
export function specToSlack(spec: Spec): { text: string; blocks: SlackBlock[] } {
// Chat SDK's CardEleme