share-as-link-skill

KO | EN

gitlite — search

#typescript #ai-agents #ai #dsh-plugin #deepseek-harness #open-source #cli #claude-code #codex #developer-tools #react #windows

share-as-link-skill

★ 92 Open GitHub ↗

Claude Code & Codex skill: say "share this as a link" and any AI output — chat, artifact, or markdown — becomes a live public URL in ~10 seconds, with document tracking (aggregate view counts). A lightweight DocSend alternative for the simple case. Publishes via the ReportRoom MCP.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Share as Link — a Claude Code & Codex skill that turns any AI output into a live URL

> **Status: new.** Freshly published and not yet exercised end-to-end against a live account — feedback and issues welcome.

**share-as-link** is a free Claude Code & Codex skill that publishes AI output — a conversation, an analysis, an artifact, a markdown file — as a live shareable webpage with built-in document tracking (aggregate view counts). The content is published verbatim, without restructuring or reformatting; a typical publish takes about ten seconds.

## What it does

- Take whatever was just produced — chat output, an artifact, a markdown file — and
  publish it **verbatim** to a live URL, with light theming for readability.
- Return the link immediately, with a short, readable slug.
- Attach view analytics, so the agent can later report whether anyone opened the page.
- Warn before publishing anything that looks sensitive — published pages are public URLs.

## How do I share Claude's output as a link?

Install the skill (one command, below), then say **"share this as a link"** — or "put this
online", "make this a page", "give me a link". Claude publishes the output as-is and returns
a live URL. No export step, CMS, or hosting setup is involved.

The flow is the same for chat answers, artifacts, and markdown files, from Claude Code or Codex.

## Can I track who opened my link?

You can see **whether and how much** it was opened: every published page comes with
aggregate view counts by day. Asking Claude "did anyone open that link?" returns those
counts.

What is not available from a plain link is *who* opened it — there is no per-viewer identity
on a public URL. Confirming that a specific person opened a specific document (investor
decks, due diligence) requires an email-gated data room — see the
[virtual data room skill](https://github.com/dashaworks/data-room-skill).

## Document tracking scope

Most document tracking tools assume a sales workflow: upload a PDF, gate it behind an email
form, receive per-viewer engagement scores. This skill covers the simpler case of checking
whether a page was viewed at all: publish, share, then check aggregate views over time. For
the full tracked-document workflow — per-viewer opens on a proposal, or a gated data room —
the [report-skills](https://github.com/dashaworks/report-skills) hub and the
[data room skill](https://github.com/dashaworks/data-room-skill) cover those cases.

## Comparison with DocSend

DocSend alternatives are often evaluated for link sharing plus basic analytics, without seat
licenses or an email gate for every recipient. For that use, a published page with view
counts covers the requirement: recipients open the link directly, with nothing to sign up
for.

DocSend's core feature — per-viewer, page-by-page engagement on a gated document — is not
part of this skill. The [data room skill](https://github.com/dashaworks/data-room-skill)
provides the equivalent.

## What the link is (and isn't)

Properties of a published link:

- **Public.** The page lives on a public URL and can be indexed by search engines. The
  random slug makes it hard to guess, but that is obfuscation, not access control. Do not
  publish secrets, credentials, or confidential data — the skill scans and warns, but the
  decision to publish is the user's.
- **Aggregate analytics only.** View counts by day. No per-viewer identity, no record of
  which person opened which page. Per-viewer tracking exists only in data rooms.
- **Branded footer.** Every page carries a small "Published with ReportRoom" credit.
- **Verbatim.** The content is published as-is — light theming, no rewriting.

## Scope

This skill publishes content as-is. It does not restructure, rewrite, or redesign, which is
what keeps a publish to roughly ten seconds.

For content that needs more:

- **Restructuring and design** → [report-skills](https://github.com/dashaworks/report-skills)
  reshapes content into a structured document and applies the design system.
- **Read tracking on a document sent to a specific person** →
  the tracked-proposal skill in [report-skills](https://github.com/dashaworks/report-skills).

## Install

```bash
/plugin marketplace add dashaworks/share-as-link-skill
```

## How it works

Publishes through the **[ReportRoom](https://reportroom.io) MCP server** — a single publish
call returns a live URL with analytics attached. ReportRoom is a hosted service; the skill
provisions a free account in-conversation on first use, and published pages carry a small
"Published with ReportRoom" footer credit.

## Related skills

- [report-skills](https://github.com/dashaworks/report-skills) — the AI report generator hub:
  designed reports, tracked proposals, published decks
- [data-room-skill](https://github.com/dashaworks/data-room-skill) — virtual data room skill
  for fundraising & M&A, with per-viewer tracking
- [seo-client-report-skill](https://github.com/dashaworks/seo-client-report-skill) — monthly
  SEO client report skill for agencies

All publish through [ReportRoom](https://reportroom.io).

## License

MIT — see [LICENSE](LICENSE).

share-as-link-skill

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README