psd-automator-skill-command_skill

This skill dispatches PSD automation tasks via a command entry, reusing the /psd orchestration pipeline for consistent results.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill psd-automator-skill-command

  • _meta.json305 B
  • SKILL.md999 B

Overview

This skill dispatches PSD automation tasks through a skill-command entry while reusing the same /psd orchestrator. It provides a drop-in command equivalent to the existing /psd endpoint so workflows and metrics remain consistent. It requires the psd-automator core to run and preserves DINGTALK image marker behavior.

How this skill works

The command accepts an agentId and a task description or path to a task JSON, then routes that job into the established /psd orchestration pipeline. Optional flags support dry-run verification and custom index paths for asset lookup. Execution shares the same usage statistics store with entrypoint set to skill_command, ensuring unified telemetry and reporting.

When to use it

  • You want to trigger PSD automation from a skill command instead of the chat slash command.
  • You need to reuse the existing /psd orchestration without changing behavior or templates.
  • You need to run automated edits, exports, or conversions on PSD files programmatically.
  • You want consistent DINGTALK image marker handling across interfaces.
  • You need to track skill usage under the skill_command entrypoint.

Best practices

  • Ensure psd-automator core is installed and configured before invoking the command.
  • Provide either a clear JSON task path or a concise natural language task description to reduce parsing errors.
  • Use --dry-run to validate actions and paths before committing file changes.
  • Specify --index when you rely on a custom asset index for faster lookup.
  • Keep task descriptions focused: name target file, desired edits, output format, and destination.

Example use cases

  • Change a name on a PSD team badge and export a PNG to a desktop folder via an agent ID.
  • Run a batch conversion of layered PSDs to flattened web-optimized PNGs using an index of assets.
  • Validate a sequence of edits with --dry-run to confirm automations before saving changes.
  • Trigger a localized style update across multiple PSD templates by referencing a JSON task manifest.
  • Integrate PSD automation into larger workflows by invoking the command from other skill-driven steps.

FAQ

It accepts a task JSON path or a concise natural language task description; task JSON offers precise, repeatable instructions.

Does this change the behavior of the existing /psd endpoint?

No. It reuses the same orchestration pipeline and preserves behavior, including DINGTALK image markers and telemetry collection.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational