pinme-share

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`.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear sequenced workflow and a pre-upload verification checklist, all well-organized in a single self-contained file. Its main weakness is mild verbosity where generic web best practices are restated.

Suggestions

Trim the HTML Guidelines to skill-specific guidance only (first-viewport link, restrained design for technical handoffs, escape user text, short <pre><code>); drop general reminders about responsive/accessible/semantic markup that Claude already knows.

Consider compressing the three Share Page Content sub-lists into a compact shared checklist with per-type callouts, reducing repetition between the project, conversation, and file share sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but the HTML Guidelines section restates general web knowledge Claude already has (responsive layout, accessible contrast, semantic sections, descriptive link text) and the Share Page Content lists run long, so it could be tightened.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands (`pinme upload share/<slug>`, `pinme --version`, `pinme login`, `pinme set-appkey <AppKey>`), concrete paths, an explicit URL-preference ordering, and a concrete sanitization/do-not-upload list.	3 / 3
Workflow Clarity	A clear 5-step Core Workflow (identify, create, sanitize, upload, return URL) is paired with a PinMe Upload Checklist that verifies version and auth before upload, plus a final-response caveat for skipped uploads — an explicit pre-flight verification step and checklist.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single SKILL.md is organized into clear, well-signaled sections (When to Use, Core Workflow, Share Page Content, HTML Guidelines, Upload Checklist, Final Response) with no nested or broken references.	3 / 3
	Total	11 / 12 Passed

Description

92%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit triggers, concrete actions, and broad natural keyword coverage. Its only weakness is an unaddressed overlap with the main `pinme` skill, which is resolved only in the body rather than in the description itself.

Suggestions

Add a brief disambiguator in the description, e.g. 'Use for packaging a finished static result for upload, not for building apps with backend/auth needs (use the main pinme skill for those).'

Trim the trailing 'any 分享/发布/上传分享页 request' clause, which mixes languages and reads as jargon rather than a natural user trigger.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ("share, publish, or upload", "generating a static HTML share page") and enumerates specific artifact types (project link, deployed full-stack app, Codex conversation summary, report, file, demo), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It explicitly states what the skill does (generate/upload a static share page via PinMe) and includes an explicit 'Use this skill when...' trigger clause answering when to use it, satisfying both what and when.	3 / 3
Trigger Term Quality	It uses natural terms users would say ("share", "publish", "upload", "demo", "report", "static HTML share page") with good coverage, matching the strong trigger-term anchor; the appended Chinese 分享/发布/上传 is a minor oddity but does not reduce coverage.	3 / 3
Distinctiveness Conflict Risk	The PinMe-static-share niche is specific, but the description does not disambiguate from the sibling main `pinme` skill (which also performs uploads); the boundary is only clarified in the body, so overlap with a similar skill remains.	2 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: glitternetwork/pinme
Path: skills/pinme-share/SKILL.md
Commit: 7822b05

Reviewed: 25 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.