agentleFS
PicsArtPicsArt/media-studio/skills/make-cartoon/SKILL.md

make-cartoon

Skill1 starsChanged 10 days agoMITView on GitHub

Make a short cartoon clip with a character the user picks or describes - one 9:16 video of 8 to 20 seconds with one or two characters in one place, who walk in, wave, reach, hold or carry a prop, and a narrator's voice-over or captions. A character is picked from the ready-made cast or the user's saved library, or built from a part sheet into an editable cut-out rig and checked on a short test render, then saved for reuse. Use when the user wants a cartoon, an animated character or a mascot clip, a kids' story beat, or a short scene with their character. Not for a character's sheet with no scene, nor for a drama with several scenes, nor for motion on a design (animate-design).

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    When you read picsart_scene_capabilities or the recipe index (picsart_scene_recipe without name), pass useCase: "make-cartoon": the answer …

    line 15
  2. Distinctive:

    Read picsart-video-rules first.

    line 17
  3. Distinctive:

    Before acting on a stage, load the available skills in its row that apply to this job, also when the work resumes there.

    line 24
  4. Distinctive:

    Only when a beat needs one, and one prop per character, one of:

    line 80
  5. Very specific:

    Place each character's scene with fit: none on the floor line.

    line 92
  6. Very specific:

    Start each line within 0.3 seconds of the beat it describes.

    line 97
  7. Very specific:

    Check the scene with picsart_scene_validate and the capabilities' own limits.

    line 99
  8. Distinctive:

    Before building, list one shot per beat, each with its size:

    line 103
  9. Distinctive:

    no torn, floating or missing part in any frame, and the far hand never vanishes in a walk.

    line 120
  10. Very specific:

    no torn or missing part, and nothing cut by the frame edge (sheet.

    line 134

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Make a cartoon

When you read picsart_scene_capabilities or the recipe index (picsart_scene_recipe without name), pass useCase: "make-cartoon": the answer leads with what this job reads and names the rest in one line.

Read picsart-video-rules first. One job: one short cartoon clip, 9:16, 8 to 20 seconds, one or two characters, one place, with a narrator's voice-over or captions. The characters do not speak on screen, and nothing here turns, sits, hugs, claps or hands a prop to another character: reword such a beat or say "not yet". More than two characters, a second place, more than 20 seconds or another ratio is a different job: say so before starting. These limits are for planning a new cartoon. They never cap an edit the user asks for: an edit that lengthens the clip, such as slowing the ending, is done as asked. If it pushes the clip past 20 seconds, say so once and do it anyway.

Before acting on a stage, load the available skills in its row that apply to this job, also when the work resumes there.

character-rigging is read by section, not whole: references/rig-build.md for Cast, rig-place.md and rig-controls.md for Place and Prop, rig-act.md for Build the scene (its router table names them).

StageGateSkills
1. The planASKscene-building-basics
2. CastASK, SPEND, REVIEWcharacter-rigging
3. PlaceSPENDscene-building-basics
4. PropSPENDcharacter-rigging
5. Build the sceneSPENDcharacter-rigging, scene-building-basics, voice-over-generation, background-music
6. ReviewREVIEWmotion-review
7. ExportDELIVERscene-building-basics

1. The plan

Turn the request into one short paragraph and ASK (with your host's own question tool, such as AskUserQuestion, so the options are buttons the user taps, the recommended one first; only where the host has none, the options numbered in one message; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) the user to approve or edit it in one turn: who (one or two characters), where (one place), what happens in 3 to 5 beats, and the narration or caption lines. A beat is one of: walk in or out, idle, wave, reach, pick up, hold or carry a prop, put it down, jump, jog. Think and hand-over join the list when picsart_scene_capabilities shows them. Read the allowed actions from picsart_scene_capabilities, not from memory: a beat it does not list is reworded or refused.

2. Cast

One character at a time. Look in the user's saved library first with picsart_scene_library_list (kind: "character"; each row gives parameterCount, and detail: "full" with name returns that one character's controls), and offer the ready-made cast from picsart_scene_capabilities. ASK (with your host's own question tool, such as AskUserQuestion, so the options are buttons the user taps, the recommended one first; only where the host has none, the options numbered in one message; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) which: a saved or ready-made one, or one built from a part sheet they drew.

Pick. A saved character is a scene in the library, placed by reference so a second scene with the same character is identical: picsart_scene_apply_template with uri: "library:<libraryId>" (no mode) returns a scene_ref snippet, and picsart_scene_patch adds it as a layer: an add op with kind: "layer" and value { id, start, duration, content: <the snippet> }. Do not inline the character. A ready-made one comes from picsart_scene_templates the same way, with the template's uri. Actions are applied later, to the placed character, with picsart_scene_apply_preset.

Their own sheet. The user sends one SVG drawn to character-rigging's part-sheet layout, received with picsart_drive_upload_ask. Run picsart_scene_build_model with character: {svg, check: true} first and read pictureCheck: a failed named check is fixed on the drawing by the user, never by building anyway. Build the view with character: {svg, view}, place it in a 3-second test scene (rest, then walk), render it with picsart_scene_export and REVIEW it by eye: every part present and attached, the far hand there, feet on the floor. Save the accepted character with picsart_scene_library_save, kind: "character", so it is reused from the library.

3. Place

The background is one of:

  • a plain or gradient background from the capabilities;
  • the user's own 9:16 picture, received with picsart_drive_upload_ask and declared as an asset.

Set the floor line where the characters stand, and say where it is.

4. Prop

Only when a beat needs one, and one prop per character, one of:

  • a shape;
  • the user's own picture with a transparent background (PNG or SVG), received with picsart_drive_upload_ask; check its alpha edges.

It is held by the hand socket, and by the mouth for the dog: read how from character-rigging's held props. A prop that is not held by a socket is not a prop.

5. Build the scene

Catalogue presets only, through picsart_scene_apply_preset and picsart_scene_patch: the walk, wave, reach, hold and carry, jump, jog, idle, with the camera fixed for each shot and one view per beat. Place each character's scene with fit: none on the floor line. The narration is one of:

  • the user's own recording, received with picsart_drive_upload_ask and transcribed with picsart_media_transcribe for its timing;
  • the lines as captions, with no voice.

Start each line within 0.3 seconds of the beat it describes. Background music is optional: music the user sends, received with picsart_drive_upload_ask, goes on an audio layer under any voice. Check the scene with picsart_scene_validate and the capabilities' own limits.

Staging

Before building, list one shot per beat, each with its size:

  • wide: the establishing shot, the opening beat only;
  • medium: the characters are at least 35% of the frame height, for action and dialogue;
  • close: head and shoulders, the face at least 15% of the frame width, for the emotional beat.

A story has at least 3 shots, and its emotional beat is a close. Change the framing with the camera: the push_in preset (zoom is the scale it ends at) for a move in, or a cut, the camera keys on the same frame, for a new shot. A move eases and never snaps in the middle of a beat.

Two characters who talk or react to each other face each other, both in the three-quarter view, never both side-on. Nothing important is cut by the frame edge: never a face; feet leave the frame only in a close. A prop that changes state (a tower that falls, a cup that fills) crossfades over at least 6 frames; it never swaps in one.

6. Review

Render the busiest beat for 3 to 5 seconds first, then the whole clip, and look at every beat of it, not one still. Review it as motion-review says. The checks that matter:

  • no torn, floating or missing part in any frame, and the far hand never vanishes in a walk;
  • planted feet do not slip, the walk starts and stops cleanly, and the character stays on the floor line;
  • a wave keeps the hand beside or above the head, never over the face;
  • a held prop stays at its socket in every frame, and is picked up and put down without a jump.

Self-check before export. Render a contact sheet with picsart_scene_contact_sheet at about 2 frames a second and look at it. Fix each failure through its own path and render again, before any export:

  • legs cycle while a character moves, and nothing freezes for over 1 s except the end hold: also run picsart_scene_check_motion at 10 fps on a foot's and a hand's part layer (<id>__leftFootArt, <id>__rightHandArt, ids from picsart_scene_query_layout) and read observedMin/observedMax: a foot that never moves up and down, or a hand flat for seconds, lost its preset bindings, so reapply acting (or walk_cycle) and merge new keys into content.parameters, never replace it;
  • a held prop sits in the palm and is layered right (no tool checks this; look at the sheet): hold it in the near hand, heldBy the near side (right on a rig as drawn);
  • no torn or missing part, and nothing cut by the frame edge (sheet; picsart_scene_lint_layout only lists a layer mostly off canvas): move the layer's transform.position;
  • characters and props do not overlap each other (sheet; picsart_scene_lint_layout compares whole frames and flags a pair that does not touch): move the layer's transform.position;
  • whatever stands nearer paints in front: for each beat where layers overlap, write a contract asserting {"kind": "order", "axis": "paint", "follows": "bottom", "members": [...]}, run picsart_scene_check_contracts and read groundPaintOrder in picsart_scene_lint_layout; on a failure, move the nearer layer after the other in layers;
  • the ending hold is 1 s or less (picsart_scene_check_motion shows when the last part stops): shorten the composition and layer duration;
  • the voice-over starts on its beat: move the audio layer's start.

REVIEW the preview with the user. They tweak timing, positions and colours in picsart_scene_tune, or ask in words.

7. Export

picsart_scene_export, 1080 by 1920 at 30 fps. DELIVER the downloadUrl, naming each check that failed its bar before any praise, and for each character whether it was loaded from the library or newly drawn (DELIVER in picsart-video-rules). Offer to save the scene to the library as kind story with picsart_scene_library_save, and do it only on a yes. Say where each character is kept.

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.