communicator

Present completed work to humans and request decisions through rendered artifacts and plain language.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/happysasha18/live-spec --skill communicator-happysasha18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: communicator
Source: https://github.com/happysasha18/live-spec/tree/main/skills/communicator
Command: npx skills add https://github.com/happysasha18/live-spec --skill communicator-happysasha18

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI agents routinely describe visual work in words instead of showing it, and ask humans to decide in units they don't think in (pixels, dB, internal ids). This Skill fixes the human-facing exchange: it governs when and how an agent shows finished work, narrates progress, and asks for decisions a person can actually make. ## Core Features & Use Cases - Show, don't describe: Render side-by-side comparisons and mockups for visual or textual decisions instead of asking in raw units, with artifacts opened where the human will actually see them (browser or inline, never a bare file path). - Structured decision requests: Batch multiple open questions into one interactive HTML decision page with radio options, a marked recommendation, and a downloadable JSON answer file that gets harvested back into the work queue. - Progress narration and reporting: Twenty-two rules covering capture echoes, mid-work beats, offline windows, status boards, honest result reporting, and plain-language registers in the product's own vocabulary. - Use Case: After an agent finishes a UI change, it opens a rendered before/after page in the browser with a one-line passport stating what needs the human's word, rather than pasting a wall of test counts and version strings into chat. ## Quick Start Ask the agent to show you the finished change rendered side by side with the previous version and to present any open choices as one decision page with its recommendation marked.

Frequently Asked Questions about communicator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an AI agent to show visual changes instead of describing them?▼

Use rules that require rendering side-by-side comparisons and opening artifacts in the browser or inline in chat. The agent must never hand over a bare file path or ask questions in raw units like pixels or decibels.

How to collect multiple decisions from a user in one step?▼

Render one interactive HTML decision page with one card per question, radio options, a marked recommendation, and a Download JSON button. The saved answers file is read back and harvested into the project queue the same session.

What is the best way for an agent to report progress during long tasks?▼

Narrate beats as work runs: a start line for detached operations, heartbeat updates roughly every two minutes, and a digest when each pipeline step completes. Long stretches get an offline window stating when the human can step away and when they are needed again.

Does this skill work for remote or cloud-based agent sessions?▼

Yes, the channel is picked by seat. Local sessions open rendered pages in a browser; remote sessions show work textually through inline chat markdown or host-rendered artifact pages, and the seat is re-detected after any machine move.

When should an agent not escalate a question to the human?▼

An agent should not escalate decisions it can make itself, and should never interrupt mid-work for narration-level updates. Only genuine decisions, finished results, and problems needing the human's word warrant a direct ask.