← Back to Skills Marketplace
172
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install pinterest-browser-publisher
Description
Automate Pinterest pin publishing via browser automation (Playwright). No API key needed. Supports jp.pinterest.com, single pins, carousels, and batch publis...
Usage Guidance
This skill appears to implement browser automation for Pinterest and needs Playwright and Chromium — that's expected. Before installing or running it:
- Inspect and remove or update hardcoded absolute paths (e.g., /Users/dhr/...) in scripts; they will fail or act on unintended files.
- Be aware it saves session cookies to ~/.config/pinterest/cookies.json; treat that file as highly sensitive (contains auth/session cookies). Do not commit it to git or leave it in shared environments.
- Consider removing or modifying lines that print cookie values to stdout (force-login.js logs cookie names and value prefixes) to avoid leaking tokens to logs.
- Verify Node version (package-lock/playwright indicate Node >=18) and the registry source in package-lock.json (npmmirror) before npm installing; prefer the official npm registry unless you intentionally use a mirror you trust.
- Run the skill in an isolated account/container if possible the first time, and monitor network/console activity. If you rely on this in production, fork the repository, sanitize developer-specific paths, and remove any unnecessary logging of secrets.
These issues look like careless engineering rather than deliberate malign behavior, but they increase your exposure to accidental token leakage and runtime surprises, so proceed cautiously.
Capability Analysis
Type: OpenClaw Skill
Name: pinterest-browser-publisher
Version: 1.0.2
The skill bundle provides a comprehensive set of Playwright-based scripts for automating Pinterest pin publishing, specifically targeting the Japanese market. It includes mechanisms for manual login and local cookie persistence in `~/.config/pinterest/cookies.json` to maintain sessions without an official API. While several scripts (e.g., `scripts/auto-publish-all.js` and `scripts/publish-fix.js`) contain hardcoded absolute file paths from a specific developer environment, these are functional bugs rather than malicious indicators. The code simulates human-like interactions (Bezier curve mouse movements and random delays) to avoid bot detection, and all network activity is restricted to official Pinterest domains.
Capability Assessment
Purpose & Capability
The name/description (Playwright-based Pinterest publisher) match the included scripts: they automate browser login, persist cookies, upload images, fill title/description, and click publish. However some files contain developer-specific absolute paths (/Users/dhr/...) for images and screenshots, and these are unrelated to the skill's stated configuration model (which expects user-provided images). Hardcoded paths are likely leftover test artifacts and are inconsistent with a general-purpose skill.
Instruction Scope
The SKILL.md instructs installing Playwright and saving cookies to ~/.config/pinterest/cookies.json which is expected. But some scripts print cookie contents (force-login.js logs cookie names and first 50 chars) — exposing authentication tokens to stdout — and several scripts write screenshots/saves to explicit /Users/dhr/... paths (not only HOME-based paths), which is unexpected and may fail or leak information. Scripts also try multiple site URLs and include wide timeouts and manual-fallback flows; these are reasonable for brittle UI automation but give the code broad discretion (file reads/writes, screenshots, long waits).
Install Mechanism
There is no platform install spec in registry metadata (instruction-only), but SKILL.md and package.json require installing Playwright and Chromium. Playwright will download browser binaries during install/runtime; that is normal but significant. The package-lock.json shows packages resolved from registry.npmmirror.com (a mirror) and a playwright-core that requires Node >=18, while SKILL.md says Node 16+. These mismatches are sloppy and could cause runtime failures or pull packages from a non-default registry — worth verifying before installation.
Credentials
The skill declares no required environment variables (good), and uses only HOME/USERPROFILE to read/write ~/.config/pinterest/cookies.json which is appropriate. However the code also references absolute paths tied to a specific developer account and prints cookie values (sensitive session tokens) to console. While cookies must be stored for session reuse, printing token prefixes and leaving cookie files on disk increases risk if you run this in a shared environment. There are no external secrets requested, but the handling of session cookies is the primary sensitive surface and is currently treated sloppily.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It stores cookies and config under the user's home config directory (~/.config/pinterest) which is expected for session persistence. It does not modify other skills or global agent settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install pinterest-browser-publisher - After installation, invoke the skill by name or use
/pinterest-browser-publisher - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Updated script usage examples in documentation for more clarity and accuracy.
- Removed references to outdated scripts and streamlined script descriptions.
- Bumped version information in metadata and documentation.
- No code changes; documentation and metadata updates only.
v1.0.1
- Expanded support for jp.pinterest.com, including Japanese copywriting and locale-specific scripts.
- Added multiple new publishing scripts (e.g., auto-publish-all, force-login, publish-jp-direct, publish-fix, publish-remaining) for flexible pin publishing workflows.
- Enhanced documentation with usage examples, best practices, image requirements, troubleshooting, and Japanese localization.
- Updated configuration and session handling details, emphasizing cookie persistence.
- Added safety features: human-like interactions, random delays, and rate limiting for account protection.
v1.0.0
- Initial release: Automate Pinterest pin publishing using browser automation (Playwright) without the need for an API key.
- Supports publishing single pins, carousels, and batch uploads.
- Includes tools for board management (listing and creation) and account status checking.
- Requires a one-time manual login using a browser; session persists with saved cookies.
- Built-in safety: rate limits, random delays, and human-like interactions to reduce risk of detection.
Metadata
Frequently Asked Questions
What is Pinterest Browser Publisher?
Automate Pinterest pin publishing via browser automation (Playwright). No API key needed. Supports jp.pinterest.com, single pins, carousels, and batch publis... It is an AI Agent Skill for Claude Code / OpenClaw, with 172 downloads so far.
How do I install Pinterest Browser Publisher?
Run "/install pinterest-browser-publisher" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Pinterest Browser Publisher free?
Yes, Pinterest Browser Publisher is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Pinterest Browser Publisher support?
Pinterest Browser Publisher is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Pinterest Browser Publisher?
It is built and maintained by luoboask (@luoboask); the current version is v1.0.2.
More Skills