본문으로 건너뛰기
cccskills
무료GitHub에 공개

report-publisher

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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, include your suggested title — titles that state the conclusion travel better than topic labels ("X is 30% cheaper than Y at scale", not "X vs Y comparison").
  4. Publish and hand over the URL. Mention the page is tracked: "ask me later how it's doing" (get_analytics).

Hard rules

  • Preserve the substance exactly — restructuring is allowed, changing findings, numbers, or hedges is not.
  • Keep the user's citations/sources; a published report without its sources is a downgrade, not an upgrade.
  • If content contains third-party confidential material (client names in research, quoted private messages), flag it at the approval gate.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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의 스킬 모두 보기

이 스킬의 문제 신고