This skill is responsible for querying actual command parameters and capabilities, invoking the public CLI, MCP, and diagnostics. 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 pinned official vectorcraft-cli and preserves native editing projects.
Inputs and Deliverables
The 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. It returns actual CLI results, the saved native project, any required derived outputs, and verification records. Installation success, command directory existence, and creative task completion are reported separately.
First Use and Common Entry Points
Locate the real directory of the current SKILL.md. Currently supported: macOS arm64, Python 3.11+; the pinned CLI is installed to the user data directory. When existing task authorization covers the necessary dependencies, run this skill's installer directly; do not create 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 at ~/.agents/skills/vectorcraft-cli, a project-level one may be located at .agents/skills/vectorcraft-cli, and a plugin may be located in its skills/vectorcraft-cli or the host cache directory; go by the actual load path, do not guess based on the current working directory, and do not search and then arbitrarily pick among duplicate versions. The skill directory and the CLI's user data installation directory are two separate locations.
Execution is implemented and converged within 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
In 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 explains launch parameters.
Scenario Operations
First query the current version and command directory; record read-only and editing invocations separately. After reading the current project state and command enabled/params, construct argv; consecutive steps that need to create objects must be executed in the same session, and the returned ID must not be guessed.
commands returns the JSON parameter catalog;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, parse object IDs within the same batch; convert outputs by extension.
For native composition and source project revision, use the vectorcraft-harness skill's scripts/workflow.py; read the workflow contract, with templates inside this skill's examples. Only modify authorized objects; preserve native projects and dependent assets; for derived format loss, read the 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 checked. Mark timeout results as unknown, check the original task/project first, and do not automatically replay edits. Existing native workflows support save-as revision; refuse to overwrite when the corresponding project summary does not match.
On-Demand References and Handoff
- Actual command evidence: pinned-version observations, used only as routing and parameter references; live results take priority, and disabled items are not executed.
- Workflow contract: composition operations, native saving, dependency collection, and revision.
- Hand off to when installation/diagnosis requires vectorcraft-cli-setup, hand off complete 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 fictitious login interface; local headless does not require a cloud account. Full GUI, cross-editor fidelity, and creation quality are stated according to actual evidence.
The current runtime is a maintained version based on the official v0.2.0 maintained build 0.2.0-craft.2, published by full-aigc-skills/vectorcraft-skills ; the installation record clearly distinguishes the source of the maintained build. 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 to the delivery manifest, and this record is verified during rework; the native project date and revision history remain traceable.
Complete native commands use
The current skill includes the parameter descriptions for the complete catalog and the same-session entry point, and is not restricted by the creation template whitelist. Read complete usage guide, and consult as needed 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 current executable status, retaining 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.
See the complete workflow command gateway at usage instructions. The version and artifact digest of the pinned 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; release does not replace acceptance.
For native gradients, global palette linkage, multiple fills, and explicit active-row scenarios, use this skill'sexecutable creation/rework instructions。
GUI tasks can first use this skill's included pinned 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 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 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 diagnosis, and use the receipts to locate the setup entry point of the current skill itself; installation failures and native invocation failures are handled separately.
For related creation tasks, read object selection and transformation scenarios, and 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. Contention or unknown states must not delete registrations, automatically replay, or switch targets to bypass verification.
Operation contract and routing policy
Read this skill'sinput, prior state, side effects, results, recovery, and acceptance contract. The examples referenced in the contract are divided into creation and rework; before use, they are bound to the current source project and real receipts; the normal workflow and the complete command plan format are handled separately. The host that supports the invocation policy is by default routed by vectorcraft-use , and specialized skills can be invoked explicitly; other hosts dispatch according to actual capabilities.