agentleFS
Sign inStart free
freemafreema/ai-skills/skills/pixelart-cleanup/SKILL.md

pixelart-cleanup

Skill5 starsChanged 19 days agoMITView on GitHub

Use when the user wants to clean halo fragments or

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If halo is 0 but you still see artifacts, the specks have alpha ≥ threshold — raise it

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to trigger

  • User mentions "halo", "ghost pixels", "semi-transparent fringing", or "alpha cleanup"
  • User ran PixelLab and wants to post-process the output before committing assets
  • User says sprites look blurry or have faint artifacts around edges

Invocation examples

Single file:

cd scripts/pixelart-cleanup
pnpm start -- -i ../../public/assets/games/my-game/sprite.png -o ./test-samples/output --verbose

Batch folder:

cd scripts/pixelart-cleanup
pnpm start -- -i ../../public/assets/games/my-game/ -o ../../public/assets/games/my-game/ --verbose

(When output == input dir, the cleaned files overwrite in place)

Tuning order

  1. Default (--alpha-threshold 32, orphans on, min-size 1) — try this first
  2. Specks remain → raise --alpha-threshold 48 or 64
  3. Silhouette degraded → lower --alpha-threshold 16
  4. Stray clumps remain → --min-orphan-size 3
  5. Details disappearing → --no-remove-orphans as last resort

Test samples

  • Input: scripts/pixelart-cleanup/test-samples/input/
  • Output: scripts/pixelart-cleanup/test-samples/output/
  • Reference sprite: bust-1.png (64×96 PixelLab portrait)
    • Expected: halo:~177 orphans:~23

Reading the report

bust-1.png  64x96  visible 3697 -> 3343  halo:177  orphans:23  12ms
  • visible before -> after — sanity check; large drop means threshold is too aggressive
  • halo — pixels killed by the alpha-threshold pass
  • orphans — isolated pixels killed by connected-components pass
  • If halo is 0 but you still see artifacts, the specks have alpha ≥ threshold — raise it

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free