agentleFS
PicsArtPicsArt/gen-ai-skills/skills/face-hiding/SKILL.md

face-hiding

Skill6 starsChanged 19 days agoMITView on GitHub

Hide the faces in a video or photo by blurring or pixelating them. A face-masked gaussian_blur or pixelate follows every face frame by frame and leaves the rest of the picture sharp. Use when asked to hide, blur, pixelate, censor, anonymize or cover someone's face, to blur faces for privacy, or to hide who is in a video. Hiding a face is an effect, not a look.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    Put the effect on the media layer and confine it with a portrait / face_skin mask.

    line 30
  2. Very specific:

    Look at two or three moments where the faces are visible, with picsart_scene_contact_sheet and times.

    line 73

≈ “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

Hiding faces

Two treatments hide a face. Both are effects, applied with picsart_scene_apply_preset; no look does this, and none is needed. Never answer that nothing is made for hiding a face.

TreatmentPresetWhat the viewer sees
Blureffect:gaussian_blur with a face maska soft, unreadable face
Pixelateeffect:pixelate with a face maskthe mosaic used to censor faces on TV

When the request names no treatment ("hide her face", "cover her face", "make him anonymous"), ask before applying anything: suggest blur and pixelate, in that order, in one short message, then apply the one the user picks.

When the request names one, apply it without asking: "blur" is the blur; "pixelate" or "mosaic" is the pixelation.

Blur or pixelate the faces

Put the effect on the media layer and confine it with a portrait / face_skin mask. The mask finds every face in each frame, so on a video the effect follows the faces as they move, and the hair, body and background stay sharp:

picsart_scene_apply_preset({
  "scene": ..., "layerId": "clip", "preset": "effect:gaussian_blur",
  "params": { "blur": 60 },
  "mask": { "provider": "portrait", "segments": ["face_skin"] }
})
picsart_scene_apply_preset({
  "scene": ..., "layerId": "clip", "preset": "effect:pixelate",
  "params": { "pixelSize": 40 },
  "mask": { "provider": "portrait", "segments": ["face_skin"] }
})

Set the strength from the size of the faces, not a fixed number:

  • blur about a tenth of the face's width in composition pixels. A face 600 px wide needs about 60; at 40 its eyes and mouth still show through. Small faces in a group shot need 20-30.
  • pixelSize about a twelfth of the face's width: 40 for a face 600 px wide.

For an export, any value is fine. For live playback, a blur past 32 costs frame time on a full-frame video, so prefer pixelate there.

What the mask covers

  • Every face in the layer. The detector does not tell people apart, so there is no way to hide one person's face and keep another's. When the request points at one person ("her face", "the man on the left") and the frames show more than one face, tell the user before exporting that every face gets the treatment.
  • The face, not the hair. To hide more of the person, mask the whole person instead: { "provider": "scene", "segments": ["person"] }. supports.maskProviders in picsart_scene_capabilities lists every region and the platforms that produce it.
  • One region per effect. Applying gaussian_blur again replaces the layer's earlier gaussian_blur, mask included.

Check the result

Look at two or three moments where the faces are visible, with picsart_scene_contact_sheet and times. Look at every face, not only the largest:

  • Each face is unreadable and the rest of the frame is as it was: the effect works. Export.
  • The whole frame is blurred: the mask did not resolve, and the effect landed on the whole layer. Check that the provider and segment are spelled as supports.maskProviders lists them.
  • A face still shows: it was too small or turned too far away for the detector at that moment. Tell the user which shots still show a face.

A masked effect runs the face detector on every frame, so a video export takes noticeably longer than one without the mask.

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.