PinMe Share
Create a polished static share page and upload it to PinMe in one command.
The skill mandates authentication before upload, either via `pinme login` or `pinme set-appkey`. It explicitly instructs to sanitize secrets, tokens, API keys, .env values, internal URLs, private data, and prohibits uploading .env, .git, node_modules, source trees, private datasets, or raw logs with credentials. This demonstrates awareness of least privilege and sensitive data handling. However, it lacks explicit user confirmation steps and sandboxing/rollback details. Publisher identity is unverified, so source attribution is incomplete. Deductions for missing explicit confirmation mechanisms and unverified publisher.
Instructions are self-consistent; core workflow is clear with a pre-upload checklist. The repository includes a CI workflow (ci.yml) running `npm run verify` on multiple Node versions and multiple test files (basic.test.ts, commands.test.ts, success.test.ts) covering auth-missing, nonexistent paths, invalid CIDs, etc. These provide evidence of both happy and failure paths. However, this static review does not execute anything, so reliability is capped at 10. Actual behavior in real environment is unconfirmed.
Scenario definition is clear: sharing/publishing static results, generating static HTML share pages for PinMe project links, conversation summaries, reports, etc. The skill explains when to use and when not, referring backend/database/auth/email/LLM needs to the main `pinme` skill. Trigger conditions are well specified in description and 'When to Use'. However, publisher is unverified and the skill depends on external PinMe CLI/network services that may be inaccessible or slow from mainland China, impacting Chinese users. Non-fit boundaries and environment constraints are not explicitly stated. Deductions for environmental fit and boundary evidence.
Documentation is well-layered: name, description, when-to-use, core workflow, HTML guidelines, upload checklist, final response. Examples are provided. However, no install/dependency notes (though README has them), no versioning or changelog, no maintenance responsibility, and no troubleshooting. License (MIT) exists in repo root but not referenced in the skill. Deductions for missing versioning, changelog, maintenance, and troubleshooting guidance.
The skill clearly describes how to complete the core task (create and upload a share page), with detailed steps and HTML guidelines. Repository tests (success.test.ts) simulate upload flow and verify URL output, suggesting CLI works as intended. However, the skill itself lacks concrete example outputs, and static review cannot confirm the generated share pages are directly usable or need light review. Thus score is capped at 7.
CI workflow and multiple test files exist, providing third-party executable evidence for CLI behavior and failure modes. However, this is a static review without execution, and tests target the CLI, not the skill itself. Evidence types are limited, cross-correlation is weak, and the skill's claims are not directly verified. Score 5.
- This skill depends on PinMe CLI and its network services, which may be inaccessible or slow from mainland China, affecting practical usability.
- The skill requires login or AppKey but does not specify secure storage; users should ensure their environment is secure.
- No explicit user confirmation or approval flow is provided; manual review of what gets uploaded is advised.
- Publisher identity is unverified; assess its reputation before use.
What does this skill do, and when should you use it?
This skill creates a clean static HTML share page to wrap a deployed project link, a Codex conversation summary, a report, a file, or a demo, then uploads it via `pinme upload` and returns the final URL. It identifies what is being shared, generates a self-contained `index.html`, sanitizes sensitive info, and uploads to PinMe. It is meant to be used at the end of a workflow, often after the full PinMe project flow, to publish the result.
Reads user-provided share content (e.g., project URL, conversation summary, file path), generates a self-contained share/<slug>/index.html with inline CSS for portability. Sanitizes secrets and internal URLs before publishing, and summarizes conversations instead of dumping raw transcripts. Runs pinme upload to publish to IPFS and extracts the final URL from CLI output, preferring DNS domains, then PinMe subdomains, then short URLs.
- A developer wants to share a deployed full-stack app with a feature list and tech stack.
- A user wants to summarize a Codex session and share it with a colleague, including decisions and next steps.
- Sharing a static report or demo file quickly, with a download or preview link.
- During project handoff, generating a public landing page that summarizes the project.
- A user already has a static `dist` folder and wants to upload it directly for sharing.
What are this skill's strengths and limitations?
- Zero-config one-command static deploy.
- Automatically generates a polished share page, no manual HTML needed.
- Includes sanitization step to avoid leaking secrets.
- Covers multiple share scenarios: project, conversation, file, report.
- Depends on an external CLI and network; requires installation and login.
- Generated page is static; no backend logic.
- For full-stack needs, this skill only does final publish; main `pinme` skill is required for backend/SQL.
- Does not share raw transcripts by default; requires explicit user approval.
How do you install this skill?
Install the entire PinMe collection via npx skills add glitternetwork/pinme; this skill (pinme-share) is then available.
How do you use this skill?
Ask the agent to 'share https://my-site.eth.limo as a static page' or similar. The skill will create the share page, upload it, and return the URL. Ensure the pinme CLI is installed (npm install -g pinme) and authenticated (pinme login).