Tooluck logoTooluck
SKILL.md

pinme-share

Agent skill fromglitternetwork/pinme

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

How to install pinme-share

install pinme-share
# install the pinme pack with the skills CLI
npx skills add glitternetwork/pinme

# or add only this skill to Claude Code: copy the folder

skills/pinme-share/

# into

~/.claude/skills/pinme-share/ (all projects)

.claude/skills/pinme-share/ (one project)

skills/pinme-share/SKILL.md

MITFull file
1# PinMe Share
2
3Create a polished static share artifact, upload it with `pinme upload`, and return the final URL.
4
5## When to Use
6
7Use this skill when the user asks to:
8
9- Share or publish a result using PinMe.
10- Create a static page that wraps a deployed project link, demo, report, or artifact.
11- Summarize a Codex conversation/session and share it as a page.
12- Turn a project handoff into a public landing or summary page.
13- Upload an existing static file or folder for lightweight distribution.
14
15If 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.
16
17## Core Workflow
18
191. Identify what is being shared:
20 - **PinMe/full-stack project**: deployed URL, short description, key features, tech stack, usage notes.
21 - **Codex conversation**: goal, decisions, implementation summary, important outputs, next steps.
22 - **Static file/report/demo**: title, purpose, file contents or preview, context for the recipient.
232. Create a static share artifact:
24 - Prefer a single self-contained `index.html`.
25 - Use `share/<slug>/index.html` in the current workspace unless the repo has an existing output/share convention.
26 - Keep CSS inline for portability.
27 - Do not require JavaScript unless interaction is valuable.
283. Sanitize before publishing:
29…

Excerpt shown under the repository's MIT license.

More skills in pinme

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates