agentleFS
with-pebblywith-pebbly/aseprite-ai-artist/skills/export/SKILL.md

export

Skill473 starsChanged 44 days agoMITView on GitHub

Produce the files an engine actually consumes — spritesheets with atlases, GIFs, scaled PNGs — with the tags and layout the target needs. Use when work is finished and needs to leave Aseprite.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use menu, import and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sasly2048Skill

    menu

    Point the user to cc-atlas's full interactive menu (dashboard, project comparison, session replay, team activity, anomalies, goals) — screens that need a real terminal.

    Also in 3 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 3 projects that use this

  • kv0906Skill

    preview

    Render vault notes as styled HTML and open in browser. Turn markdown docs, decisions, progress reports into readable previews. Use for "/preview docs/project-a/checkout-flow.md", "/preview progress all", "/preview decide auth-approach", or when user wants to see a doc before sharing.

    Also in 3 projects that use this

  • AnthropicSkill

    search

    Search across all connected sources in one query. Trigger with "find that doc about...", "what did we decide on...", "where was the conversation about...", or when looking for a decision, document, or discussion that could live in chat, email, cloud storage, or a project tracker.

    Also in 4 projects that use this

  • GoogleSkill

    dashboard

    Configures and launches the GKE Capacity & Triage Dashboard scoped to a GCP project ID, GKE cluster name, or target ML workload ID. Uses the configure-and-launch-dashboard action and launch-workload-dashboard workflow to verify local dashboard health, discover cluster capacity, trigger live scans, and generate deep-linked URLs. Use when the user types "/dashboard", says "launch dashboard", "open dashboard", "show capacity", or "view triage dashboard" with a project, cluster, or workload. Don't use for general workload log querying or automated failure attribution (use the troubleshoot skill).

    Also in 4 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Run aseprite:review. Exporting broken art just distributes it.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “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

Export game-ready assets

Ask what consumes it

The target decides the format, and guessing produces files someone has to re-export. If you do not know, ask — it is one question.

TargetWants
UnitySpritesheet PNG + JSON atlas, byTag split
GodotSpritesheet PNG, or .aseprite via an importer plugin
Web / canvasSpritesheet PNG + JSON
Preview for a humanGIF, or a scaled PNG
Print / socialPNG at 4–8×

Before exporting

Run aseprite:review. Exporting broken art just distributes it.

Then check specifically:

  • Tags exist and are named the way the engine expects — idle, walk, attack. validate errors on untagged multi-frame sprites.
  • The reference layer is deleted or hidden, and so is the sketch layer.
  • Frame durations are set. GIF and most engines read them from the file.

Exporting

Spritesheet with atlas — what an engine usually wants:

export op="spritesheet" path="…/knight.png" sheetType="packed" byTag=true padding=1

padding prevents texture bleed at non-integer zoom, which shows up as a thin line of the neighbouring frame along a sprite's edge. Use 1 unless the engine says otherwise.

The JSON atlas is written beside the PNG and carries per-frame rectangles and per-tag ranges.

9-patch panels and hotspots — sprite_manage op="slice_create" names a region with an optional center (the stretchable middle, for 9-slicing) or pivot. Create slices before exporting; a spritesheet export carries them into its JSON atlas alongside the per-frame rectangles.

Animation preview for a human:

export op="gif" path="…/walk.gif"

Scaled PNG — for a store page or a README:

export op="png" path="…/knight@8x.png" scale=8

Integer scale only. Nearest-neighbour. Any other kind of resize destroys the thing you made.

Save the source

Exporting does not save the working document.

sprite_manage op="save"

The .aseprite file is the asset. The PNG is a build artifact.

Report

List the files you wrote, their dimensions, the frame count and the tags. That is what the person wiring them into the engine needs.

Related

rules://07-review-checklist, rules://05-animation.

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.