AgentStack
SKILL verified MIT Self-run

Report Designer

skill-dashaworks-report-skills-report-designer · by dashaworks

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).

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-dashaworks-report-skills-report-designer

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Report Designer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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_sites → 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.