Back to Details

pinme-share

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

PinMe Share

PinMe 分享

Create a polished static share artifact, upload it with 
pinme upload
, and return the final URL.
创建精美的静态分享制品，使用
pinme upload
上传，并返回最终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.
当用户提出以下需求时使用此技能：
  • 使用PinMe分享或发布成果。
  • 创建静态页面来包装已部署的项目链接、演示、报告或制品。
  • 总结Codex对话/会话并以页面形式分享。
  • 将项目交接内容转换为公开的着陆页或摘要页。
  • 上传现有的静态文件或文件夹进行轻量级分发。
如果用户需要后端、数据库、认证、邮件或LLM功能，请先使用主
pinme
技能及任何相关的PinMe集成技能。在最后使用
pinme-share
来打包并发布成果。

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.
  1. 确定要分享的内容：
    • PinMe/全栈项目：已部署URL、简短描述、核心功能、技术栈、使用说明。
    • Codex对话：目标、决策、实现摘要、重要输出、后续步骤。
    • 静态文件/报告/演示：标题、用途、文件内容或预览、收件人相关背景信息。
  2. 创建静态分享制品：
    • 优先选择单一自包含的
      index.html
      文件。
    • 使用当前工作区中的
      share/<slug>/index.html
      ，除非仓库已有现有的输出/分享约定。
    • 为了可移植性，将CSS内联使用。
    • 除非需要交互功能，否则不要依赖JavaScript。
  3. 发布前清理内容：
    • 删除密钥、令牌、API密钥、
      .env
      值、仅限内部访问的URL、用户私有数据以及无关日志。
    • 对于对话摘要，进行总结而非直接转储原始记录，除非用户明确要求逐字分享。
    • 确保链接明确且可点击。
  4. 使用PinMe上传：
    bash
    pinme upload share/<slug>
  5. 返回PinMe输出的URL。如果PinMe输出多个URL，优先选择DNS域名，其次是PinMe子域名，然后是短URL，最后是完整预览URL。切勿截断哈希片段。

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.
项目分享页应包含：
  • 项目名称和一句话描述。
  • 将主要启动/演示链接作为首个操作项。
  • 功能介绍、目标用户及价值所在。
  • 聚焦用户可见功能的特性列表。
  • 仅在对收件人有用时才包含构建/部署细节。
  • 仅在合适时添加日期和来源信息，例如“由Codex创建”。
对话分享页应包含：
  • 对话标题。
  • 初始目标或问题。
  • 关键背景和约束条件。
  • 已做出的决策。
  • 已完成的工作或答案摘要。
  • 相关的文件变更、执行的命令、生成的链接或创建的制品。
  • 后续待办事项。
文件/报告分享页应包含：
  • 清晰的标题和简短摘要。
  • 如果存在单独文件，添加上传制品的下载/打开链接。
  • 重要摘录或生成的摘要。
  • 来源/背景说明。

HTML Guidelines

HTML指南

  • 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.
  • 创建真实的分享页，而非通用占位符。
  • 最重要的链接要在首屏可见。
  • 使用简洁、响应式的HTML/CSS，可作为独立静态文件运行。
  • 设计要简洁易读；技术交接场景避免过度装饰的营销布局。
  • 使用语义化区块、符合无障碍标准的对比度、描述性链接文本以及合理的移动端间距。
  • 将用户提供的文本插入HTML前进行转义处理。
  • 如果展示代码或命令输出，将其包裹在
    <pre><code>
    标签中并保持内容简短。

PinMe Upload Checklist

PinMe上传检查清单

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
上传前：
bash
pinme --version
如果PinMe缺失或版本陈旧，请根据主
pinme
技能进行安装或更新。上传需要认证：
bash
pinme login

or: pinme set-appkey <AppKey>

或：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.

上传示例：

```bash
pinme upload share/my-project
pinme upload share/conversation-summary
pinme upload ./report.html
pinme upload ./dist
请勿上传：
  • .env
    、
    .git
    、
    node_modules
    、源码树、私有数据集、包含凭证的原始日志或无关的构建缓存。
  • 可能包含密钥或私有上下文的原始对话记录，除非用户明确批准具体内容。

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.
告知用户：
  • 创建了何种分享制品。
  • 上传后PinMe返回的URL。
  • 任何重要注意事项，例如因PinMe未认证或不可用而跳过上传。
回复要简洁。URL是主要交付成果。