本文へ移動
cccskills
無料GitHub で公開

report-designer

Polish an existing report, deck, or HTML page to the ReportRoom design bar — visual hierarchy, typography, charts, dark mode, OG/social link preview. Use when the user says "make it beautiful", "improve the design", "it looks plain", "fix the layout" about something already written or published. Not for creating content from scratch (use report-publisher or deck-publisher).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Report Designer

The polish pass: takes an existing document — a draft, a published ReportRoom page, or pasted HTML — and raises it to the design bar without touching the substance.

Follow the shared flow in the root SKILL.md (get_design_system is the source of truth; lint before republish).

When to use

  • "Make it beautiful / less plain / more professional"
  • A page published earlier needs a visual upgrade
  • Another skill's output was approved on content but the user wants another design pass

What a design pass covers

Work through these in order; each is a check, not an automatic rewrite:

  1. Hierarchy — is the most important thing visually the biggest thing? Title states the conclusion; section headings scannable as a story on their own.
  2. Typography & rhythm — design-system type scale applied; line lengths readable; whitespace between sections doing the separating (not horizontal rules everywhere).
  3. Data presentation — numbers that compare become charts; tables get aligned columns and clear headers; every chart labeled well enough to survive being screenshot alone.
  4. Color & emphasis — design-system palette only; emphasis (callouts, highlights) reserved for the few things that deserve it. If everything is highlighted, nothing is.
  5. Dark mode & responsiveness — verify both render correctly, especially charts and images.
  6. Link presentation — title/description/OG image make the page unfurl well when shared in Slack/LinkedIn/iMessage — the unfurl is the first impression.

Steps

  1. Get the current document (from the conversation, or list_documents → the published page).
  2. Run the six checks; list what you'll change and why, in one short list — get a nod before a big restyle.
  3. Apply, lint_document, show before/after summary, republish on approval (same URL — publish replaces).

Hard rules

  • Never change words, numbers, or ordering of arguments — design pass means design only. If the content needs work, say so separately.
  • Don't fight the design system with custom overrides; if it can't express something, simplify the element rather than hacking around it.
  • The "Published with ReportRoom" footer credit is added by ReportRoom at publish and is part of every page by design — don't try to hide, restyle, or override it as part of a polish pass.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Create and publish a recurring client-facing deliverable — SEO or analytics monthly, project status report, audit results — as a branded live page with view tracking. Use when the user says "client report", "monthly report for", "status update for the client", "send this to my client". Not for one-off research shares (use report-publisher) or proposals (use proposal-tracker).

日本語の概要は準備中です。原文の説明を表示しています。

dashaworks/report-skills122026年8月6日 更新

Turn content into a responsive, presenter-friendly slide deck published at a live URL via ReportRoom. Use when the user says "make this a deck", "turn this into slides", "presentation for", or wants something to present rather than read. Not for long-form documents (use report-publisher) or polishing an existing deck (use report-designer).

日本語の概要は準備中です。原文の説明を表示しています。

dashaworks/report-skills122026年8月6日 更新

Publish a proposal, offer, or pitch as a tracked link and report back whether it's getting read (view analytics after sending). Use when the user says "send the proposal", "did they open it", "track whether they read it", "share the offer". Not for recurring client reports (use client-reporter) or general research shares (use report-publisher).

日本語の概要は準備中です。原文の説明を表示しています。

dashaworks/report-skills122026年8月6日 更新

Turn research, analysis, or any markdown the agent just produced into a live, beautifully designed web report with a shareable tracked URL via ReportRoom. Use when the user says "publish this", "make this shareable", "turn this into a report", "put this on a page", or wants findings to live beyond the chat. Not for recurring client deliverables (use client-reporter), slide decks (use deck-publisher), or proposals that need view alerts (use proposal-tracker).

日本語の概要は準備中です。原文の説明を表示しています。

dashaworks/report-skills122026年8月6日 更新

Shared setup and rules for the report-skills bundle (report-publisher, client-reporter, proposal-tracker, deck-publisher, report-designer). Loaded by the individual skills for the common ReportRoom MCP publish flow, account bootstrap, and safety gates. Not invoked directly — pick the specific skill for the job.

日本語の概要は準備中です。原文の説明を表示しています。

dashaworks/report-skills122026年8月6日 更新

dashaworks のスキルをすべて見る

このスキルの問題を報告する