This skill handles the use of adjustment layers or specified local color adjustments. It hands off by name with skills in the same package and can be used when installed alone; it does not read sibling directories. It invokes the pinned 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 modification scope; when an existing project is required, verify the summary first. Return the actual CLI results, the saved native project, the required derived outputs, and the verification records. Report installation success, the existence of the command directory, and completion of the creative task separately.
First use and public entry points
Execution implementation converges on 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 used only to read its own examples/ and references/。
Locate the real directory of the current SKILL.md. Currently supports macOS arm64, Python 3.11+; the pinned CLI is installed into the user data directory. When the existing task authorization covers the necessary dependencies, directly execute this skill's installer without creating a separate approval process.
Set SKILL_DIR to the directory (absolute path) where this SKILL.md actually loaded by the host is located. User-level installations may be located at ~/.agents/skills/photocraft-cli-adjustments, project-level ones may be located at .agents/skills/photocraft-cli-adjustments, and plugins may be located in their skills/photocraft-cli-adjustments 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
In the CLI argv, after -- , the native subcommand must come first. Installation arguments go before the separator;--runtime-home can isolate the cache. Stop when pinning 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 describes startup arguments.
Scenario operations
Verify this scenario's inputs, native project, target object, version, and output boundaries. According to 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.
From commands --json --filter <关键词> , read params;run <工程> --cmd <id> --params <JSON> ... --out <新工程.pcraft>, each --params belongs to the preceding --cmd; serve/MCP can maintain a single session.
Prefer adjustment layers to preserve the original image; mode, depth, and color management constraints are subject to the actual results.
Native composition and source project revisions use the built-in photocraft-harness skill's scripts/workflow.py; read workflow contract, with templates in this skill's examples. Modify only the authorized objects; preserve the native project and dependent assets; for derivative format loss, read exchange report。
Verification and recovery
A non-zero command exit does not count as completion; the actual saved project, exports, dimensions, and media decoding need to be inspected. Mark timeout results as unknown; check the original task/project first, and do not automatically replay edits. The existing native workflow supports Save As revisions; refuse to overwrite when the corresponding project summary does not match.
On-demand reference and handoff
- Actual command evidence: Fixed version observation, for routing and parameter reference only; real-time results take priority, disabled items are not executed.
- Workflow Contract: composite operations, native save, dependency collection and revision.
- When installation/diagnostics require it, hand off to photocraft-cli-setup, hand off full task routing to photocraft-use; when a skill is 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 fabricated login interface; local headless does not require a cloud account. The PhotoCraft bridge's control-token is local application access control, which is different from cloud login. Full GUI, cross-editor fidelity and creative quality are stated according to actual evidence.
Local modifications to the source project may declare protectedRegions, before release and delivery check pixels in non-target areas; see this skill'sprotected area contract. When no area is declared, do not automatically infer the protection scope.
Complete native command usage
The current skill includes complete directory parameter descriptions and same-session entry points, and is not restricted by the creative template allowlist. Read complete usage guide, query on demand command reference; each instruction has a skill route, prior observation 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; do not pass off semantic errors or timeouts as success. Directory coverage and direct native use do not mean that all instructions, GUI, delivery or Art orchestration have been accepted.
For the complete workflow command gateway, see usage instructions. For the fixed CLI version and artifact digest, refer to the built-in photocraft-harness skill's scripts/runtime.lock.json ; the skill package version is subject to the corresponding release tag. Independent installation re-verification and full command-by-command acceptance are recorded separately; 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, each item can be viewed through 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 by input check, 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.
For size, color mode or automatic pixel adjustment tasks, read this skill's built-in image transformation guide, first checking layer retention requirements and conversion impact.
Same-target execution protection
Before invoking a public workflow, read this skill's execution registration and interruption handling. Competing or unknown states must not delete registrations, automatically replay, or switch targets to bypass verification.
Before reworking a delivery, mobile package, or source project, follow Delivery Integrity to verify all files and the exchange identity in the checklist; read-only inspection requires no runtime installation.
Scenario Contract and Routing
Follow Scenario Contract to verify the inputs, target and protection scope, recovery, and acceptance. For a complete task, select the shortest skill chain by name; when known results are unclear, first verify the original task and do not replay. For explicit intent, you may 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 necessary features; observed loss/degradation and unknown necessary items will block success. When the user explicitly accepts, record it under the same source version and actual observation summary; do not accept automatically; see this skill'sPSD Exchange and Acceptance Gate。
When flat export requires explicit color/ICC/transparency requirements or retention of the source of externally generated assets, read this skill's Flat Export and Provenance Contract。
For runtime/backend identity and capability drift issues, read this skill's Capability Snapshot and Refusal Contract。
Continuous Tasks and Instance Reuse
When continuously inspecting, 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, keeping the same foreground process and input handles. After failure/unknown, first verify the original receipt and project; do not start a substitute instance for replay.