New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Pinme Share

by glitternetwork in glitternetwork/pinme

A skill your agent uses 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…

MITAuto-check: notesBackend & APIs

Install Pinme Share

skills CLI
$ npx skills add glitternetwork/pinme --skill pinme-share -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install glitternetwork/pinme pinme-share --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/glitternetwork/pinme.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pinme-share .claude/skills/pinme-share && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pinme-share
GitHub stars
3.7k
Token cost
~1.2k tokens
SKILL.md length
576 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • Works in 5 steps: Identify what is being shared → Create a static share artifact → Sanitize before publishing → …
  • The user wants to share
  • SKILL.md covers When to Use, Core Workflow, Share Page Content and HTML Guidelines, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pinme Share is an agent skill from glitternetwork/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.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs. The repository describes itself as: Deploy Your Frontend in a Single Command. Claude Code Skills supported. The licence is MIT.

When your agent uses it

  • The user wants to share
  • Upload a static result through PinMe
  • Especially by generating a static HTML share page for a PinMe project link
  • Deployed full-stack app

Example prompts

  • “/pinme-share”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify what is being shared
  2. Create a static share artifact
  3. Sanitize before publishing
  4. Upload with PinMe
  5. Return the URL printed by PinMe. If PinMe outputs multiple URLs, prefer DNS domain, then PinMe subdomain, then short URL, then full…

What it can do on your machine

Read from SKILL.md and the folder at commit 7822b05. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pinme Share loads about 1.2k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 576 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:34
    - Remove secrets, tokens, API keys, `.env` values, internal-only URLs, private user data, and unrelated logs.
  • NoteMentions a .env fileSKILL.md:107
    - `.env`, `.git`, `node_modules`, source trees, private datasets, raw logs with credentials, or unrelated build cache.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from glitternetwork/pinme at commit 7822b05, republished under its MIT licence (© glitternetwork). 576 words, ~1,166 tokens.

Download SKILL.mdSave it as .claude/skills/pinme-share/SKILL.md (or your agent's skills folder).
name
pinme-share
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`.

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

For a project share page, include:

  • Project name and one-sentence description.
  • Primary launch/demo link as the first action.
  • What it does, who it is for, and why it matters.
  • Feature list focused on user-visible behavior.
  • Build/deploy details only when useful to the recipient.
  • Date and provenance such as "Created with Codex" only if appropriate.

For a conversation share page, include:

  • Conversation title.
  • Initial goal or question.
  • Key context and constraints.
  • Decisions made.
  • Work completed or answer summary.
  • Files changed, commands run, links produced, or artifacts created when relevant.
  • Follow-up items.

For a file/report share page, include:

  • Clear title and short abstract.
  • Download/open link to the uploaded artifact if there is a separate file.
  • Important excerpts or generated summary.
  • Source/context notes.
Show full SKILL.md (183 more words)Show less

HTML Guidelines

  • Build a real share page, not a generic placeholder.
  • Make the most important link visible in the first viewport.
  • Use clean, responsive HTML/CSS that works as a standalone static file.
  • Keep the design restrained and readable; avoid overdecorated marketing layouts for technical handoffs.
  • Use semantic sections, accessible contrast, descriptive link text, and sensible mobile spacing.
  • Escape user-provided text before inserting it into HTML.
  • If showing code or command output, wrap it in <pre><code> and keep it short.

PinMe Upload Checklist

Before upload:

bash
pinme --version

If PinMe is missing or stale, install or update it according to the main pinme skill. Authentication is required for upload:

bash
pinme login
# or: pinme set-appkey <AppKey>

Upload examples:

bash
pinme upload share/my-project
pinme upload share/conversation-summary
pinme upload ./report.html
pinme upload ./dist

Do not upload:

  • .env, .git, node_modules, source trees, private datasets, raw logs with credentials, or unrelated build cache.
  • Raw conversation transcripts that may include secrets or private context unless the user explicitly approves the exact content.

Final Response

Tell the user:

  • What share artifact was created.
  • The PinMe URL returned by upload.
  • Any important caveat, such as skipped upload because PinMe was not authenticated or unavailable.

Keep the response short. The URL is the main deliverable.

© glitternetwork, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/pinme-share of glitternetwork/pinme.

Open the folder on GitHubat commit 7822b05

Compare with similar skills

Pinme Share next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pinme Share compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pinme Share this skillglitternetwork/pinme3.7k—~1.2kAutomated safety check: NotesMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
Nestjs Best Practicesrolling-scopes/rsschool-app10k6 repos~1.2kAutomated safety check: PassMIT
Sub2API AdminWei-Shaw/sub2api43k1 repos~717Automated safety check: PassLGPL-3.0
Firecrawl Build Onboardingfirecrawl/firecrawl190k1 repos~1.4kAutomated safety check: NotesISC
Obsidian BasesAtmosphere/atmosphere3.8k22 repos~3.2kAutomated safety check: PassApache-2.0

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed

  • Nestjs Best Practices

    rolling-scopes/rsschool-app

    NestJS best practices and architecture patterns for building production-ready applications.

    10k GitHub starsUsed in 6 repos~1.2k tokens
    Backend & APIsAuto-check passed

  • Sub2API Admin

    Wei-Shaw/sub2api

    Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.

    43k GitHub starsUsed in 1 repo~717 tokens
    Backend & APIsAuto-check passed

  • Firecrawl Build Onboarding

    firecrawl/firecrawl

    Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

    190k GitHub starsUsed in 1 repo~1.4k tokens
    Backend & APIsAuto-check: notes

  • Obsidian Bases

    Atmosphere/atmosphere

    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries.

    3.8k GitHub starsUsed in 22 repos~3.2k tokens
    Backend & APIsAuto-check passed

  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed

More from glitternetwork/pinme

  • Pinme LLM

    glitternetwork/pinme

    A skill your agent uses when a PinMe project (Worker TypeScript) needs to call OpenRouter-backed LLM APIs, including models, chat/completions, streaming, or OpenRouter web search.

    3.7k GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed

  • Pinme

    glitternetwork/pinme

    A skill your agent uses when the user mentions "pinme", or needs to upload files, store to IPFS, create/publish/deploy websites or full-stack services (including frontend pages, backend APIs…

    3.7k GitHub stars~3.8k tokensUpdated 26 days ago
    Auto-check: notes

  • Pinme Auth

    glitternetwork/pinme

    A skill your agent uses when a PinMe project (Worker TypeScript) needs to integrate user authentication — creating email/password users, verifying idtokens, querying user info, or listing users via…

    3.7k GitHub stars~2.6k tokensUpdated 26 days ago
    Auto-check passed

  • Pinme Email

    glitternetwork/pinme

    A skill your agent uses when a PinMe project (Worker TypeScript) needs to integrate email sending (sendemail).

    3.7k GitHub stars~1.2k tokensUpdated 26 days ago
    Auto-check passed

  • Pinme R2

    glitternetwork/pinme

    A skill your agent uses when a PinMe Cloudflare Worker needs R2 object storage, including secure file or image upload, streaming download, metadata lookup, deletion, listing, Range requests, or…

    3.7k GitHub stars~3.6k tokensUpdated 26 days ago
    Auto-check passed

  • Pinme Uniwebpay

    glitternetwork/pinme

    A skill your agent uses when generating, modifying, or reviewing PinMe Worker (Cloudflare Worker TypeScript) code that accepts payments through UniwebPay — payment links, products/prices, checkout…

    3.7k GitHub starsUsed in 1 repo~7.3k tokens
    Auto-check passed

Categories

Questions about Pinme Share

What does Pinme Share do?

A skill your agent uses 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…. Pinme Share is an agent skill from glitternetwork/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.

When should I use Pinme Share?

Pinme Share fits situations like: the user wants to share; upload a static result through PinMe; especially by generating a static HTML share page for a PinMe project link; deployed full-stack app.

How do I install Pinme Share in Claude Code?

Run `npx skills add glitternetwork/pinme --skill pinme-share -a claude-code`. Or copy the skill folder (skills/pinme-share in glitternetwork/pinme) into .claude/skills/pinme-share in your project. Claude Code loads it when a task matches its description.

How do I install Pinme Share in Codex?

Run `npx skills add glitternetwork/pinme --skill pinme-share -a codex`. Or copy the skill folder (skills/pinme-share in glitternetwork/pinme) into .agents/skills/pinme-share in your project. Codex loads it when a task matches its description.

Can I use Pinme Share in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add glitternetwork/pinme --skill pinme-share -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pinme-share, .gemini/skills/pinme-share, .github/skills/pinme-share and .opencode/skills/pinme-share in your project.

What does Pinme Share need to run?

SKILL.md names no scripts, command-line tools or credentials: Pinme Share is instructions for the agent only.

Does Pinme Share access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pinme Share safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Pinme Share use?

Pinme Share is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pinme Share use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pinme Share?

Skills that share tags, products or a category with Pinme Share: Configuring Horizon (coollabsio/coolify, 63k stars), Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Sub2API Admin (Wei-Shaw/sub2api, 43k stars) and Firecrawl Build Onboarding (firecrawl/firecrawl, 190k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pinme Share?

glitternetwork (a GitHub organization) maintains it in glitternetwork/pinme, which has 3,746 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 12, 2026.

Source: glitternetwork/pinme on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.