sac-interaction

SaC Interaction Skill

Render interactive apps via the SaC (Software as Content) interaction layer. SaC turns structured content (markdown, data) into rich, interactive web UIs.

When to Use

USE this skill when:

• The user asks to create a visual UI, page, dashboard, or interactive app
• The user says "build me a ...", "show me a ...", "create a page for ..."
• The user wants to display data visually (charts, tables, guides, etc.)
• The user wants to update or evolve an existing SaC app
• You receive a message starting with "A user is viewing a SaC interactive app" (this is a callback from a rendered app — follow the instructions in the message)

Do NOT use when:

• The user just wants a text answer or chat reply
• The user wants to run a shell command or code locally

Infrastructure boundary (read first)

SaC server lifecycle is not your responsibility. You are a publish client, not an operator. Do not:

• restart, stop, or kill servers/processes
• change ports or migrate to a different port
• run test suites or debug unrelated infrastructure

If /inbox is unreachable (connection refused), tell the user: "SaC server unavailable — start it with sac serve." Then stop.

Server

SaC runs locally at http://127.0.0.1:18420. Always use this exact URL and port. Do not use any other port.

New App

Compose substantive markdown content first. Prefer structured sections, tables, data, and actionable items.

Publish in exactly one POST. Do not send a probe / draft POST to "test the endpoint" — the first POST becomes app v1.

Write content to a temp file, then use sac publish:

cat > /tmp/sac_content.md << 'CONTENT_EOF'
YOUR MARKDOWN CONTENT HERE
CONTENT_EOF

sac publish --file /tmp/sac_content.md \
  --intent "INTENT" \
  --callback-url "ws://127.0.0.1:18789?session=agent:main:main" \
  --callback-format openclaw_gateway \
  --callback-auth "Bearer YOUR_GATEWAY_TOKEN"

Replace CONTENT with your markdown and INTENT with a short description (e.g. "Tokyo travel guide").