This skill handles first-time installation, digest verification, version checking, and missing-runtime troubleshooting. 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 official vectorcraft-cli and preserves native editing projects.
Inputs and Deliverables
The inputs are the user-confirmed task, materials, project or object, output directory, and modification scope; when an existing project is needed, verify the digest first. It returns the actual CLI results, the saved native project, any required derived outputs, and verification records. Installation success, command directory existence, and creation task completion are reported 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 fixed CLI is installed to the user data directory. When an existing task authorization covers the necessary dependencies, run 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 at ~/.agents/skills/vectorcraft-cli-setup, project-level ones may be located at .agents/skills/vectorcraft-cli-setup, and plugins may be located in their skills/vectorcraft-cli-setup 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.
Execution implementation converges in the built-in vectorcraft-harness skill (installed bundled with the plugin; for standalone installation use npx skills add full-aigc-skills/vectorcraft-skills --skill vectorcraft-harness). Set HARNESS_DIR to that skill's actual loaded directory (absolute path); this skill's SKILL_DIR is used only to read its own examples/ and references/。
: "${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
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 locking the artifact digest fails, when the installation is corrupted, or when 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 read the system/architecture, Python version, and the user's existing authorization; run this skill's bootstrap.py. Verify the executable path, digest, and version in the JSON receipt; do not rely on the shell PATH. Repeated calls reuse the fixed installation; on failure, stop and record the specific error.
commands returns the JSON parameter directory;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, parse object IDs in the same batch; convert outputs by extension.
Do not modify PATH and do not use sudo; keep corrupted versions and report errors, do not automatically upgrade.
Native composition and source project revision use the vectorcraft-harness skill's scripts/workflow.py; read workflow contract, the templates are in this skill's examples. Modify only authorized objects, preserve native projects and dependent materials, and for derived format loss read 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. Mark timeout results as unknown, check the original task/project first, and do not automatically replay edits. Existing native workflows support Save As revision; when the corresponding project digest does not match, refuse to overwrite.
On-Demand References and Handoff
- Actual command evidence: Fixed-version observation, for routing and parameter reference only; real-time results take precedence, and disabled items are not executed.
- Workflow contract: combined operations, native saving, dependency collection, and revision.
- When installation/diagnosis is needed, hand off to vectorcraft-cli-setup, and hand off complete task routing to vectorcraft-use; when a skill is missing, use
npx skills add full-aigc-skills/vectorcraft-skills --skill <skill-name>. Do not load other skills through adjacent file paths.
This skill does not provide a fictitious login interface; local headless does not require a cloud account. Complete GUI, cross-editor fidelity, and creative quality are stated according to actual evidence.
The current runtime is a maintained version v0.2.0 based on the official 0.2.0-craft.2, published by full-aigc-skills/vectorcraft-skills ; the installation record clearly distinguishes the source of the maintained version. The SVG workflow isolates the artboard according to native drawing boundaries, conservatively preserving groups, clipping, and unknown-scope dependencies.
The PDF workflow is bound to the project creation date; when the creation date is missing, the first export date record is retained.pdf-export-date.json The summary is written into the delivery manifest, and this record is verified during rework; native project dates and revision history remain traceable.
Complete native commands use
The current skill includes the complete directory parameter descriptions and same-session entry points, and is not subject to the creative template whitelist. Read the complete usage guide, and consult as needed the 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. 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 the usage instructions. The version and artifact digest of the fixed CLI are based on the scripts/runtime.lock.json included with the vectorcraft-harness skill; the skill package version is based on the corresponding release tag. Independent installation re-verification and full command-by-command acceptance are recorded separately, and release is not used as a substitute for acceptance.
For native gradients, global palette linkage, multiple fills, and clear active-row scenarios, use this skill'sexecutable creation/rework instructions。
For GUI tasks, you may first use this skill's built-in fixed desktop installation; installation, startup, and actual GUI editing are verified separately.
Business tasks start from the scenario operation manual , and are executed according to input checks, template adaptation, native delivery, local rework, and result verification.
When installation fails, read the first-use diagnosis, and use the receipt to locate the current skill's own setup entry point; installation failures and native invocation failures are handled separately.
For related creative tasks, read the object selection and transformation scenarios, and check native parameters, object context, local rework, and delivery boundaries.
Same-target execution protection
Before invoking a public workflow, read this skill's execution registration and interruption handling. In cases of competition or unknown status, do not delete the registration, automatically replay, or switch targets to bypass verification.
Operation contract and routing policy
Read as needed this skill'sinput, prior state, side effects, results, recovery, and acceptance contract. The examples referenced in the contract are divided into creation and rework, bound to the current source project and real receipts before use; ordinary workflows and full command plan formats are handled separately. Hosts that support invocation policies are by default routed by vectorcraft-use , and specialized skills may be explicitly invoked; other hosts dispatch according to actual capabilities.