This skill is responsible for producing Logo icon multi-artboard and artboard size variants. 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 the native editing project.
Inputs and Deliverables
The inputs are the user-confirmed task, assets, project or object, output directory, and modification scope; when an existing project is needed, verify the summary first. Return the actual CLI results, the saved native project, the required derived outputs, and the verification record. Installation success, command directory existence, and creation task completion are reported 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 the existing task authorization covers the necessary dependencies, execute this skill's installer directly, without creating a separate approval process.
Set SKILL_DIR to the directory (absolute path) where the actually loaded SKILL.md for this host resides. User-level installations may be located at ~/.agents/skills/vectorcraft-cli-artboards, project-level ones may be located at .agents/skills/vectorcraft-cli-artboards, and plugins may be located in their skills/vectorcraft-cli-artboards 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 select a duplicate version. The skill directory and the CLI's user data installation directory are two independent locations.
The execution implementation is converged into 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
After the CLI argv is at -- , the native subcommand must be placed 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 execute floating upgrades. The native help entry point is help; the launcher itself --help only describes startup parameters.
Scenario Operations
Verify this scenario's inputs, native project, target objects, versions, and output boundaries. According to the scenario guide , select the current command, save an independent checkpoint, then execute; after completion, reopen the native project and check the actual outputs and non-target content.
commands returns a JSON parameter catalog;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, resolve object IDs in the same batch; convert outputs by extension.
--artboard is 0-based; --range is 1-based; verify the correspondence of each artboard during export.
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 dependent assets, and 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, exports, dimensions, and media decoding need to be inspected. Mark timeout results as unknown, check the original task/project first, and do not automatically replay edits. The existing native workflow supports save-as revisions; refuse to overwrite when the corresponding project summary does not match.
On-Demand Reference and Handoff
- Actual command evidence: observations for the fixed version, 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 revisions.
- When installation/diagnostics are needed, hand off to vectorcraft-cli-setup; for full task routing, hand off 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 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 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'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 to the delivery manifest, and this record is validated during rework; native project dates and revision history remain traceable.
Complete native commands use
The current skill includes the full directory's parameter descriptions and same-session entry points, and is not restricted by 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 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 fixed CLI's version and artifact summary are based on the vectorcraft-harness skill's bundled scripts/runtime.lock.json ; 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 clear active row scenarios, use this skill'sexecutable creation/rework instructions。
For GUI tasks, you can 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 can be viewed via 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 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 current skill's own setup entry point; 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.
Same-target execution protection
Before invoking a public workflow, read this skill's execution registration and interruption handling. Competing 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, and before use they are bound to the current source project and the actual receipt; the ordinary workflow and the complete command plan format are handled separately. Hosts that support the invocation policy are by default routed by vectorcraft-use routed, and specialized skills may be explicitly invoked; other hosts dispatch according to actual capabilities.