Update to Picsart
Snapshot Nov 7, 2026 · 00:09 UTC · version 2.4.0
Collection source: downloaded plugin package.
Instructions updated for get-started
Skill instructions — Now says: Before acting on a stage, load the skills in its row that apply to this job, also when the work resumes there. - `edit-footage`: the user's own footage...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Nov 3, 2026 · 18:14 UTC
- `cut-footage-into-reel`: the user's own footage of people talking becomes a tight vertical short, the best moments in order, with captions and music if they want them.
Nov 7, 2026 · 00:09 UTC
Before acting on a stage, load the skills in its row that apply to this job, also when the work resumes there. - `edit-footage`: the user's own footage becomes a tight vertical short, podcast clips or a finished edit, the best moments ...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -18,6 +18,8 @@ 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. + | Stage | Gate | Skills | |---|---|---| | 1. The account and the credits | — | — | @@ -73,8 +75,9 @@ - `animate-design`: a design or the user's own images and clips become an animated ad or reel; - `movie-producer`: a story becomes a short film with recurring characters, one look and several scenes; -- `cut-footage-into-reel`: the user's own footage of people talking becomes a tight vertical short, the - best moments in order, with captions and music if they want them. +- `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; +- `make-comics`: a photo of a person becomes a ComicMe comic book, tale, video, reel or anime series. ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; 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.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: get-started\ndescription: 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.\nmetadata:\n uses: open-picsart-app\n optional: open-picsart-app\n title: Get started\n short-description: Connect your account and see what Picsart can do\n argument-hint: '[what you want to make]'\n starter-prompt: Show me what Picsart can do.\n---\n\n# Getting started with Picsart Video\n\nRead picsart-video-rules first. One job: in a turn or two, the user knows their account works, has their\nPicsart open if they want it, and knows what to ask for next. Nothing here charges credits.\n\nIf the user installed Picsart Video in the middle of a task, do stage 1, then go back to that task\nin the same conversation. Offer the rest in one line at the end instead.\n\n| Stage | Gate | Skills |\n|---|---|---|\n| 1. The account and the credits | — | — |\n| 2. Open Picsart, when the host has it | ASK | open-picsart-app |\n| 3. What Picsart Video does | — | — |\n| 4. Where to start | ASK | — |\n\n## 1. The account and the credits\n\nCall `picsart_credits` with `{}`.\n\n- **It answers:** say in one line that the account is connected and give the balance as the tool\n returns it. Never round it, add it up or guess it.\n- **It says the user is not signed in:** say that making and editing need a signed-in Picsart\n account, and that the host will ask them to sign in the first time a step needs it. Go on with\n stage 3, and skip stage 2 until they are signed in.\n- **It fails otherwise:** say that the balance could not be read right now, and go on.\n\n## 2. Open Picsart, when the host has it\n\nOnly when the open-picsart-app skill is among your skills: offer it as that skill says. Without it,\nskip this stage and say nothing about it: not every host can open Picsart beside the conversation.\n\n## 3. What Picsart Video does\n\nSay it in three short parts, in the user's words. The tools in brackets are for you, never for the\nuser (picsart-video-rules's Tools).\n\n- **Drive.** Their files, stored with their Picsart account: browse them, search them in\n Picsart, make folders, move and delete (a deleted file goes to the trash first).\n The `picsart_drive_*` tools do this (`picsart_drive_list`, `picsart_drive_create_folder`,\n `picsart_drive_move`, `picsart_drive_delete`). When they bring a file of their own, it comes in with\n `picsart_drive_upload_ask`.\n- **Create.** Images, videos and audio from a prompt, with a choice of models. They can pick a\n model themselves (`picsart_model_show`), and every creation is quoted before anything is\n charged (`picsart_preflight`, then picsart-video-rules's SPEND).\n- **Edit.** For an image: remove the background (`picsart_image_remove_bg`), replace it\n (`picsart_image_change_bg`), enhance it (`picsart_image_enhance`) or turn it into a vector\n (`picsart_image_vectorize`). For a video: a scene editor where they watch it, trim, split and comment,\n and approve it before it is exported (`picsart_scene_editor`, picsart-video-rules's REVIEW).\n\nEdits charge credits too; each is quoted first. Say that once, not per item.\n\n## 4. Where to start\n\nOffer the use cases in this package that fit the user, in their words. Name only use cases that\nare here: look at the skills you have, not at this list. Today they can include:\n\n- `generate-media`: one image, video, voice line, sound or song from a prompt, or one edit of a\n picture;\n- `make-screen-videos`: a screen recording of an app or website becomes how-to shorts, a promo or a\n tutorial;\n- `animate-design`: a design or the user's own images and clips become an animated ad or reel;\n- `movie-producer`: a story becomes a short film with recurring characters, one look and several\n scenes;\n- `cut-footage-into-reel`: the user's own footage of people talking becomes a tight vertical short, the\n best moments in order, with captions and music if they want them.\n\nASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; 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\nstage. On \"Just explore\", invite them to ask for anything from stage 3, and end the turn.\n""---\nname: get-started\ndescription: 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.\nmetadata:\n uses: open-picsart-app\n optional: open-picsart-app\n title: Get started\n short-description: Connect your account and see what Picsart can do\n argument-hint: '[what you want to make]'\n starter-prompt: Show me what Picsart can do.\n---\n\n# Getting started with Picsart Video\n\nRead picsart-video-rules first. One job: in a turn or two, the user knows their account works, has their\nPicsart open if they want it, and knows what to ask for next. Nothing here charges credits.\n\nIf the user installed Picsart Video in the middle of a task, do stage 1, then go back to that task\nin the same conversation. Offer the rest in one line at the end instead.\n\nBefore acting on a stage, load the skills in its row that apply to this job, also when the work resumes there.\n\n| Stage | Gate | Skills |\n|---|---|---|\n| 1. The account and the credits | — | — |\n| 2. Open Picsart, when the host has it | ASK | open-picsart-app |\n| 3. What Picsart Video does | — | — |\n| 4. Where to start | ASK | — |\n\n## 1. The account and the credits\n\nCall `picsart_credits` with `{}`.\n\n- **It answers:** say in one line that the account is connected and give the balance as the tool\n returns it. Never round it, add it up or guess it.\n- **It says the user is not signed in:** say that making and editing need a signed-in Picsart\n account, and that the host will ask them to sign in the first time a step needs it. Go on with\n stage 3, and skip stage 2 until they are signed in.\n- **It fails otherwise:** say that the balance could not be read right now, and go on.\n\n## 2. Open Picsart, when the host has it\n\nOnly when the open-picsart-app skill is among your skills: offer it as that skill says. Without it,\nskip this stage and say nothing about it: not every host can open Picsart beside the conversation.\n\n## 3. What Picsart Video does\n\nSay it in three short parts, in the user's words. The tools in brackets are for you, never for the\nuser (picsart-video-rules's Tools).\n\n- **Drive.** Their files, stored with their Picsart account: browse them, search them in\n Picsart, make folders, move and delete (a deleted file goes to the trash first).\n The `picsart_drive_*` tools do this (`picsart_drive_list`, `picsart_drive_create_folder`,\n `picsart_drive_move`, `picsart_drive_delete`). When they bring a file of their own, it comes in with\n `picsart_drive_upload_ask`.\n- **Create.** Images, videos and audio from a prompt, with a choice of models. They can pick a\n model themselves (`picsart_model_show`), and every creation is quoted before anything is\n charged (`picsart_preflight`, then picsart-video-rules's SPEND).\n- **Edit.** For an image: remove the background (`picsart_image_remove_bg`), replace it\n (`picsart_image_change_bg`), enhance it (`picsart_image_enhance`) or turn it into a vector\n (`picsart_image_vectorize`). For a video: a scene editor where they watch it, trim, split and comment,\n and approve it before it is exported (`picsart_scene_editor`, picsart-video-rules's REVIEW).\n\nEdits charge credits too; each is quoted first. Say that once, not per item.\n\n## 4. Where to start\n\nOffer the use cases in this package that fit the user, in their words. Name only use cases that\nare here: look at the skills you have, not at this list. Today they can include:\n\n- `generate-media`: one image, video, voice line, sound or song from a prompt, or one edit of a\n picture;\n- `make-screen-videos`: a screen recording of an app or website becomes how-to shorts, a promo or a\n tutorial;\n- `animate-design`: a design or the user's own images and clips become an animated ad or reel;\n- `movie-producer`: a story becomes a short film with recurring characters, one look and several\n scenes;\n- `edit-footage`: the user's own footage becomes a tight vertical short, podcast clips or a finished\n edit, the best moments in order, with captions and music if they want them;\n- `make-comics`: a photo of a person becomes a ComicMe comic book, tale, video, reel or anime series.\n\nASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; 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\nstage. On \"Just explore\", invite them to ask for anything from stage 3, and end the turn.\n"Full snapshot data
{
"description": "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.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 162
}
],
"name": "get-started",
"skill_md_contents": "---\nname: get-started\ndescription: 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.\nmetadata:\n uses: open-picsart-app\n optional: open-picsart-app\n title: Get started\n short-description: Connect your account and see what Picsart can do\n argument-hint: '[what you want to make]'\n starter-prompt: Show me what Picsart can do.\n---\n\n# Getting started with Picsart Video\n\nRead picsart-video-rules first. One job: in a turn or two, the user knows their account works, has their\nPicsart open if they want it, and knows what to ask for next. Nothing here charges credits.\n\nIf the user installed Picsart Video in the middle of a task, do stage 1, then go back to that task\nin the same conversation. Offer the rest in one line at the end instead.\n\nBefore acting on a stage, load the skills in its row that apply to this job, also when the work resumes there.\n\n| Stage | Gate | Skills |\n|---|---|---|\n| 1. The account and the credits | — | — |\n| 2. Open Picsart, when the host has it | ASK | open-picsart-app |\n| 3. What Picsart Video does | — | — |\n| 4. Where to start | ASK | — |\n\n## 1. The account and the credits\n\nCall `picsart_credits` with `{}`.\n\n- **It answers:** say in one line that the account is connected and give the balance as the tool\n returns it. Never round it, add it up or guess it.\n- **It says the user is not signed in:** say that making and editing need a signed-in Picsart\n account, and that the host will ask them to sign in the first time a step needs it. Go on with\n stage 3, and skip stage 2 until they are signed in.\n- **It fails otherwise:** say that the balance could not be read right now, and go on.\n\n## 2. Open Picsart, when the host has it\n\nOnly when the open-picsart-app skill is among your skills: offer it as that skill says. Without it,\nskip this stage and say nothing about it: not every host can open Picsart beside the conversation.\n\n## 3. What Picsart Video does\n\nSay it in three short parts, in the user's words. The tools in brackets are for you, never for the\nuser (picsart-video-rules's Tools).\n\n- **Drive.** Their files, stored with their Picsart account: browse them, search them in\n Picsart, make folders, move and delete (a deleted file goes to the trash first).\n The `picsart_drive_*` tools do this (`picsart_drive_list`, `picsart_drive_create_folder`,\n `picsart_drive_move`, `picsart_drive_delete`). When they bring a file of their own, it comes in with\n `picsart_drive_upload_ask`.\n- **Create.** Images, videos and audio from a prompt, with a choice of models. They can pick a\n model themselves (`picsart_model_show`), and every creation is quoted before anything is\n charged (`picsart_preflight`, then picsart-video-rules's SPEND).\n- **Edit.** For an image: remove the background (`picsart_image_remove_bg`), replace it\n (`picsart_image_change_bg`), enhance it (`picsart_image_enhance`) or turn it into a vector\n (`picsart_image_vectorize`). For a video: a scene editor where they watch it, trim, split and comment,\n and approve it before it is exported (`picsart_scene_editor`, picsart-video-rules's REVIEW).\n\nEdits charge credits too; each is quoted first. Say that once, not per item.\n\n## 4. Where to start\n\nOffer the use cases in this package that fit the user, in their words. Name only use cases that\nare here: look at the skills you have, not at this list. Today they can include:\n\n- `generate-media`: one image, video, voice line, sound or song from a prompt, or one edit of a\n picture;\n- `make-screen-videos`: a screen recording of an app or website becomes how-to shorts, a promo or a\n tutorial;\n- `animate-design`: a design or the user's own images and clips become an animated ad or reel;\n- `movie-producer`: a story becomes a short film with recurring characters, one look and several\n scenes;\n- `edit-footage`: the user's own footage becomes a tight vertical short, podcast clips or a finished\n edit, the best moments in order, with captions and music if they want them;\n- `make-comics`: a photo of a person becomes a ComicMe comic book, tale, video, reel or anime series.\n\nASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; 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\nstage. On \"Just explore\", invite them to ask for anything from stage 3, and end the turn.\n"
}SHA-256 of public snapshot: 8a189c1d0cd372fde0b3748ba8b6438e4c62d02e5b32da49328c387655492a5e