This skill is responsible for querying actual command parameters and capabilities, and invoking the public CLI, MCP, and diagnostics. It hands off to skills in the same package by name, can be used when installed alone, and does not read sibling directories. Use this project's local orchestration CLI; upstream ArtCraft is a Tauri application, and no official CLI of the same name is installed or impersonated.
Execution implementation converges 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, materials, project or object, output directory, and modification scope; when an existing project is needed, verify the summary first. Return actual CLI results, the saved native project, required derived outputs, and verification records. Report installation success, command directory existence, and creation task completion separately.
First Use and Public Entry Point
Locate the real directory of the current SKILL.md. Currently supports macOS arm64 and 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 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) where this SKILL.md actually loaded by the host resides. User-level installations may be located at ~/.agents/skills/artcraft-cli, project-level ones may be located at .agents/skills/artcraft-cli, and plugins may be located in their skills/artcraft-cli or the host cache directory; go by the actual loaded path, 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" --runtime-only
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- --version
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- --help
CLI argv comes after -- , and the native subcommand must come first. Installation parameters go before the separator;--runtime-home can isolate the cache. Stop when locking artifact digests 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
First query the current version and command directory; record read-only and edit invocations separately. After reading the current project state and command enabled/params, construct argv; consecutive steps that need to create objects must be executed in the same session, and returned IDs must not be guessed.
This project's --help defines run/status/cancel/package/verify-package; semantic plans go through workflow.py, and upstream Tauri's account/vendor methods must not be treated as orchestration CLI commands.
Native composition and source project revision 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; native projects and dependency materials are retained, 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 inspected. Timeout results are marked unknown; check the original task/project first, and do not automatically replay edits. Recovery and packaging are performed according to this skill's references/recovery.md and references/project-package.md respectively; review_ready only indicates technical readiness.
On-demand reference and handoff
- Actual command evidence: Fixed-version observations, provided solely as routing and parameter reference; live results take precedence, and disabled items are not executed.
- Workflow contract: Composite operations, native saving, dependency collection, and revision.
- 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 through adjacent file paths.
This skill does not provide a fabricated login interface; local headless does not require a cloud account. Full GUI, cross-editor fidelity, and creative quality are stated based on actual evidence.
When verification of a finished video is needed through the existing Video Factory, read this skill's public verification handoff. This adaptation preserves NOT_RUN and does not substitute for creative review or the native project.
When the result is unknown after saving, verify according to this skill's references/recovery.md verify failure.json, the original staged project, and the stop evidence; do not replay the same task, and a failed staging is not a successful delivery.
Full domain command handoff
When native operations beyond the template are needed, read this skill'sfull domain command component, use the bundled domain_commands.py to query 2646 commands, actual MCP parameters, and hand off the selected domain. Each skill includes examples for creation/rework in the four domains; unknown items are not replayed, and component receipts do not replace DAG native delivery and acceptance.
Native gradients, multiple fills, and source project recolor rework: use this skill's Vector Appearance Guide。
Native parenting, opacity expressions, and source project rework: use this skill's Effect Expression Guide。
For Photo native adjustment layers, selection masks, and trusted-source rework, see Local Adjustment Guide。
When you need to independently launch a domain GUI command, see Own Desktop Handoff。
Hybrid task reference Business Scenario Manual, first confirm dependencies and input versions, then execute sub-projects, local rework, and delivery verification.
When installation fails, read First-Use Diagnostics, and use the receipt to locate the setup entry point of the current skill itself; handle installation failure and native invocation failure separately.
For real voiceover recognition and mixed subtitle tasks, please read this skill's Mixed ASR Guide / Mixed ASR guide, and execute according to the fixed domain dispatch and persistent model directory; planning, rework, and acceptance retain dependencies, 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 hybrid posters, covers, and source project rework, read Photo Full Delivery, and distinguish host-independent plugins from fixed dependencies within Art.
For cross-artifact observation with fixed brand and subject references, see this skill's Consistency Review Contract; acceptance of source candidates and the published fixed version are reported separately.
Runtime upgrades and legacy ledgers
When encountering runtime_upgrade_busy , keep the old runtime, original project, and ledger, and 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 the validation and mode boundaries of native command execution, see Command contract boundaries。
For the classification, parameter differences, and rejection boundaries of mode directory candidates, seeMode directory usage; Vector desktop/bridge duplicate commands have not yet completed execution qualification and cannot fall back according to the headless directory.