Install
$ agentstack add skill-dashaworks-report-skills-report-publisher ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- 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.
- 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…").
- 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").
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dashaworks
- Source: dashaworks/report-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.