glitternetwork/pinme / skills/pinme-share
pinme-share
VerifiedUse 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
- 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.
- Create a static share artifact:
- Prefer a single self-contained
index.html. - Use
share/<slug>/index.htmlin 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.
- Prefer a single self-contained
- Sanitize before publishing:
- Remove secrets, tokens, API keys,
.envvalues, 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.
- Remove secrets, tokens, API keys,
- Upload with PinMe:
pinme upload share/<slug> - 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.
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:
pinme --version
If PinMe is missing or stale, install or update it according to the main pinme skill. Authentication is required for upload:
pinme login
# or: pinme set-appkey <AppKey>
Upload examples:
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |