This skill is responsible for outputting PSD, PNG, or other interchange files from a native layered project. It hands off to skills in the same package by name and can be used when installed on its own, without reading sibling directories. It calls the fixed maintenance version photocraft-cli and preserves the native editing project.
Inputs and deliverables
The inputs are the user-confirmed task, assets, project or object, output directory, and scope of modification; when an existing project is needed, verify the summary first. It returns the actual CLI results, the saved native project, the required derived outputs, and verification records. Successful installation, existence of the command directory, and completion of the creative task are reported separately.
First-time use and public entry point
Execution of the implementation is contained in the built-in photocraft-harness skill (installed bundled with the plugin; for standalone installation use npx skills add full-aigc-skills/photocraft-skills --skill photocraft-harness). Set HARNESS_DIR to the directory where that skill is actually loaded (absolute path); this skill's SKILL_DIR is only used to read its own examples/ and references/。
Locate the real directory of the current SKILL.md. Currently supports macOS arm64, Python 3.11+; the fixed CLI is installed to the user data directory. When an existing task authorization covers the necessary dependencies, execute this skill's installer directly and do not create a separate approval process.
Set SKILL_DIR to the directory containing this SKILL.md that is actually loaded by the host (absolute path). A user-level installation may be located at ~/.agents/skills/photocraft-cli-export, a project-level installation may be located at .agents/skills/photocraft-cli-export, and a plugin may be located in its skills/photocraft-cli-export or the host cache directory; use the actual loaded path as the standard, do not guess based on the current working directory, and do not search and then arbitrarily select a duplicate version. The skill directory and the CLI's user data installation directory are two independent locations.
: "${SKILL_DIR:?请先设置为本 SKILL.md 的实际所在目录}"
python3 -I -B "$HARNESS_DIR/scripts/bootstrap.py"
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- --version
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- commands --json
For CLI argv, after -- , the native subcommand must come first. Installation parameters go before the separator;--runtime-home can isolate the cache. Stop when locking the artifact digest fails, the installation is corrupted, or the platform is unsupported; do not modify PATH and do not perform floating upgrades. The native help entry point is help; the launcher's own --help only explains launch parameters.
Scenario operations
Verify this scenario's inputs, native project, target object, version, and output boundaries. According to the scenario guide , select the current command, save an independent checkpoint, and then execute; after completion, reopen the native project and inspect the actual output and non-target content.
Read params from commands --json --filter <关键词> ;run <工程> --cmd <id> --params <JSON> ... --out <新工程.pcraft>, each --params belongs to the preceding --cmd; serve/MCP can maintain a single session.
Reopening PSD checks the layer structure but does not claim full fidelity; flat output explicitly loses the editing structure and retains a loss report.
Native composition and source project revisions use the built-in photocraft-harness skill's scripts/workflow.py; read the workflow contract, and the templates are within this skill's examples. Modify only authorized objects; preserve the native project and dependent assets; for derived format loss, read the interchange report。
Verification and recovery
A nonzero command exit does not count as completion; it is necessary to inspect the actually saved project, exports, dimensions, and media decoding. A timeout result is marked unknown; check the original task/project first, and do not automatically replay edits. The existing native workflow supports Save As revision; refuse to overwrite when the corresponding project summary does not match.
On-demand reference and handoff
- Actual command evidence: Fixed-version observations, for routing and parameter reference only; real-time results take priority, and disabled items are not executed.
- Workflow Contract: Composite operations, native saving, dependency collection, and revision.
- Hand installation/diagnostics to photocraft-cli-setupwhen needed, and full task routing to photocraft-use; when skills are missing, use
npx skills add full-aigc-skills/photocraft-skills --skill <skill-name>. Do not load other skills via adjacent file paths.
This skill does not provide a fictitious login interface; local headless does not require a cloud account. The PhotoCraft bridge control-token is local application access control and differs from cloud login. Full GUI, cross-editor fidelity, and creative quality are stated according to actual evidence.
Full native command usage
The current skill includes its own complete directory of parameter descriptions and same-session entry points, and is not limited by the creative template whitelist. Read Complete Usage Guide, and consult as needed Command Reference; each instruction has skill routing, prerequisite observations, and acceptance status.
python3 -I -B "$HARNESS_DIR/scripts/commands.py" list --filter QUERY
python3 -I -B "$HARNESS_DIR/scripts/commands.py" describe COMMAND_ID
python3 -I -B "$HARNESS_DIR/scripts/commands.py" run "$SKILL_DIR/examples/commands-advanced.json" --output /absolute/new-command-result
Before executing a new entry point, check the real registry and current executable status, retain return value references and step-by-step receipts; semantic errors or timeouts must not be passed off as success. Directory coverage and direct native use do not mean that all commands, GUI, delivery, or Art orchestration have been accepted.
For the complete workflow command gateway, see Usage Instructions. For fixed CLI versions and artifact digests, the built-in photocraft-harness skill's scripts/runtime.lock.json shall prevail; skill package versions shall be based on the corresponding release tags. Independent installation re-verification and full command-by-command acceptance are recorded separately, and release does not replace acceptance.
For editable local adjustments and source rework, see Mask Adjustment Usage Instructions; paired plans are in this skill's examples, with source candidates and fixed installation evidence kept separate.
For GUI tasks, you may first use this skill's built-in Fixed Desktop Installation; installation, startup, and actual GUI editing are verified separately.
Complete attribution commands are listed by command family in Categorized Usage List, and each item can be viewed via this skill's commands.py describe for parameters; the general CLI list also retains all commands not assigned to specialized skills.
For business tasks, start from Scenario Operation Manual and execute according to input checks, template adaptation, native delivery, local rework, and result verification.
When installation fails, read First-Use Diagnosticsand use the receipt to locate the current skill's own setup entry point; handle installation failures and native invocation failures separately.
For product local filter, background blur, and output sharpening tasks, read Filter Scenarios, distinguish editable filters from baked pixels, and verify selections, layers, and non-target content.
Same-Target Execution Protection
Before invoking a public workflow, read this skill's Execution Registration and Interruption Handling. In competing or unknown states, do not delete registrations, automatically replay, or switch targets to bypass verification.
Before delivery, moving packages, or source project rework, verify all files and exchange identities according to the Delivery Integrity checklist; read-only checks do not require installing a runtime.
Scenario Contract and Routing
According to Scenario Contract Check inputs, targets and protection scope, recovery, and acceptance. For a complete task, select the shortest skill chain by name; when a known result is unclear, first check the original task and do not replay. Explicit intent can use the built-in photocraft-harness skill's scripts/route.py INTENT query entry point; this is a contract query and does not prove that host model dispatch has passed.
PSD delivery requires explicit required characteristics; observed loss/degradation and unknown required items will prevent success. When the user explicitly accepts, record it under the same source version and actual observation summary, and do not accept automatically; see this skill'sPSD exchange and acceptance gate。
When flat export requires explicit color/ICC/transparency requirements or preservation of the source of externally generated assets, read this skill's flat export and source contract。
For runtime/backend identity and capability drift issues, read this skill's capability snapshot and rejection contract。
Continuous tasks and instance reuse
When continuously checking, editing, saving, reopening, and reworking the same user task, use this skill's task-level session and the built-in photocraft-harness skill's scripts/task_session.py, maintaining the same foreground process and input handle. After failure/unknown, first check the original receipt and project, and do not start a replacement instance to replay.