photoshop-automator▌
abdul-karim-mia/photoshop-automator · updated Jun 10, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
This skill provides a high-performance bridge for automating Adobe Photoshop (vCS6 - 2026+) on Windows and macOS using the ExtendScript (JSX) engine via VBScript or AppleScript.
Photoshop Automator Skill (v1.2.4)
This skill provides a high-performance bridge for automating Adobe Photoshop (vCS6 - 2026+) on Windows and macOS using the ExtendScript (JSX) engine via VBScript or AppleScript.
Commands
- runScript: Executes raw ExtendScript (ES3) code. Use this for complex document manipulation.
- updateText: Target a specific text layer by name and update its contents instantly.
- createLayer: Create new art layers with custom opacity and blending modes.
- applyFilter: Apply a professional Gaussian Blur filter to the active layer.
- playAction: Play recorded Photoshop actions (.atn) by name and set.
- export: Save the active document as a high-quality PNG or JPEG.
🛠 AI Protocol
1. Technical Constraints (Strict)
- ES3 Syntax Only: Photoshop's ExtendScript engine uses ECMAScript 3 (ES3).
- ❌ DO NOT USE:
const,let, arrow functions() => {}, template literals`${}`, orMap/Set. - ✅ USE: Only
var, standardfunctiondeclarations, and string concatenation ('a' + b).
- ❌ DO NOT USE:
- Assume Active Document: Commands operate on the active document. If none is open, scripts will fail unless they call
app.documents.add().
2. Security & Side Effects
- Filesystem Access: The
runScriptcommand allows execution of arbitrary ExtendScript. This engine has direct access to the host filesystem. - Side Effects: Scripts can create, modify, or delete files on the local machine via the
FileandFolderobjects. - Verification: Always review dynamically generated scripts before execution to prevent unintended document or filesystem modifications.
3. Error Handling
- GUI Blocks: If Photoshop has a modal dialog open (e.g., Save As window, error popup), COM operations will hang or fail. Direct the user to close any open dialogs.
- Layer Presence: If
updateTextfails, ensure the layer name provided matches exactly (case-sensitive) with the layer in the PSD.
Setup
Ensure Adobe Photoshop is installed on the host system. The skill automatically uses the registered COM server.
Developed for the OpenClaw community by Abdul Karim Mia.
How to use photoshop-automator on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add photoshop-automator
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches photoshop-automator from GitHub repository abdul-karim-mia/photoshop-automator and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate photoshop-automator. Access the skill through slash commands (e.g., /photoshop-automator) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★72 reviews- ★★★★★Chaitanya Patil· Dec 28, 2024
Solid pick for teams standardizing on skills: photoshop-automator is focused, and the summary matches what you get after install.
- ★★★★★Amina Flores· Dec 28, 2024
We added photoshop-automator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Amina Ndlovu· Dec 16, 2024
photoshop-automator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Nikhil Mensah· Dec 12, 2024
Keeps context tight: photoshop-automator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Min Thompson· Dec 4, 2024
photoshop-automator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Amina Thompson· Dec 4, 2024
photoshop-automator reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kofi Gill· Nov 23, 2024
Useful defaults in photoshop-automator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Piyush G· Nov 19, 2024
We added photoshop-automator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Min Martinez· Nov 19, 2024
Registry listing for photoshop-automator matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Arya Johnson· Nov 15, 2024
photoshop-automator reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 72