Skip to content
Design
Skill

/bots

Turns chosen Grok Bots into a shakeable pile, portfolio cards and an org chart page, each with a link to copy the bot, with private details stripped.

From plugin
userinterface
6526 skills

Claude Code

$ npx -y skills add raphaelsalaja/skills --skill bots --agent claude-code

SKILL.md

bots.SKILL.md
name: bots
description: Turns chosen Grok Bots into a shakeable pile, portfolio cards and an org chart page, each with a link to copy the bot, with private details stripped.
disable-model-invocation: true

Bots

This skill puts the user's Grok Bots on their site. A prompt run inside Grok collects the chosen Bots and their copy links, then the site gets one data file, a physics pile, cards and an org chart page.

Exact physics, only the Bots the user picks

The marks in [marks.js](marks.js) and the values in [pile.js](pile.js) are exact. The copy comes from the Bots themselves and is trimmed, never invented. It applies whenever Grok Bots are shown on a site.

Living eyes and their reactions belong to `avatar`. Label case and word counts belong to `copy`. Surfaces, hover, focus, theme and sound cues belong to `defaults`. Easing and durations outside the pile belong to `motion`, and contrast belongs to `color`. Building in the project's own components belongs to `reuse`. Opening the result belongs to `verify`, and committing belongs to `ship`.

1. Run the Grok round

Give the user the prompt in [grok.md](grok.md) to paste into their primary Bot. It lists every Bot, waits for the user's picks, has each picked Bot clean and describe itself, then hands over a publish checklist.

Only the Bots the user picked go on the site. A Bot added because it looked good is `bots-user-picks`.

Wait for the JSON array it returns. When the user pastes setups directly instead, read those the same way.

2. Strip what is private

Check every entry again, whatever the Bots already removed. Strip emails, phone numbers, addresses, other people's names, clients, employers, private projects, internal links, keys, tokens, account details, memory and personal facts.

When unsure, leave it out and list it at the end. A client name kept because it seemed harmless is `bots-strip-private`.

A copy link comes only from a published template the user pasted back. A link written from a guessed pattern or a Bot's id is `bots-real-links`.

3. Write one data file

All Bots live in one typed file, such as `data/bots.ts`, one entry per Bot. Areas, shapes and colours are `as const` unions, and `shareUrl` and `video` are optional. Bots spread across components is `bots-one-file`.

Each entry holds a title of 2–3 words, one line of description and 3–5 short items it does. Routines read in plain words with a time, such as "Daily idea drop, 9am", and tools are short names. A paragraph pasted from the Bot's instructions is `bots-entry-shape`.

The areas are the user's own sidebar sections in Grok, named and ordered as they are there. The entry marked `lead` is the primary Bot.

Shape and colour come from each Bot's published page, as [grok.md](grok.md) describes. A shape or colour picked by eye from a screenshot is `bots-page-marks`.

4. Draw each Bot in its own mark

Copy [marks.js](marks.js) beside the components. Each Bot is drawn in the shape and colour it has in Grok, from `MARKS[shape].path` and `markEyes(shape)`, with fills from `MARK_COLORS`. A generic avatar or an initial in a circle is `bots-real-marks`.

Black takes the page's text colour for the body and its background for the eyes, so it flips with the theme. Give the eyes life with `avatar`.

5. Build the pile

The home page gets a section titled "Grok Bots" holding one card. Inside it sits a 300px stage, 340px under 480px wide, and every Bot as an absolutely placed piece. Shuffle the order with a seeded random so the server and client agree.

Copy [pile.js](pile.js) beside the component and add `matter-js`. Call `createPile` once the pieces mount and `destroy` on unmount.

Each body is the mark's convex hull from `markHull`, so stars rest on their points and blobs roll. Circles for every shape is `bots-hull-bodies`.

A drag pulls the Bot through a spring while the world keeps stepping, so it shoves its neighbours. Pausing the world during a drag is `bots-drag-pushes`. Pieces take `touch-action: none` and the stage `pan-y`, so the page still scrolls.

Bots squash against contacts and stretch along their velocity, clamped and normalised to keep their area. A squash that grows the Bot or flips it inside out is `bots-jelly-keeps-area`.

A shake throws every Bot up 3–7px a frame and sideways up to 6, never enough to leave the stage. A phone shake does the same once iOS grants motion access from the button tap. A shake that throws Bots out of view is `bots-shake-stays-in`.

`on.bump` passes a soft hit to the avatar as a blink and a hard hit as a spin. `on.sound` plays a low thud, 150Hz falling to 64Hz over 70ms, only once a grab has unlocked audio. A pile that makes sound before the user touches it is `bots-quiet-until-touched`.

A tap shows the Bot's title as a pill linking to its card, above the Bot or below it near the top. A drag past 6px opens nothing, and a tap elsewhere closes it. A drag that also opens the name is `bots-tap-names`.

The loop runs only while the stage is on screen and something still moves or wobbles. A loop that keeps running once the pile sleeps is `bots-sleep-when-still`.

Under reduced motion, `pile.js` runs the drop offline and draws the settled pile once. A shake reshuffles instantly. A pile that still tumbles is `bots-settle-when-reduced`.

Under the stage sit two equal buttons: Shake Bots on a quiet grey surface and View Bots in the solid primary style, linking to the Team page. A lone icon button in the stage corner is `bots-two-actions`.

6. Build the cards

`BotCard` shows the mark, the title and a two-line description. Opening it shows what it does, its routines, its tools as small tags and an optional muted looping clip. Cards in a row share one height.

Copy This Bot opens the share link in a new tab and says so to screen readers. A Bot with no link shows no button. A disabled Link Coming Soon button is `bots-no-dead-copy`.

7. Lay out the Team page as an org chart

The lead Bot sits alone at the top. A hai

Read more
@raphaelsalaja
Ships withuserinterface

A collection of agent skills for building interfaces with coding agents.

Stars on GitHub

Momentum

stars in total
65
Star history of raphaelsalaja/skill on GitHub, a chart by star-history.com

Other skills on userinterface.

alignment

alignment

Measures a running page for edges, gaps, centring and radii that miss by a pixel or two, then judges visual weight and returns a…

audit

audit

Reviews a change, a session or a whole codebase against every skill in this collection and returns one ranked, numbered report.

avatar

avatar

Draws any object as a flat character with two capsule eyes, then animates its whole body so it glances, blinks, breathes, follows…

color

color

Holds text and control contrast to exact ratios, routes colour through role tokens and gives dark mode its own palette.

More skills from other plugins.

impeccable

impeccable

Use to design, redesign, critique, audit, polish or animate a frontend: websites, landing pages, dashboards, app UI, components,…

@pbakaus@pbakausInstall Skill

Questions about bots.

Which coding agents can use bots?
bots installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.