# Pinme Share

Use this skill when the user wants to share, publish, or upload a static result through...

- Repository: https://github.com/glitternetwork/pinme (3753 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-09-12
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add glitternetwork/pinme --skill pinme-share -g -a claude-code -y`
Codex: `npx skills add glitternetwork/pinme --skill pinme-share -g -a codex -y`
Cursor: `npx skills add glitternetwork/pinme --skill pinme-share -g -a cursor -y`
Gemini CLI: `npx skills add glitternetwork/pinme --skill pinme-share -g -a gemini-cli -y`

## Description

Use this skill when the user wants to share, publish, or upload a static result through PinMe, especially by generating a static HTML share page for a PinMe project link, deployed full-stack app, Codex conversation summary, report, file, demo, or any 分享/发布/上传分享页 request that should end with `pinme upload`.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# PinMe Share

Create a polished static share artifact, upload it with `pinme upload`, and return the final URL.

## When to Use

Use this skill when the user asks to:

- Share or publish a result using PinMe.
- Create a static page that wraps a deployed project link, demo, report, or artifact.
- Summarize a Codex conversation/session and share it as a page.
- Turn a project handoff into a public landing or summary page.
- Upload an existing static file or folder for lightweight distribution.

If the user needs a backend, database, auth, email, or LLM functionality, use the main `pinme` skill and any relevant PinMe integration skill first. Use `pinme-share` at the end to package and publish the result.

## Core Workflow

1. Identify what is being shared:
   - **PinMe/full-stack project**: deployed URL, short description, key features, tech stack, usage notes.
   - **Codex conversation**: goal, decisions, implementation summary, important outputs, next steps.
   - **Static file/report/demo**: title, purpose, file contents or preview, context for the recipient.
2. Create a static share artifact:
   - Prefer a single self-contained `index.html`.
   - Use `share/<slug>/index.html` in the current workspace unless the repo has an existing output/share convention.
   - Keep CSS inline for portability.
   - Do not require JavaScript unless interaction is valuable.
3. Sanitize before publishing:
   - Remove secrets, tokens, API keys, `.env` values, internal-only URLs, private user data, and unrelated logs.
   - For conversation summaries, summarize rather than dumping raw transcript unless the user explicitly asks for verbatim sharing.
   - Make links explicit and clickable.
4. Upload with PinMe:
   ```bash
   pinme upload share/<slug>
   ```
5. Return the URL printed by PinMe. If PinMe outputs multiple URLs, prefer DNS domain, then PinMe subdomain, then short URL, then full preview URL. Never truncate hash fragments.

## Share Page Content

The rest: https://github.com/glitternetwork/pinme/blob/HEAD/skills/pinme-share/SKILL.md