crossgen-artist

CrossGen Artist

Use this skill when an agent needs to create or modify images through a local CrossGen installation. CrossGen owns provider credentials, model capability checks, the durable queue, and Gallery state; do not bypass it by calling an image provider directly unless the user explicitly asks for a separate integration.

Choose a transport

1. Prefer the installed CrossGen MCP server when crossgen_* tools are available. The model-facing names are usually mcp__crossgen__crossgen_<tool>.
2. Otherwise use the JSON CLI (crossgen ... --json). Discover the executable with crossgen doctor --agent --json; do not assume an app path or disclose API keys.
3. If the host is DeepSeek Harness, read references/harness-mcp.md for the stdio bridge configuration. Read references/mcp-tools.md for the MCP contract and references/cli-fallback.md for equivalent CLI calls.

Standard workflow

1. Check readiness. Call crossgen_config_status or crossgen doctor --agent --json, then crossgen_provider_list and crossgen_models_list. Treat the model catalog as authoritative for provider/model compatibility.
2. Clarify the visual task. Convert the user's intent into a concrete prompt: subject, composition, style, lighting, materials, text requirements, aspect ratio, and exclusions. Preserve user-provided wording; only add structure that improves reproducibility. See references/model-workflows.md.
3. Select the operation. Use generation for prompt-only output, edit for one or more reference images, and inpaint only when a mask is available and the selected adapter advertises support. Pass providerId/model only when needed; otherwise use the active compatible configuration.
4. Confirm immediately before side effects. Generation, editing, cancellation, retry, Gallery mutations, path disclosure, and export require explicit user authorization. For MCP calls this is confirm: true; for CLI calls use --yes. Never infer confirmation from an earlier conversational turn when the request has materially changed.
5. Use idempotency for paid retries. Set a stable idempotencyKey when a request may be retried or a host may reconnect. Do not submit a second paid request merely because the first call returned before completion.
6. Monitor the durable job. Use waitMs only as a short convenience wait. Then poll crossgen_job_status (or crossgen job status) until a terminal state, with a bounded backoff. On failure, report the diagnostic and retry only with authorization.
7. Handle results through Gallery. Use crossgen_gallery_list and crossgen_asset_inspect for metadata. Export with crossgen_asset_export only when the user specifies a destination and confirms it; do not rely on undisclosed absolute paths.
8. Report precisely. Include the model/provider used, job id, terminal status, asset id(s), and any next action. Do not include API keys or local absolute paths unless explicitly requested and confirmed.