agentleFS
PicsArtPicsArt/media-studio/skills/get-started/SKILL.md

get-started

Skill1 starsChanged 10 days agoMITView on GitHub

Get started with Picsart Video - check that your Picsart account is connected and how many credits you have, open Picsart beside the conversation where the host can, and see what you can make and edit. Use when the user has just installed Picsart or Picsart Video, asks to set it up, asks what it can do, or asks how to get started.

32 other projects use 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

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

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 4

    Distinctive

    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:

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

    line 14
  2. Distinctive:

    Read picsart-video-rules first.

    line 16
  3. Distinctive:

    If the user installed Picsart Video in the middle of a task, do stage 1, then go back to that task in the same conversation.

    line 19
  4. Distinctive:

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

    line 22
  5. Very specific:

    Call picsart_credits with {}.

    line 33
  6. Distinctive:

    Only when the open-picsart-app skill is among your skills: offer it as that skill says.

    line 44

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

Getting started with Picsart Video

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

Read picsart-video-rules first. One job: in a turn or two, the user knows their account works, has their Picsart open if they want it, and knows what to ask for next. Nothing here charges credits.

If the user installed Picsart Video in the middle of a task, do stage 1, then go back to that task in the same conversation. Offer the rest in one line at the end instead.

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

StageGateSkills
1. The account and the credits——
2. Open Picsart, when the host has itASKopen-picsart-app
3. What Picsart Video does——
4. Where to startASK—

1. The account and the credits

Call picsart_credits with {}.

  • It answers: say in one line that the account is connected and give the balance as the tool returns it. Never round it, add it up or guess it.
  • It says the user is not signed in: say that making and editing need a signed-in Picsart account, and that the host will ask them to sign in the first time a step needs it. Go on with stage 3, and skip stage 2 until they are signed in.
  • It fails otherwise: say that the balance could not be read right now, and go on.

2. Open Picsart, when the host has it

Only when the open-picsart-app skill is among your skills: offer it as that skill says. Without it, skip this stage and say nothing about it: not every host can open Picsart beside the conversation.

3. What Picsart Video does

Say it in short parts, in the user's words. The tools in brackets are for you, never for the user (picsart-video-rules's Tools).

  • Drive. Their files, stored with their Picsart account: browse them, search them in Picsart, make folders, move and delete (a deleted file goes to the trash first). The picsart_drive_* tools do this (picsart_drive_list, picsart_drive_create_folder, picsart_drive_move, picsart_drive_delete). When they bring a file of their own, it comes in with picsart_drive_upload_ask. Their saved characters, locations, templates and looks (scene documents) open in the same browser with picsart_scene_library_list.
  • Edit. For a video: a scene editor where they watch it, trim, split and comment, and approve it before it is exported (picsart_scene_editor, picsart-video-rules's REVIEW).

4. Where to start

Offer the use cases in this package that fit the user, in their words. Name only use cases that are here: look at the skills you have, not at this list. Today they can include:

  • make-screen-videos: a screen recording of an app or website becomes how-to shorts, a promo or a tutorial;
  • animate-design: a design or the user's own images and clips become an animated ad or reel;
  • edit-footage: the user's own footage becomes a tight vertical short, podcast clips or a finished edit, the best moments in order, with captions and music if they want them;

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) with 2–4 of them, plus "Just explore". On a use case, start it by its name, from its first stage. On "Just explore", invite them to ask for anything from stage 3, and end the turn.

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.