本文へ移動
cccskills
無料GitHub で公開

pb-image-to-3d

Turn one reference image into a cleaned, scaled 3D asset: your own image-to-3D ComfyUI workflow makes the mesh, Blender decimates it to a poly budget, fixes scale, origin and material, and exports a .glb. Use for "image to 3D", "make a 3D model from this picture", "photo to glb".

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Image to 3D asset

What you get: a cleaned, scaled .glb from one reference image, with a preview you approved. Availability: needs the comfyui-mcp server configured in the harness (no config is shipped). Missing → stop at preflight with that message.

Inputs

  • image — the reference image path
  • comfy_workflow — path to a ComfyUI API-format workflow JSON that contains the image-to-3D nodes; required, never invented (no TripoSR or TRELLIS server ships with AOS)
  • poly_budget — maximum face count
  • project — a slug for renders/<project>/

Steps

  1. Preflight — one probe per server, before any file is written: check_comfyui_health on comfyui-mcp; get_scene_info on bdb_blender_mcp. MCP tools may be deferred in the harness: try to load the tool once via the harness MCP list before declaring it missing. Tool not loaded, call errors, or ComfyUI status is not "online" → stop with "Missing MCP: <server> (<tool> unavailable). Start <ComfyUI|Blender and click Connect to Claude in the BlenderMCP sidebar tab> and check mcpServers.<server> in your harness config." (comfyui-mcp: use the Availability message above) and write nothing except the run log — both probes answered
  2. Ask — image, comfy_workflow path, poly_budget, project slug, target size in metres → run log and renders/<project>/ — all answered, image and workflow files exist
  3. ComfyUI — the workflow file's text with the image filled in as the JSON string for queue_prompt → get_history <prompt_id> status success → get_output_media_info path of the mesh file — a mesh file exists; local_path is only set when COMFYUI_DIR is set, so if local_path is empty or exists_locally is false, stop with a clear message and import nothing
  4. Blender (bdb-blender-mcp, godmode-3d-creation) — mesh file → via execute_blender_code: import, Decimate modifier down to poly_budget, scale to the target size, origin to base centre, one material, and report face count and dimensions; get_scene_info as the cross-check — face count <= poly_budget and non-zero dimensions; save the Blender project first, since scripted code can crash the session
  5. Preview — a viewport render saved to renders/<project>/preview.png via execute_blender_code — file exists — stops for approval (taste review); changes loop back to step 4
  6. Export — execute_blender_code runs the glTF binary export → renders/<project>/asset.glb — file exists and is larger than 0 bytes; re-import the file or read the exported object stats and log face count and dimensions again

Run log: production_artifacts/pb-image-to-3d-<date>.md in the start directory, never committed

Rules

  • A failed check stops the run: write the failure into the run log and report. No silent retries.
  • Write one run-log line per step as it completes (N. done|skipped|failed — artifact — check result) and WAITING FOR APPROVAL: <step> at each stop.
  • This playbook has no GO step: it writes only under renders/<project>/ and publishes nothing.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

hybridlabor-api のスキルをすべて見る

このスキルの問題を報告する