This skill handles placing assets, managing links, symbols, and tracing existing images. 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
Inputs are the user-confirmed task, assets, project or objects, output directory, and modification scope; 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 creation task completion separately.
First-time 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 installs to the user data directory. When 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) where the host actually loads this SKILL.md . User-level installations may be located in ~/.agents/skills/vectorcraft-cli-assets, project-level ones may be located in .agents/skills/vectorcraft-cli-assets, and plugins may be located in their skills/vectorcraft-cli-assets or host cache directory; rely on the actual load 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.
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 load directory (absolute path); this skill's SKILL_DIR is only used 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
For CLI argv, after -- , 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 on an unsupported platform; do not modify PATH and do not perform floating upgrades. The native help entry point is help; the launcher's own --help only explains launch parameters.
Scenario operations
Verify this scenario's inputs, native project, target objects, 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 inspect the actual output and non-target content.
commands returns the JSON parameter catalog;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, resolve object IDs within the same batch; convert outputs by extension.
After image tracing, inspect the actual path structure; collect links and verify digests, and clarify the difference between embedding and referencing.
Native composition and source project revisions use the vectorcraft-harness skill's scripts/workflow.py; read the workflow contract, and templates are in this skill's examples. Modify only authorized objects, preserve the native project and dependency assets, and for derived-format loss read the exchange report。
Verification and recovery
A non-zero command exit does not count as completion; you need to inspect the actual saved project, exports, dimensions, and media decoding. Mark timeout results as unknown, check the original task/project first, and do not automatically replay edits. Existing native workflows support saving revisions; refuse to overwrite when the corresponding project summary does not match.
On-demand reference and handoff
- actual command evidence: Fixed-version observation, used only as routing and parameter reference; real-time 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 vectorcraft-cli-setup, and hand off full 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 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.
The current runtime is the 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 maintained version source. The SVG workflow isolates artboards 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 to the delivery manifest, and this record is verified during rework; native project dates and revision history remain traceable.
Register asset operations: use the examples/provided-assets.jsonincluded with this skill, and pass the actual asset via --asset product=/absolute/product.png --asset logo=/absolute/logo.svg .asset.place supports multiple instances;asset.replace performs targeted updates with the original alias and the new input alias. For specific parameters, raster linking/vector embedding, dependency collection, and migration boundaries, see this skill's Workflow contract. This is currently a skill source candidate and does not mean the old fixed plugin snapshot already includes this capability.
Full native command usage
The current skill includes parameter descriptions for the full catalog and same-session entry points, and is not restricted by the creative template whitelist. Read Full usage guide, and consult the command referenceas needed; each instruction has a skill route, pre-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 all instructions, GUI, delivery, or Art orchestration have been accepted.
For the full workflow command gateway, see Usage instructions. The version and artifact summary 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 a substitute for acceptance.
For native gradients, global palette linkage, multiple fills, and explicit active row scenarios, use this skill'sexecutable creation/rework instructions。
For GUI tasks, you can first use the fixed desktop installationincluded with this skill; installation, startup, and actual GUI editing are verified separately.
Full attribution commands are listed by command family in categorized usage list, and each item can be viewed through this skill's commands.py describe to view parameters; the general CLI list 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 use the receipt to locate the current skill's own setup entry point; installation failures and native invocation failures are handled separately.
Related creative tasks read Object selection and transformation scenarios, verify native parameters, object context, local rework, and delivery boundaries.
Same-target execution protection
Before invoking public workflows, read this skill's execution registration and interruption handling. Contested or unknown states must not delete registrations, automatically replay, or switch targets to bypass verification.
Operation contract and routing policy
Read this skill'sinput, precondition state, side effects, results, recovery, and acceptance contractas needed. The examples referenced by the contract are divided into creation and rework; before use, bind the current source project and real receipts; 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.