PinMe Share — polished share pages for results
Turn a result into a polished static share artifact — project link, Codex conversation summary, report, file or demo — sanitize it (no secrets), and publish it with pinme upload
- What
- Turn a result into a polished static share artifact — project link, Codex conversation summary, report, file or demo — sanitize it (no secrets), and publish it with pinme upload
- Cost
- Free
- Needs
- a PinMe account with the pinme CLI installed and authenticated (`pinme login` or AppKey) — the main `pinme` skill should be installed too if the shared artifact needs a backend or database first
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @glitternetwork's PinMe Share skill: the publishing companion to the main `pinme` skill. It turns a finished result into a polished static share artifact — a share page wrapping a deployed project link, a Codex conversation summary (decisions, work done, files changed, follow-ups), or a report/file/demo — built as a single self-contained `index.html` with inline CSS, clean responsive design, and semantic accessible HTML. Enforces sanitization before publishing: strip secrets, tokens, API keys, `.env` values, internal-only URLs, private user data and raw transcripts (summarize instead unless verbatim sharing is explicitly approved), then `pinme upload share/<slug>` and return the full URL. Honest caveats: requires PinMe authentication (login or AppKey); if the task needs a backend, database, auth or email, use the main `pinme` skill first and `pinme-share` last. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a PinMe account with the pinme CLI installed and authenticated (`pinme login` or AppKey) — the main `pinme` skill should be installed too if the shared artifact needs a backend or database first Install "PinMe Share — polished share pages for results" for me. It gives my agent @glitternetwork's share workflow: identify what is being shared (deployed project, Codex conversation summary, static file/report/demo), build a polished single self-contained index.html share artifact (clean responsive HTML/CSS, inline styles, semantic accessible markup, most important link in the first viewport), sanitize it (remove secrets, tokens, API keys, .env values, internal-only URLs, private user data; summarize conversations rather than dumping raw transcripts unless verbatim sharing is explicitly approved), upload with `pinme upload share/<slug>`, and return the full final URL. MIT-licensed. Repository: https://github.com/glitternetwork/pinme/blob/main/skills/pinme-share/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "pinme-share". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. authenticate the pinme CLI with my account — that's on me). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.