report-publisher

Solid

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

AI & Automation 9 stars 1 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 77/100

Stars 20%
33
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Report Publisher The default "get it out of the chat" skill: whatever was just produced — deep research, a competitive analysis, a technical write-up — becomes a live web report with a URL worth sharing. Follow the shared flow in the root `SKILL.md` (access check → `get_design_system` → author → `lint_document` → approval → `publish`). This file covers only what's specific. ## When to use - The user finished a research/analysis task and says "publish this", "make this a report", "make this shareable", "I want to send this to someone" - Long markdown output that deserves better than a chat scroll or a raw gist - The user wants a link, not a file ## Steps 1. **Scope the content.** Confirm what goes in (the whole conversation output? just the final analysis?) and the audience (colleague, community, public). Audience decides tone of the framing, not the facts. If it's for the team rather than the world and the user is in a team workspace (`account_status` → `org_kind: team`), publish with `visibility: "team"` so only signed-in org members can view it. 2. **Structure for the web, don't paste.** Reshape chat-formatted output into a real document: a title that states the finding, an executive summary up top, sections with descriptive headings, data moved into tables/charts where the design system provides them, sources/appendix at the end. Cut conversational scaffolding ("as we discussed above…"). 3. **Author + lint + approval gate** per the shared flow. In the preview, incl...

Details

Author
dashaworks
Repository
dashaworks/report-skills
Created
2 weeks ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category