← Search

PinMe Share — polished share pages for results
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 7822b05
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a PinMe account with the pinme CLI installed and…

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

At a glance
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.

Version:

@

Quick answer

PinMe Share is a free Muse 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 covering decisions, work done, files changed and follow-ups, or a report, file or demo.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 7822b05

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/glitternetwork/pinme/7822b0501607786958ecb458f3bd02a061933efa/skills/pinme-share/SKILL.md Pinned version: install the code at commit 7822b0501607786958ecb458f3bd02a061933efa exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 7822b05 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
7822b05 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.