picsart-add-media
Skill7 starsChanged 20 days agoMITView on GitHub
Bring the user's own clips, photos or audio into Picsart as hosted URLs, through the gen-ai MCP's upload widget or, where a shell can read the file, a direct upload. Use when a Picsart tool needs a URL and the media is on the user's machine or in a chat attachment.
In this repository69 other files it gives its agents.
- ai-presenterSkill
- animate-designSkill
- app-ui-animationSkill
- asset-auditSkill
- assetsSkill
- background-musicSkill
- caption-decorationsSkill
- character-riggingSkill
- custom-transitionsSkill
- design-layer-importSkill
- drama-series-writingSkill
- edit-footageSkill
- edit-on-your-computerSkill
- edit-pipelineSkill
- face-hidingSkill
- figma-storyboard-animationSkill
- film-animaticSkill
- film-cast-designSkill
- film-cuttingSkill
- film-finishingSkill
- film-shot-generationSkill
- film-story-writingSkill
- footage-analysisSkill
- footage-reframingSkill
- generate-mediaSkill
- get-startedSkill
- large-scene-assemblySkill
- linked-element-motionSkill
- make-cartoonSkill
- make-characterSkill
- make-comicsSkill
- make-screen-videosSkill
- make-short-dramaSkill
- motion-design-craftSkill
- motion-intentSkill
- motion-pattern-librarySkill
- motion-reviewSkill
- motion-scene-continuitySkill
- motion-tracking-from-videoSkill
- movie-producerSkill
- open-picsart-appSkill
- photo-slideshowSkill
- picsart-video-rulesSkill
- quality-reviewSkill
- quick-merge-and-exportSkill
- realistic-color-gradeSkill
- recastSkill
- recreate-videoSkill
- reel-structureSkill
- reference-fragment-matchingSkill
- resting-frame-rulesSkill
- retention-hooksSkill
- scene-3d-authoringSkill
- scene-animation-referenceSkill
- scene-building-basicsSkill
- scene-template-remixSkill
- screen-recording-analysisSkill
- screen-recording-layoutsSkill
- screen-recording-zoomSkill
- screen-ui-redesignSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
If the server is not connected, say so.
- Very specific: line 62
If you have a shell and the file is on disk, use picsart_upload_local_files instead: pass each file's name and bytes, run the command it …
- Very specific: line 68
Call picsart_media_upload with whichever of purpose, accept, detected_files, known_urls apply.
- Very specific: line 104
Re-asking for a file that's already uploaded: Check the conversation for a URL you already have before opening the widget — pass it via …
≈ “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.
Files
Add Media (Upload Widget)
Picsart's MCP tools take URLs, not local paths, and most agent hosts (browser-based chats, Claude Code without shell access, ChatGPT web) can't read a file straight off the user's disk either. The fix is a browser-based upload widget: an MCP tool opens a drag-and-drop panel in the user's browser, the browser uploads the file directly to Picsart's CDN, and the widget hands the resulting URL back to you. No file bytes ever pass through a tool call.
When to Use
Fires on things like "I have 3 video clips", "here are my photos", "use my footage", "combine these clips" — anything where the media is the user's own and you don't already have a link to it.
Reach for this whenever the next step needs a URL (image_url, video_url, startFrame, …) and
the source is something on the user's own machine, a chat attachment you can't fetch, or anything
else not already a public https:// link.
Prerequisites
The Picsart gen-ai MCP server (picsart, declared in this repo's .mcp.json) in the
current tool list. It offers two routes:
picsart_media_upload— opens the upload widget. Works on every host, including ones with no shell. The widget also has a "My Drive" tab when the user's Picsart Drive is reachable, and tries to save each upload to their Drive.picsart_upload_local_files— for a host that can run shell commands and can read the file on disk. It returns one upload command per file; run it, and the printed JSON holds the hosted URL atresponse.url. No widget and no wait for the user. The hosted copy is temporary.
If the server is not connected, say so; don't guess a tool name.
How to Run
No script to run — this skill is one tool call plus a short wait for the user's next message.
Quick Reference
| Argument | What it does |
| (none) | Opens the widget with no pre-filled context — a plain drag-and-drop |
purpose | Label shown on the dropzone (e.g. "product photo") |
accept | Restrict to image, video, or audio |
detected_files | Filenames you can see in the conversation but can't reach yourself (e.g. a chat attachment) — rendered as a hint only |
known_urls | URLs already produced earlier in the conversation, seeded as pickable chips so the user isn't asked to re-upload something already available |
Procedure
If you have a shell and the file is on disk, use picsart_upload_local_files instead: pass each
file's name and bytes, run the command it returns with the file's path, and go straight to
step 3 with the URL it prints. Otherwise:
1. Call the upload tool
Call picsart_media_upload with whichever of purpose,
accept, detected_files, known_urls apply. All arguments are optional — calling with none
just opens the widget.
{ "purpose": "product photo", "accept": "image", "known_urls": ["https://cdn.picsart.io/…already-uploaded.jpg"] }detected_filesis a label hint only, never a filter — it's model-supplied and can be wrong or hallucinated. The user can still drop any file they want; don't tell them a file is "not accepted" because it wasn't in yourdetected_fileslist.known_urlssaves a re-upload: if a URL already exists from earlier in the conversation (a prior generation result, a prior upload), pass it here so it shows up as a chip the user can pick instead of finding the file again.
2. Tell the user what to do, then wait for their next message
The widget reports the uploaded URL(s) back to you via a mechanism most agent hosts only deliver on the user's next message — not instantly within the same turn. This is a real two-turn handshake, not a delay you can poll through.
Say something like: "I've opened the upload panel — drop your file in and let me know once it's there." Then stop and wait. Do not claim you can't see the file, or that the upload failed, just because nothing arrived in the same turn you called the tool.
3. Hand the URL to the tool the user actually wanted
Once the URL comes back (on the user's next message), pass it into the URL-shaped parameter of
whatever tool the user's original request needs (image_url, video_url, etc.).
Pitfalls
- Expecting the URL in the same turn. It won't be there — see step 2. Prompt the user and wait for their next message instead of reporting failure early.
- Treating
detected_filesas a filter. It's a display hint for filenames you can see but can't fetch. Never reject or second-guess a file the user actually drops based on this list. - Re-asking for a file that's already uploaded. Check the conversation for a URL you already
have before opening the widget — pass it via
known_urlsinstead of starting over. - Guessing the tool name. The upload tools are
picsart_media_uploadandpicsart_upload_local_files, both onpicsart. Read what the tool list actually shows.
Verification
- The tool call that opened the widget returned without error.
- A URL came back on a subsequent user message and looks like a real hosted link (not a local path).
- The downstream tool call accepting that URL didn't fail on the URL itself.
Related
- The
video-prompt-engineerskill writes the prompt for a video generated from the URLs this skill returns.
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
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.

