This skill is responsible for outputting vector exchange, preview, and multi-artboard asset packages. It hands off to skills in the same package by name, can be used when installed standalone, and does not read sibling directories. It invokes the fixed official vectorcraft-cli and preserves native editing projects.
Inputs and Delivery
The inputs are the user-confirmed task, materials, project or objects, output directory, and modification scope; when an existing project is required, 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 creation task completion separately.
First-Time Use and Public Entry Point
Locate the real directory of the current SKILL.md. Currently supports macOS arm64, Python 3.11+; the fixed CLI is installed to the user data directory. When existing task authorization covers the necessary dependencies, execute this skill's installer directly and do not create a separate approval process.
Set SKILL_DIR to the directory (absolute path) of the actually loaded SKILL.md on the host. User-level installations may be located at ~/.agents/skills/vectorcraft-cli-export, project-level installations may be located at .agents/skills/vectorcraft-cli-export, and plugins may be located in their skills/vectorcraft-cli-export or host cache directory; use the actual loaded path as authoritative, do not guess based on the current working directory, and do not search and arbitrarily select a duplicate version. The skill directory and the CLI's user data installation directory are two independent locations.
Execution implementation is converged 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 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
In CLI argv, after -- , the native subcommand must come first. Installation parameters go before the separator;--runtime-home can isolate the cache. Stop when locked 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 startup 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, and then execute; after completion, reopen the native project and check the actual output and non-target content.
commands returns a JSON parameter directory;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, parse object IDs in the same batch; convert outputs by extension.
Export by extension and artboard scope, and verify SVG structure/PDF page count/PNG dimensions; the native format is always preserved.
For native composition and source project revisions, use the vectorcraft-harness skill's scripts/workflow.py; read the workflow contract, and the templates are in this skill's examples. Modify only authorized objects, preserve the native project and dependency materials, and for derived format loss read the exchange report。
Verification and Recovery
A non-zero command exit is not considered completion; it is necessary to inspect the actually 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 Save As revisions; when the corresponding project summary does not match, refuse to overwrite.
On-Demand References and Handoff
- actual command evidence: Fixed-version observations, for routing and parameter reference only; real-time results take precedence, and disabled items are not executed.
- Workflow Contract: Composite operations, native saving, dependency collection, and revision.
- Hand installation/diagnostics to vectorcraft-cli-setupwhen needed, and hand full task routing to vectorcraft-use; when skills are 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 a maintained version based on the official v0.2.0 : 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 artboards according to native drawing boundaries, conservatively preserving groups, clipping, and unknown-scope dependencies.
The PDF workflow binds 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.
Complete native commands use
The current skill includes a complete directory of parameter descriptions and same-session entry points, and is not subject to the creative template allowlist. Read the complete usage guide, and consult the command referenceas needed; 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 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 explicit active row scenarios, use this skill'sexecutable creation/rework instructions。
For GUI tasks, you may first use the fixed desktop installationincluded with this skill; installation, startup, and actual GUI editing are verified separately.
Complete attribution commands are listed by command family in the categorized usage list, and each item can be viewed through this skill's commands.py describe to see parameters; the general CLI list also retains all commands not assigned to specialized skills.
Business tasks start from the scenario operation manual and are executed through 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 setup entry point of the current skill itself; installation failures and native invocation failures are handled separately.
For related creative tasks, read object selection and transformation scenarios, and verify native parameters, object context, local rework, and delivery boundaries.
Same-target execution protection
Before calling a public workflow, read this skill's execution registration and interruption handling. In competitive or unknown states, do not delete registrations, automatically replay, or switch targets to bypass verification.
Operation contract and routing policy
Read this skill's as neededInput, precondition, side effect, result, recovery, and acceptance contract. The examples referenced by the contract are divided into creation and rework, and are bound to the current source project and real receipts before use; the normal workflow and the complete command plan format are handled separately. Hosts that support the invocation policy are routed by default via vectorcraft-use , and specialized skills may be invoked explicitly; other hosts dispatch according to their actual capabilities.