agentleFS
Sign inStart free
PicsArtPicsArt/gen-ai-skills/skills/assets/SKILL.md

assets

Skill6 starsChanged 19 days agoMITView on GitHub

Open the Picsart Assets panel on what the user made with Picsart - their videos, images, audio, film characters, film props and film projects - newest first, with previews, or on one kind or one film when they name it. Use when the user wants to see what they made ("show my assets", "my film characters", "open the two-sisters film") or asks for the assets panel. Not for browsing Drive folders, and not for choosing a film's references for a generation.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read picsart-video-rules first.

    line 14
  2. Very specific:

    Call picsart_film_show_assets, read-only and free:

    line 24
  3. Very specific:

    Nothing named: call it with {}. Every kind opens, one tab per kind.

    line 26
  4. Very specific:

    One kind named: call it with type: video, image, audio, character, prop, or project for their films or projects.

    line 27
  5. Very specific:

    A film named: call it with { "type": "project", "pageSize": 128 } first.

    line 29
  6. Distinctive:

    When the tool says the user is not signed in, or that Drive is unavailable, say so in one line.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 7 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

Browse assets

Read picsart-video-rules first. One job: open the Assets panel on what the user asked to see. Nothing here charges credits.

StageGateSkills
1. Open the panelASK—
2. One line——

1. Open the panel

Call picsart_film_show_assets, read-only and free:

  • Nothing named: call it with {}. Every kind opens, one tab per kind.
  • One kind named: call it with type: video, image, audio, character, prop, or project for their films or projects.
  • A film named: call it with { "type": "project", "pageSize": 128 } first. Find the film by its name among the projects it returns; while none fits and the reply says hasNext, call it again with the next page. Then call it with that project's uid as projectUid, and with type too when they asked for one kind of that film ("the characters of the garage film"). When two films fit the name, 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 one, with their names as the options. When no page has it, say in one line that no film has that name, and stop.

Pass a projectUid only as a type: "project" reply gave it: the panel refuses any other folder. When the tool says the user is not signed in, or that Drive is unavailable, say so in one line.

This panel is for looking. Browsing Drive folders is picsart_drive_list, and reading a film's assets for a generation is picsart_film_list_assets.

2. One line

The panel already shows every file. Say in one short sentence what is open ("Your film characters are open."), and never list the files back, by name or by count.

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