Product Lens
affaan-m/ECC
Validate the why before building through four product diagnostics — a YC-style product diagnostic that produces PRODUCT-BRIEF.md with a go/no-go recommendation, a founder review scoring…
Create and audit Printify products with manifest-driven image uploads, personalization checks, and local proofing.
$ npx skills add mvanhorn/printing-press-library --skill pp-printify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-printify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-printify .claude/skills/pp-printify && rm -rf skills-srcUse ~/.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/
Install the "pp-printify" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-printify into .claude/skills/pp-printify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-printify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-printifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mvanhorn/printing-press-library --skill pp-printify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-printify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-printify .agents/skills/pp-printify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-printify" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-printify into .agents/skills/pp-printify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-printify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-printify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-printify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-printify .cursor/skills/pp-printify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pp-printify" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-printify into .cursor/skills/pp-printify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-printify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mvanhorn/printing-press-library.git --path cli-skills/pp-printify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mvanhorn/printing-press-library --skill pp-printify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-printify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-printify .gemini/skills/pp-printify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pp-printify" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-printify into .gemini/skills/pp-printify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-printify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mvanhorn/printing-press-library pp-printifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mvanhorn/printing-press-library --skill pp-printify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-printify .github/skills/pp-printify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pp-printify" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-printify into .github/skills/pp-printify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-printify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-printify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-printify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-printify .opencode/skills/pp-printify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pp-printify" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-printify into .opencode/skills/pp-printify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-printify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
pp-printifyCreate and audit Printify products with manifest-driven image uploads, personalization checks, and local proofing.
Pp Printify is an agent skill from mvanhorn/printing-press-library. Create and audit Printify products with manifest-driven image uploads, personalization checks, and local proofing. Trigger phrases: create Printify products, upload Printify artwork, audit Printify personalization, check Printify product drift, run Printify, use Printify.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 0fdcc7a. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
goclaudenpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
PRINTIFY_API_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Printify loads about 3.7k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 1,373 words of instructions outside code blocks.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
NTIFY_API_TOKEN` in your environment or `.env`; do not pass the token as a command argument.allowed-tools: Read, BashAutomated 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.
The full file from mvanhorn/printing-press-library at commit 0fdcc7a, republished under its Apache-2.0 licence (© mvanhorn). 1,373 words, ~3,696 tokens.
.claude/skills/pp-printify/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/commerce/printify/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
This skill drives the printify-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install printify --cli-onlyprintify-pp-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer):
go install github.com/mvanhorn/printing-press-library/library/commerce/printify/cmd/printify-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
Use this CLI for Printify product automation that needs more than raw endpoint calls: image uploads, manifest-driven drafts, personalization field checks, placement proofing, and operational audits. It is especially useful for agents building or verifying POD product batches from local artwork and CSV inputs.
These capabilities aren't available in any other tool for this API.
personalization-audit — Audit a product for documented personalization placeholder fields, missing text/image setup, and unsupported browser-only gaps.
Use this before publishing a personalized product or before handing a manifest to another agent.
printify-pp-cli personalization-audit --product-file ./examples/sample-product.json --agentplacement-matrix — Show variant, print-area, placeholder, uploaded image, x/y/scale/angle, and missing-placement rows for a product.
Use this when an agent must prove artwork placement is consistent across variants.
printify-pp-cli placement-matrix --product-file ./examples/sample-product.json --uploads-file ./examples/sample-uploads.json --agentproduct-drift — Compare an intended product manifest against the current Printify product payload after create or update.
Use this after automation creates a product and before trusting the resulting listing.
printify-pp-cli product-drift --product-file ./examples/current-product.json --manifest ./examples/sample-product.json --agentcatalog-margin-matrix — Join catalog variants and shipping data to estimate per-variant cost and margin at a target retail price.
Use this before creating a batch when product economics matter more than raw catalog browsing.
printify-pp-cli catalog-margin-matrix --variants-file ./examples/sample-variants.json --shipping-file ./examples/sample-shipping.json --target-price 24.99 --agentpersonalization-batch — Expand a reusable product manifest and CSV rows into per-product manifests using documented image and text placeholder fields.
Use this when an agent needs repeatable personalized product drafts before making API writes.
printify-pp-cli personalization-batch --template ./examples/template-product.json --csv ./examples/personalization.csv --out ./examples/generated-manifests --agentasset-reuse — List uploaded images, where each is used, unused uploads, and products sharing the same artwork.
Use this to clean upload libraries or verify that a product batch reuses the expected artwork.
printify-pp-cli asset-reuse --products-file ./examples/sample-products.json --uploads-file ./examples/sample-uploads.json --agentfulfillment-risk — Flag open orders tied to risky product, variant, publish, or shipment states.
Use this when an agent needs to find fulfillment problems before customer-service work starts.
printify-pp-cli fulfillment-risk --orders-file ./examples/sample-orders.json --products-file ./examples/sample-products.json --agentcatalog — Browse the Printify catalog including blueprints, print providers, product variants, and shipping information. Explore available products and their customization options.
printify-pp-cli catalog retrieve-alist-of-all-print-providers-that-fulfill-orders-for-aspecific-blueprint — Retrieve a list of all print providers that fulfill orders for a specific blueprintprintify-pp-cli catalog retrieve-alist-of-available-print-providers — Retrieves the list of blueprints in the catalog to explore fromprintify-pp-cli catalog retrieve-alist-of-variants-of-ablueprint-from-aspecific-print-provider — Retrieves the list of of variants options for the Print Provider and Blueprint.printify-pp-cli catalog retrieve-aspecific-blueprint — Retrieves the list of blueprints in the catalog to explore fromprintify-pp-cli catalog retrieve-aspecific-print-provider — Retrieves the list of blueprints in the catalog to explore fromprintify-pp-cli catalog retrieve-available-shipping-list-information — Retrieves the list of print providers avilable for the Blueprintprintify-pp-cli catalog retrieve-economy-shipping-method-information — Retrieves the list of print providers available for the Blueprintprintify-pp-cli catalog retrieve-express-shipping-method-information — Retrieves the list of print providers available for the Blueprintprintify-pp-cli catalog retrieve-priority-shipping-method-information — Retrieves the list of print providers available for the Blueprintprintify-pp-cli catalog retrieve-shipping-information — Retrieves the list of print providers avilable for the Blueprintprintify-pp-cli catalog retrieve-specific-shipping-method-information — Retrieves the list of print providers avilable for the Blueprintprintify-pp-cli catalog retrieves-list-of-blueprints-in-the — Retrieves the list of blueprints in the catalog to explore fromshops — Manage Printify shops and shop connections. Retrieve shop information and disconnect shops from your account.
shops-json — Manage shops json
printify-pp-cli shops-json — This will return the list of available merchant shops (IDs and titles)uploads — Upload and manage images and assets. Upload images from URLs or base64-encoded content, retrieve upload information, and archive uploaded images.
printify-pp-cli uploads an-image — Upload an imageprintify-pp-cli uploads retrieve-an-uploaded-image-by-id — Retrieve an uploaded image by iduploads-json — Manage uploads json
printify-pp-cli uploads-json — Retrieve a list of uploaded imagesWhen you know what you want to do but not which command does it, ask the CLI directly:
printify-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
printify-pp-cli shops-json --agent --select id,titleUse this first so follow-up product and order commands target the right shop without dumping the full shop payload.
printify-pp-cli personalization-batch --template ./examples/template-product.json --csv ./examples/personalization.csv --out ./examples/generated-manifests --agentTurn a reusable template and row data into deterministic product manifests before any API writes.
printify-pp-cli placement-matrix --product-file ./examples/sample-product.json --uploads-file ./examples/sample-uploads.json --agent --select variant_id,print_area,image_id,x,y,scale,angleInspect only the placement columns an agent needs before publishing.
printify-pp-cli product-drift --product-file ./examples/current-product.json --manifest ./examples/sample-product.json --agentConfirm the remote product still matches the manifest the automation intended.
printify-pp-cli fulfillment-risk --orders-file ./examples/sample-orders.json --products-file ./examples/sample-products.json --agentJoin orders, variants, product state, and shipment state into a single operational risk view.
Printify uses a personal access token as a bearer token. Set PRINTIFY_API_TOKEN in your environment or .env; do not pass the token as a command argument.
Run printify-pp-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
printify-pp-cli catalog retrieve-alist-of-all-print-providers-that-fulfill-orders-for-aspecific-blueprint mock-value --agent --select id,name,statusPreviewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Explicit retries — use --idempotent only when an already-existing create should count as success, and --ignore-missing only when a missing delete target should count as success
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.
When you (or the agent) notice something off about this CLI, record it:
printify-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
printify-pp-cli feedback --stdin < notes.txt
printify-pp-cli feedback list --json --limit 10Entries are stored locally at ~/.local/share/printify-pp-cli/feedback.jsonl. They are never POSTed unless PRINTIFY_FEEDBACK_ENDPOINT is set AND either --send is passed or PRINTIFY_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
printify-pp-cli profile save briefing --json
printify-pp-cli --profile briefing catalog retrieve-alist-of-all-print-providers-that-fulfill-orders-for-aspecific-blueprint mock-value
printify-pp-cli profile list --json
printify-pp-cli profile show briefing
printify-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 4 | Authentication required |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show printify-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/other/printify/cmd/printify-pp-mcp@latestclaude mcp add printify-pp-mcp -- printify-pp-mcpclaude mcp listwhich printify-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:printify-pp-cli <command> [subcommand] [args] --agentprintify-pp-cli <command> --help.© mvanhorn, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in cli-skills/pp-printify of mvanhorn/printing-press-library.
Open the folder on GitHubat commit 0fdcc7a
Pp Printify 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pp Printify this skillmvanhorn/printing-press-library | 2.1k | — | ~3.7k | Automated safety check: Notes | Apache-2.0 | |
| Product Lensaffaan-m/ECC | 275k | 2 repos | ~841 | Automated safety check: Pass | MIT | |
| Productthedaviddias/Front-End-Checklist | 74k | — | ~592 | Automated safety check: Pass | MIT | |
| Upload R2remotion-dev/remotion | 62k | — | ~535 | Automated safety check: Notes | Custom licence | |
| Product Analyticsalirezarezvani/claude-skills | 28k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Product Strategyphuryn/pm-skills | 27k | — | ~1.2k | Automated safety check: Pass | MIT |
affaan-m/ECC
Validate the why before building through four product diagnostics — a YC-style product diagnostic that produces PRODUCT-BRIEF.md with a go/no-go recommendation, a founder review scoring…
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing e-commerce product pages or implementing structured data for a shop.
remotion-dev/remotion
Upload large Remotion repository assets to the Cloudflare R2 bucket behind remotion.media and replace local public/ assets with hosted URLs.
alirezarezvani/claude-skills
A skill your agent uses when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across product stages.
phuryn/pm-skills
Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.
lobehub/lobehub
Frames new surfaces, redesigns and vague product requests by grounding the business model and the user's task before any layout, in discover, frame or materialize modes.
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Create and audit Printify products with manifest-driven image uploads, personalization checks, and local proofing. Pp Printify is an agent skill from mvanhorn/printing-press-library. Create and audit Printify products with manifest-driven image uploads, personalization checks, and local proofing.
Pp Printify fits situations like: phrases: create Printify products; upload Printify artwork; audit Printify personalization; check Printify product drift.
Run `npx skills add mvanhorn/printing-press-library --skill pp-printify -a claude-code`. Or copy the skill folder (cli-skills/pp-printify in mvanhorn/printing-press-library) into .claude/skills/pp-printify in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-printify -a codex`. Or copy the skill folder (cli-skills/pp-printify in mvanhorn/printing-press-library) into .agents/skills/pp-printify in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvanhorn/printing-press-library --skill pp-printify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-printify, .gemini/skills/pp-printify, .github/skills/pp-printify and .opencode/skills/pp-printify in your project.
Going by SKILL.md and its folder, Pp Printify needs the command-line tools its instructions call (go, claude and npx) and credentials named PRINTIFY_API_TOKEN. Our summary lists: Node.js; A credential in PRINTIFY_API_TOKEN. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Pp Printify is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pp Printify: Product Lens (affaan-m/ECC, 275k stars), Product (thedaviddias/Front-End-Checklist, 74k stars), Upload R2 (remotion-dev/remotion, 62k stars) and Product Analytics (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,053 GitHub stars. The repository holds 505 skills in this directory. The repository was last updated on October 7, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.