This skill handles creating anchor points, control handles, closing and editing vector paths. It hands off to skills in the same package by name and can be used when installed on its own; it does not read sibling directories. It invokes the fixed official vectorcraft-cli and preserves the native editing project.
Inputs and deliverables
The inputs are the user-confirmed task, materials, project or objects, output directory and scope of modification; when an existing project is needed, verify the summary first. It returns the actual CLI results, the saved native project, any required derived outputs and verification records. Installation success, the existence of the command directory and completion of the authoring task are reported separately.
First use and common entry points
Locate the real directory of the current SKILL.md. Currently macOS arm64 and Python 3.11+ are supported; the fixed CLI is installed into 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) where the host actually loads this SKILL.md . A user-level installation may be located in ~/.agents/skills/vectorcraft-cli-paths, a project-level one may be located in .agents/skills/vectorcraft-cli-paths, and a plugin may be located in its skills/vectorcraft-cli-paths 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.
Execution of the 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 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, 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 the startup parameters.
Scenario operations
Verify this scenario's inputs, native project, target objects, versions and output boundaries. Select the current command according to the scenario guide , save an independent checkpoint, then execute; after completion, reopen the native project and check the actual output and non-target content.
commands returns a JSON parameter catalog;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, resolve object IDs within the same batch; convert outputs according to extension.
Verify closure, direction, curve control handles and target IDs; do not rename raster files as vector projects.
For native composition and source project revisions, use the vectorcraft-harness skill's scripts/workflow.py; read the workflow contract, and templates are within this skill's examples. Modify only authorized objects; preserve the native project and dependent materials; for derived format loss, read the exchange report。
Verification and recovery
A non-zero command exit does not count as 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: observations for the fixed version, used only as routing and parameter references; live results take precedence, and disabled items are not executed.
- Workflow contract: combined operations, native saving, dependency collection, and revisions.
- Hand installation/diagnostics to vectorcraft-cli-setupwhen needed, and 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 via 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 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's source. 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 into the delivery manifest, and this record is verified during rework; native project dates and revision history remain traceable.
Full native commands use
The current skill comes with parameter descriptions for the complete catalog and a same-session entry point, unrestricted by the creative template whitelist. Read the full 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 real 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 that all instructions, GUI, delivery, or Art orchestration have been accepted.
For the full workflow command gateway, see usage instructions. For the fixed CLI versions and artifact digests, defer to the scripts/runtime.lock.json bundled with the vectorcraft-harness skill; the skill package version defers to 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 may first use this skill's bundled fixed desktop installation; 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's parameters can be viewed via this skill's commands.py describe ; the general CLI list also retains all commands not assigned to specialized skills.
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 diagnostics, and locate the current skill's own setup entry point based on the receipt; installation failures and native invocation failures are handled separately.
For related creative tasks, read the object selection and transformation scenarios, and verify native parameters, object context, local rework, and delivery boundaries.
For object layout, state, and path editing, first read this skill's bundled object operation guide, and verify authorized objects, boundary types, and original project retention requirements.
Same-target execution protection
Before invoking public workflows, read this skill's execution registration and interruption handling. In cases of contention or unknown state, do 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 contract on demand. The examples referenced by the contract are divided into creation and rework; before use, bind the current source project and real receipts; the normal workflow and the complete command plan format are handled separately. Hosts that support calling the policy are routed by vectorcraft-use by default, and specialized skills may call it explicitly; other hosts dispatch according to actual capabilities.