This skill is responsible for using Pathfinder, compound paths, and shape-building tools. It hands off by name with skills in the same package, can be used when installed alone, and 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, assets, project or object, output directory, and scope of modification; 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, existence of the command directory, and completion of the creative task separately.
First 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, directly execute this skill's installer and do not create a separate approval process.
Set SKILL_DIR to the directory (absolute path) of the loaded SKILL.md actually loaded by the host. User-level installations may be located at ~/.agents/skills/vectorcraft-cli-boolean, project-level ones may be located at .agents/skills/vectorcraft-cli-boolean, and plugins may be located in their skills/vectorcraft-cli-boolean 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 choose a duplicate version. The skill directory and the CLI's user data installation directory are two independent locations.
Execution is implemented and 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 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
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 itself --help only explains startup parameters.
Scenario Operations
Verify this scenario's inputs, native project, target objects, version, and output boundaries. According to the scenario guide , 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 the JSON parameter catalog;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, parse object IDs in the same batch; convert outputs according to the extension.
Boolean order affects the result; verify the selected objects, holes, and winding, and keep a checkpoint before the operation.
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 dependent assets, and for derived format loss read the exchange report。
Verification and Recovery
A nonzero 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 saving revisions under another name; refuse to overwrite when the corresponding project summary does not match.
On-Demand Reference 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/diagnostics are needed, hand off to vectorcraft-cli-setup; full task routing is handed off 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 record of the first export date is retained.pdf-export-date.json 's 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 includes a complete directory parameter description and same-session entry, not subject to the creative template whitelist. Read the complete usage guide, and query 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 real registry and the current executable state, 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 full 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 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 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 according to input checks, template adaptation, native delivery, partial rework, and result verification.
When installation fails, read first-use diagnostics, and use the receipt to locate the current skill's own setup entry; installation failures and native invocation failures are handled separately.
For related creative tasks, read object selection and transformation scenarios, and check native parameters, object context, partial 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 contention or unknown state, do not delete the registration, automatically replay, or switch targets to bypass verification.
Operation contract and routing policy
Read this skill's as neededInput, preconditions, side effects, results, recovery, and acceptance contract. The examples referenced in the contract are divided into creation and rework, and are bound to the current source project and actual receipts before use; the regular workflow and the full command plan format are handled separately. Hosts that support the invocation policy default to being routed by vectorcraft-use ; specialized skills can be invoked explicitly; other hosts dispatch according to actual capabilities.