What makes PixelLab Pip notable?

1.3K downloads. Trust evidence available

How should PixelLab Pip be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

PixelLab Pip

Use for PixelLab/Pip setup, auth, MCP/API routing, asset generation, editing, animation, talking portraits, lip sync, skeleton/template/preset animations, multi-shot/looping cinematics, Game Builder, docs/troubleshooting, bark completion sounds, and explicit PixelLab cost/budget/credit questions across MCP, REST v2/API, website/editor Pixelorama, Aseprite, and legacy v1. Trigger only when PixelLab (Pixel Lab) context is present, including PixelLab setup, MCP/API setup, PIXELLAB_SECRET, bearer-token auth, PixelLab sprites, sprite sheets, characters, portrait characters, vocal animations, talking GIFs, lip-sync plans, fonts, objects, tiles, tilesets, tilemaps, maps, Godot/Unity map export, UI, icons, backgrounds, palettes, image edits, animations, skeletons, template animations, preset animations, cinematics, looping or seamless-loop scenes, multi-shot scenes, endpoint choice, SDK integration, blueprints/recipes, recreating/replaying `*.blueprint.json` generations, troubleshooting, or PixelLab credits/cost/budget. Do not trigger for unrelated Python pip/package-manager requests or generic image/pixel-art requests with no PixelLab intent.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.3k

Updated

Oct 10, 2026

Version

1.9.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.3K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.3K downloadsadoption · observed Oct 10, 2026
Latest release: 1.9.0release · observed Sep 25, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17b8e52xm06jqme72q0tw427189zwp7:pixellab-pip

Install using `clawhub skill install s17b8e52xm06jqme72q0tw427189zwp7:pixellab-pip` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/shilo/pixellab-pip before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-shilo-pixellab-pip/snapshot"

Documentation

CLAWHUB

158,061 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: pixellab-pip
description: Use for PixelLab/Pip setup, auth, MCP/API routing, asset generation, editing, animation, talking portraits, lip sync, skeleton/template/preset animations, multi-shot/looping cinematics, Game Builder, docs/troubleshooting, bark completion sounds, and explicit PixelLab cost/budget/credit questions across MCP, REST v2/API, website/editor Pixelorama, Aseprite, and legacy v1. Trigger only when PixelLab (Pixel Lab) context is present, including PixelLab setup, MCP/API setup, PIXELLAB_SECRET, bearer-token auth, PixelLab sprites, sprite sheets, characters, portrait characters, vocal animations, talking GIFs, lip-sync plans, fonts, objects, tiles, tilesets, tilemaps, maps, Godot/Unity map export, UI, icons, backgrounds, palettes, image edits, animations, skeletons, template animations, preset animations, cinematics, looping or seamless-loop scenes, multi-shot scenes, endpoint choice, SDK integration, blueprints/recipes, recreating/replaying `*.blueprint.json` generations, troubleshooting, or PixelLab credits/cost/budget. Do not trigger for unrelated Python pip/package-manager requests or generic image/pixel-art requests with no PixelLab intent.
license: MIT
metadata:
  requires_api_key: false
  api_key_env: PIXELLAB_SECRET
  api_key_note: "Optional. Guidance, setup, routing, and docs need no key. Live PixelLab generation needs a bearer token, configured in the MCP client or as PIXELLAB_SECRET for REST v2 fallback; the skill uses it only as an auth header and never reads, prints, or stores its value."
permissions: # declared least-privilege capabilities: reads env var PIXELLAB_SECRET, runs the python command, reads/writes its own output and config files
  - env
  - shell
  - file_read
  - file_write
---

# PixelLab Pip

Classify the request, choose the supported PixelLab surface, then act. Answer questions directly when the request is a question.

## Workflow

1. Classify intent; values combine, such as `animate + cost_sensitive`:
   `question | setup | update | uninstall | bark | auto | create asset | edit/transform | animate | prompt_enhancement | cost_sensitive | integrate/code | check balance/status | troubleshoot docs/API | website/editor assistance | game_builder | aseprite_integration | blueprint/recipe`.
   A standalone `setup`, `update`, `uninstall`, `bark`, or `auto` word after an explicit skill invocation, such as `/pixellab-pip setup` or `@pixellab-pip bark off`, is that intent: for setup read `references/setup.md`, for update read `references/update.md`, for uninstall read `references/uninstall.md`, for bark read `references/bark.md`, for auto read `references/auto.md`.
2. Classify the target:
   `general_image | skill_icon | item_icon | background | character | portrait_character | font | object | effect_vfx | ui | whole_map | map_image | map_object | top_down_tileset | sidescroller_tileset | multi_shape_tileset | path_tiles | building_kit | isometric_tile | tile_variants | animation | existing_image`.
   F

_meta.json

{
  "ownerId": "kn7fdby451538hjnyh1h82kadx89zcjs",
  "slug": "pixellab-pip",
  "version": "1.9.0",
  "publishedAt": 1790370795825
}

references/animation.md

# Animation

Read this for raw animation, managed character/object animation, interpolation, skeleton animation, outfit transfer, rotation, frame anchors, or animation preview verification.

## Route Choice

Use MCP `animate_character`/`animate_object` for managed MCP assets. For a raw supplied image with no managed asset, use MCP `animate_image_pixminimax` only when the user explicitly requests PixMiniMax/MiniMax H3; otherwise use MCP `animate_image`. On REST, use `POST /animate-pixminimax` for that explicit model request, or `POST /animate-with-text-v3`/`interpolation-v2` otherwise. The v3 idle-loop, atlas, and pixel-budget risks below were characterized against the REST v3 endpoint; PixMiniMax has separate frame, cost, and prompt rules in the next section. Use REST `estimate-skeleton` for a one-pose estimate and legacy `/animate-with-skeleton` only for its exact older schema; use REST v2 for outfit transfer, raw frame editing, or rotation (`edit-animation-v2`, `transfer-outfit-v2`, `rotate`). For 8 rotations from an image, MCP only partially covers it by regenerating rather than rotating the exact input — `create_8_direction_object(reference_image_base64=…)` for objects, `create_character(mode="v3", reference_image_base64=…)` for characters (identity transfer is unreliable on `create_8_direction_object` for humanoid subjects); use REST `generate-8-rotations-v2/v3` when the exact input pixels must be preserved.

Skeleton v3 has separate raw and managed routes: use MCP `animate_with_skeleton_v3` for caller-supplied poses, or REST `POST /animate-with-skeleton-v3`; managed characters use MCP `animate_character(mode="skeleton-v3", template_animation_id=...)` when the current schema exposes that mode, otherwise REST `POST /animate-character` with `mode="skeleton-v3"` and `template_animation_id`. REST `enhance-animation-v3-prompt` accepts `engine="skeleton-v3"` for action prep; the MCP animation tool has no inline enhancer. Read `preset-skeleton-template-animation.md` for frame/keypoint requirements and the distinction from legacy `/animate-with-skeleton`.

Classify supplied frame images (first frame vs last frame vs style/edit reference vs managed asset ID) per the Goal Router in `image-input-roles.md`; ask before a credit-spending call when the role would change the endpoint, field, or output.

## PixMiniMax / MiniMax H3

PixelLab's public PixMiniMax operation is REST `POST /animate-pixminimax` and MCP `animate_image_pixminimax`. It is beta and available to Tier 1+ subscribers. Version 0.4.123 also lists it in Character Creator, Creator, Aseprite, and Pixelorama; those are human product surfaces, not private transports to reproduce in a request. The public wrapper accepts a motion-only `description` (limit in `prompt-limits.md`), a required `first_frame`, an optional same-size `last_frame`, `frame_count` 4–40 in multiples of four, an optional `seed`, `no_background`, `drift_threshold`, and `enhance_prompt`; the eight-way `direction` hint is valid o

references/aseprite-cli.md

# Aseprite CLI Integration

Read this only when the user explicitly asks for Aseprite handling: opening output in Aseprite, creating/updating an `.aseprite` file, importing PixelLab frames as layers/frames/tags, palette/indexed conversion, or exporting via the Aseprite CLI/Lua. Most local preview work belongs in `local-asset-assembly.md` instead.

This is a low-risk pipeline:

```text
PixelLab MCP or documented REST v2
  -> verified local image/frame files
  -> Aseprite CLI or Aseprite Lua script
  -> `.aseprite`, PNG sequence, GIF, spritesheet, metadata, or visible Aseprite workspace
```

Aseprite is a local workspace/import/export tool applied after PixelLab generated the pixels. It arranges PixelLab/user images into layers, frames, tags, cels, and exports; it never authors content (per SKILL.md Asset Integrity — no Lua draw/brush/shape/scripted pixel placement unless the user approves a labeled non-PixelLab fallback).

For explicit Aseprite MCP requests, read `aseprite-mcp.md`; return here when the task also needs direct CLI/Lua file handling.

## Extension Safety

This route never drives or reads the PixelLab Aseprite extension — it is built around interactive editor state, dialogs, plugin prefs, and private first-party communication, not a headless automation API. Do not:

- drive its dialogs or call its modules/operation URLs from Lua;
- run its `generate-*.lua` files through `aseprite --script` to spend credits or call private operations;
- read its credentials, payloads, auth headers, settings, or request history.

Its "reduce-colors" (and unzoom, pixel correction) round-trip the image to a PixelLab server and place the result back — they are not local Aseprite quantization; do not present them as local-only. Treat extension startup errors in batch mode as a diagnostic signal, not something to work around by reading internals. If the user needs exact extension behavior, the stable route is PixelLab MCP/REST plus Aseprite CLI workspace handling, or visible manual Aseprite use.

## Lua Integration Model

Aseprite Lua runs inside Aseprite, not as an external controller. The agent launches the executable and Aseprite runs the script:

```powershell
& $AsepritePath -b --script-param "output=$Output" --script "script.lua"
```

Inside the script Aseprite exposes globals such as `app`, `Sprite`, `Image`, `Point`, `Rectangle`, `ColorMode`. `app.params` receives `--script-param` values, `app.open()` loads sprites, and sprite methods or `app.command.*` modify/export them. This makes Lua the tool for file/workspace automation, not the extension (below).

## Safety Gates

Before running Aseprite:

1. Verify the executable path:

   ```powershell
   $AsepritePath = (Get-Command aseprite -ErrorAction SilentlyContinue).Source
   if (-not $AsepritePath) { throw "Aseprite executable not found; ask the user for the path." }
   ```

   Search common install locations only when appropriate, or ask the user for the path. Do not scan private project folders unl

references/aseprite-mcp.md

# Aseprite MCP Integration

Read this only when the user explicitly asks for a third-party Aseprite MCP server or MCP-based Aseprite tooling. For ordinary Aseprite CLI/Lua file handling, use `aseprite-cli.md`.

Third-party Aseprite MCP servers are an optional escalation, not the default PixelLab-to-Aseprite route. Use one only when it adds real value beyond documented CLI/Lua — for example many small iterative draw/layer/cel/palette/animation operations, or curated visual-QA tools that are safer or clearer than a custom script. For import/export/package tasks already covered by CLI/Lua, stay with CLI/Lua.

## Safety delta over aseprite-cli.md

Everything in `aseprite-cli.md` still applies — Safety Gates, Original File Safety, and Verification. On top of that:

- Any MCP tool that saves back to a `.aseprite` file is a write operation. Apply the CLI original-file safety first: copy the original before mutation unless the user approved in-place editing of that exact path, show which files are read/written, and ask before overwriting.
- Treat destructive tools (delete, flatten, merge, erase, crop, resize, quantize, save-back) as copy-on-write by default; prefer read-only MCP tools for inspection and QA.
- A raw-Lua MCP tool is unrestricted local host-code execution, exactly like `aseprite --script`. Prefer curated tools or small reviewed scripts.
- Do not use an MCP server to inspect PixelLab credentials, extension request history, or private extension state.
- After a run, verify expected outputs (and, for copy-on-write flows, that the original was unchanged); treat printed `ERROR:` as failure even when the MCP call itself returned success.

For palette clamps, 1-bit output, batch import/export, layer copy, and QA mechanics, follow `aseprite-cli.md` — see its "Patterns Usable Without MCP" and "Palette Quantization" sections.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.