artcraft-harness

ArtCraft Harness (built-in execution channel)

This skill is the ArtCraft skill suite'ssole execution implementation: Node and orchestration runtime installation, domain skill source distribution, semantic plan workflow, public CLI, domain command handoff, review and revision, and packaging and package verification are all consolidated in this directory scripts/ .artcraft-use、artcraft-cli and each domain skill are thin documentation skills—they provide scenario guidance, plan examples, and reference contracts, while actual execution always goes through this skill's entry points.Before executing any ArtCraft script, first set HARNESS_DIR to this SKILL.md 's directory (the absolute path actually loaded by the host); do not assume the current working directory is the skill directory. User-level installations may be located at ~/.agents/skills/artcraft-harness, project-level ones may be located at .agents/skills/artcraft-harness, and plugins may be located in their skills/artcraft-harness or the host cache directory; the path actually loaded by the host shall prevail.

Eight entry points

Entry point	Purpose
scripts/bootstrap.py	First-time installer:--runtime-only installs the locked Node and orchestration packages;--plugin <domain> incrementally installs the selected domain skill sources and native CLI, returning a JSON receipt.
scripts/workflow.py	Semantic plan executor: automatically installs the required domains according to the task graph, and saves and verifies native projects, derived outputs, and project packages.
scripts/cli.py	Public orchestration CLI direct channel:--version / --help / run/status/cancel/package/verify-package; place native subcommands after -- .
scripts/domain_commands.py	Complete domain command handoff:list / describe / check / run, query 2646 commands, actual MCP parameters, and hand off the selected domain.
scripts/package.py	Project packaging and mobile package verification:create / verify, collect native projects and workflow records from the trusted ledger.
scripts/review.py	Review records:record / verify, bind named observations, responsible plugins, and the current version.
scripts/revision.py	Controlled revision:step / status, freeze the policy and execute explicit patches, saving rounds and the best package anchor.
scripts/brief.py	Versioned requirements records:create / assess, workflow.py consumes via --brief/--brief-sha .

scripts/setup.py is the domain skill source installation implementation called internally by bootstrap.py, and is not a standalone entry point;png_inspection.py、jpeg_inspection.py、consistency.py、mode_catalog.py、public_call.py、download.py、native_contract.py is dynamically loaded by the above entry points by fixed filename or invoked as a subprocess, and is not executed separately. For runtime versions and artifact digests, scripts/distribution.lock.json and scripts/node.lock.json shall prevail.

Usage

Scenario guidance in domain skills such as artcraft-use shall prevail; plan and example files are taken from the corresponding domain skill directory (SKILL_DIR refers to the domain skill's own directory):

: "${HARNESS_DIR:?请先设置为 artcraft-harness SKILL.md 的实际所在目录}"
python3 -I -B "$HARNESS_DIR/scripts/bootstrap.py" --runtime-only
python3 -I -B "$HARNESS_DIR/scripts/workflow.py" \
  "$SKILL_DIR/examples/brand-campaign.json" \
  --output /absolute/path/brand-project \
  --authorization brand-project-authorized \
  --asset voice=/absolute/path/voice.wav

Public CLI and domain command handoff (cli.py's native subcommands must be placed after -- ; domain_commands.py output is always JSON):

python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- --version
python3 -I -B "$HARNESS_DIR/scripts/domain_commands.py" list --domain effectcraft --filter expression

Offline artifacts can be specified with --node-archive、--bundle-dir、--native-archive-dir ; these parameters do not bypass digest, path, or version verification.--runtime-home or CRAFT_RUNTIME_HOME specify the isolated installation directory. The installation scope is only the user data directory; sudo is not required, and PATH is not modified.

Relationship between domain skills and this harness

• artcraft-use: complete task routing and delivery contract; execution still goes through this harness.
• artcraft-cli: Scenario knowledge for public CLI, MCP, and diagnostics; execution still goes through this harness.
• artcraft-cli-setup: First-time installation, digest verification, and troubleshooting guidance; execution still goes through this harness.
• artcraft-cli-plan / execute / assets / revise / recover / deliver / review: Scenario knowledge and examples for planning, execution, material registration, revision, recovery, delivery, and review; execution still goes through this harness.
• In the domain skill document, SKILL_DIR refers to the domain skill's own directory (used to read its examples/、references/); script execution paths are all changed to this directory HARNESS_DIR/scripts/。
• For the execution contract (installation receipt, task receipt, recovery, review, revision, packaging, mode directory), see the artcraft-use skill's corresponding references/ document; this skill's references/ only stores the execution contract JSON read by the script via ROOT/references/ (domain-command-index.json、mode-command-catalog.json）。