This skill is responsible for creating, opening, and saving pcraft, and for checking dimensions, depth, and color mode. It hands off to skills in the same package by name, can be used when installed alone, and does not read sibling directories. It invokes the fixed maintenance version of photocraft-cli and preserves native editing projects.
Inputs and deliverables
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. Return the actual CLI results, the saved native project, any required derived outputs, and verification records. Report installation success, command directory existence, and creative task completion separately.
First use and public entry points
Execution implementation converges within 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 that skill's actual load directory (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 installs to the user data directory. When existing task authorization covers the necessary dependencies, execute this skill's installer directly without creating a separate approval process.
Set SKILL_DIR to the directory (absolute path) of the SKILL.md actually loaded by the host. User-level installations may be located in ~/.agents/skills/photocraft-cli-project, project-level ones may be located in .agents/skills/photocraft-cli-project, and plugins may be located in their skills/photocraft-cli-project or the host cache directory; the actual load path prevails, do not guess based on the current working directory, and do not search and then arbitrarily pick 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 locked artifact verification 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 parameters.
Scenario operations
Verify this scenario's inputs, native project, target object, version, and output boundaries. Follow the scenario guide to select the current command, save an independent checkpoint, then execute; after completion, reopen the native project and check 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.
The native project is the layered source of truth; after saving as, reopen with info; flat conversion does not replace the project.
Native composition and source project revisions use the built-in photocraft-harness skill's scripts/workflow.py; read the workflow contract, templates are within this skill's examples. Modify only authorized objects, preserve the native project and dependent assets, for derived format losses read the 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 timed-out results as unknown, check the original task/project first, and do not automatically replay edits. Existing native workflows support save-as revisions; refuse to overwrite when the corresponding project summary does not match.
On-demand references and handoff
- Actual command evidence: Fixed-version observation, 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 revisions.
- When installation/diagnostics are needed, hand off to photocraft-cli-setup, complete task routing is handed off to photocraft-use; when skills are missing, use
npx skills add full-aigc-skills/photocraft-skills --skill <skill-name>. Do not load other skills through adjacent file paths.
This skill does not provide a fictional 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.
Full Native Command Usage
The current skill includes parameter descriptions for the full catalog 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 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 actual 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. Catalog 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's version and artifact summary, 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, and release is not a substitute for 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 can 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 Checklist, and each item can be viewed through this skill's commands.py describe for parameters; the general CLI checklist also retains all commands not assigned to specialized skills.
Business tasks start from Scenario Operation Manual , and are executed according to input checks, template adaptation, native delivery, local rework, and result verification.
When installation fails, read First-Use Diagnostics, and locate the current skill's own setup entry point according to the receipt; installation failure and native call failure are handled 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, and first check layer preservation requirements and transformation impact.
Same-Target Execution Protection
Before invoking a public workflow, read this skill's Execution Registration and Interruption Handling. In cases of contention or unknown status, 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 an installed runtime.
Scenario Contract and Routing
According to scenario contract , verify input, goals and protection scope, recovery, and acceptance. For a complete task, select the shortest skill chain by name; when the known result is unknown, 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; this is a contract query and does not prove that host model dispatch has passed.
PSD delivery requires clearly defined 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 clear 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 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 with the built-in photocraft-harness skill's scripts/task_session.py, keeping the same foreground process and input handle. After failure/unknown, first verify the original receipt and project, and do not start a replacement instance to replay.