# Newspaper

> Maintain a live, editable newspaper-style canvas for meaningful progress, decisions, risks, findings, code, tables, metrics, and local media during a long-running task.

- Skill: `superliaye/newspaper` (Agent Skill, multi-file: 9 files)
- Install (CLI): `npx get-skill add superliaye/newspaper`
- Raw SKILL.md: https://api.skillmd.com/api/skills/superliaye/newspaper/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: superliaye (https://skillmd.com/u/superliaye)
- Updated: 2026-11-21
- Page: https://skillmd.com/skills/superliaye/newspaper

---


# newspaper

Use the bundled launcher to create a run:

```sh
node "<skill-directory>/scripts/newspaper.mjs" start
```

Keep both values it prints: the exact `canvas.json` path and the live URL. Share the URL with the
user immediately. Each run is isolated, so use that exact path for every later update.

Hydrate the canvas only at meaningful checkpoints: phase transitions, noticeable progress,
decisions, risks, or material findings. Patch stable keyed entries in `canvas.json`; leave its
`revision` unchanged because the service advances accepted revisions. Run `validate --run
<run-key>` after an uncertain edit and repair any error reported in the adjacent `validation.json`.
Keep the canvas useful as current state rather than an event transcript.

Write for scanning: put the conclusion in the headline, open long stories with a one-sentence
takeaway, and use short Markdown sections, bold labels, lists, or tables to expose the structure.
Split dense material across focused cards and use callout, metric, table, or code nodes when those
forms communicate the important information more clearly than prose.

The default document demonstrates the common fields. Read `references/canvas-schema.md` when you
need code, table, metric, callout, media, edges, explicit placement, or another region.

When the user asks what they changed, read the exact `canvas.json`, including node content,
`focus`, and explicit `frame` geography. Browser edits persist there.

Use `status --run <run-key>` to recover paths and the URL. Use `close --run <run-key>` only when the
user no longer needs the live surface; closing removes that run instead of creating a final edition.

