This skill is responsible for executing an existing ArtCraft plan, verifying input versions and concurrent writes. It hands off with skills in the same package by name, works when installed standalone, and does not read sibling directories. It uses this project's local orchestration CLI; upstream ArtCraft is a Tauri application, and it does not install or impersonate an official CLI of the same name.
Execution implementation is consolidated in the built-in artcraft-harness skill (installed bundled with the plugin; for standalone installation use npx skills add full-aigc-skills/artcraft-skills --skill artcraft-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/, and script execution paths always use $HARNESS_DIR/scripts/。
Inputs and deliverables
Inputs are the user-confirmed task, assets, project or object, output directory and modification scope; when an existing project is needed, verify the summary first. Return the actual CLI results, the saved native project, the required derived outputs and verification records. Report installation success, command directory existence and creative task completion separately.
First use and public entry point
Locate the real directory of the current SKILL.md. Currently supports macOS arm64, Python 3.11+; the base entry point installs a pinned Node and orchestration package; workflow.py installs the required domain skill sources and native CLI according to the task graph, without requiring a global Node. When an existing task authorization covers the necessary dependencies, execute this skill's installer directly; do not create a separate approval process.
Set SKILL_DIR to the directory containing this SKILL.md actually loaded by the host (absolute path). User-level installation may be located at ~/.agents/skills/artcraft-cli-execute, project-level may be located at .agents/skills/artcraft-cli-execute, and plugins may be located in their skills/artcraft-cli-execute or host cache directory; use the actual loaded path, 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" --runtime-only
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- --version
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- --help
CLI argv is after -- , and the native subcommand must come first. Installation parameters go before the separator;--runtime-home can isolate the cache. Stop when pinned artifact digest 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 launch parameters.
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 check the actual outputs and non-target content.
This project's --help defines run/status/cancel/package/verify-package; semantic plans go through workflow.py, and upstream Tauri's account/provider methods cannot be used as orchestration CLI commands.
Use workflow.py to compile the real registry; the model must not choose the shell, interpreter or sub-executor paths.
Native composition and source project revisions use the artcraft-harness skill's scripts/workflow.py; read the workflow contract, and templates are in this skill's examples. Only modify authorized objects, keep the native project and dependent assets, and for derived format loss read the exchange report。
Verification and recovery
A non-zero command exit does not count as completion; the actual saved project, export, dimensions, and media decoding need to be checked. Mark timeout results as unknown; first inspect the original task/project, and do not automatically replay edits. Perform recovery and packaging according to this skill's references/recovery.md and references/project-package.md respectively; review_ready only indicates technical readiness.
On-demand references and handoff
- Actual command evidence: fixed-version observations, used only as routing and parameter references; real-time results take precedence, and disabled items are not executed.
- Workflow contract: combined operations, native saving, dependency collection, and revisions.
- When installation/diagnostics are needed, hand off to artcraft-cli-setup; for full task routing, hand off to artcraft-use; when a skill is missing, use
npx skills add full-aigc-skills/artcraft-skills --skill <skill-name>. Do not load other skills via adjacent file paths.
This skill does not provide a fictional login interface; local headless does not require a cloud account. Full GUI, cross-editor fidelity, and creative quality are stated according to actual evidence.
When a finished video needs to be verified through the existing Video Factory, read this skill's public verification handoff. This adaptation preserves NOT_RUN and does not replace creative review or the native project.
Dynamic transparent sequence handoff
When a mixed task requires transparent animation, full-frame handoff, or downstream updates after a logo replacement, use this skill'sdynamic sequence guideand examples/dynamic-brand-campaign.json. Verify all frames, time base, native references, and local rework according to actual receipts; do not substitute the first frame or ordinary JSON for the sequence.
When the result is unknown after saving, verify according to this skill's references/recovery.md the failure.json, the original temporary project, and the stop evidence; do not replay the same task, and a failed temporary save is not a successful delivery.
Full domain command handoff
When native operations beyond the templates are needed, read this skill'sfull domain command component, use the included domain_commands.py to query 2646 commands, actual MCP parameters, and hand off the selected domain. Each skill includes creation/rework examples for the four domains; do not replay unknown, and component receipts do not replace DAG native delivery and acceptance.
Native gradients, multiple fills, and source-project color-change rework: use the current skill's Vector appearance guide。
Native parenting, opacity expressions, and source-project rework: use the current skill's Effect expression guide。
For Photo native adjustment layers, selection masks, and trusted-source rework, see local adjustment guide。
When domain GUI commands need to be launched independently, see own desktop handoff。
For mixed tasks, refer to the business scenario manual, first confirm dependencies and input versions, then execute subprojects, local rework, and delivery verification.
When installation fails, read first-use diagnostics, and locate the current skill's own setup entry according to the receipt; handle installation failures and native invocation failures separately.
For real voice recognition and mixed subtitle tasks, please read this skill's Mixed ASR guide / Mixed ASR guide, and execute according to fixed domain dispatch and the persistent model directory; for planning, rework, and acceptance, retain dependencies, the native project, and execution evidence respectively.
For task identity and rejection details, read according to task receipt description ; node summaries do not replace actual execution receipts.
Before reworking mixed posters, covers, and source projects, read Photo complete delivery, distinguishing host-independent plugins from Art-internal fixed dependencies.
For cross-artifact observation of fixed brand and subject references, see this skill's consistency review contract; source candidates and released fixed versions are reported separately for acceptance.
Runtime upgrades and legacy ledgers
When encountering runtime_upgrade_busy , retain the old runtime, original project, and ledger; do not delete leases or forcibly modify state. First complete or reliably stop the task with the old version, then migrate according to the new version; the old budget marker of read-only status indicates historically untracked. See this skill'supgrade guide。
For validation and mode boundaries of native command execution, see command contract boundaries。
For classification, parameter differences, and rejection boundaries of mode catalog candidates, seemode catalog usage; Vector desktop/bridge duplicate commands have not yet completed execution qualification and cannot fall back according to the headless catalog.