image-upload
Skill1 starsChanged 9 months agoMITView on GitHub
Upload an image to Lab Nocturne and get an instant CDN URL. Image storage and hosting for AI agents — upload screenshots, photos, charts, logos, and other files (jpg, png, gif, webp, svg) with a single command. No signup required. Alternative to S3, Cloudflare Images, or Imgur for agent workflows. Use this skill whenever the user wants to upload, host, publish, or share an image file — even if they just say 'put this image somewhere' or 'get me a URL for this'. Triggered by /upload <path> or naturally.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- lifedever/skills-plugintheir own version, first seen Nov 16, 2026
- jspi-fu/Aeson-skillstheir own version, first seen Aug 21, 2026
- iamzifei/image-upload-skilltheir own version, first seen Aug 12, 2026
- Isaac-Flath/agent-starter-skillstheir own version, first seen Apr 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- jspi-fu/Aeson-skills★ 46same name
- lifedever/skills-plugin★ 14same name
- Isaac-Flath/agent-starter-skills★ 8same name
- iamzifei/image-upload-skill★ 6same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- deleteSkill
- filesSkill
- generate-keySkill
- image-deleteSkill
- image-filesSkill
- image-keySkill
- image-statsSkill
- statsSkill
- uploadSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 21
If no path is given, ask the user which file to upload.
- Very specific: line 22
Verify the file exists using ls on the path.
- Very specific: line 23
Verify the extension is one of: jpg, jpeg, png, gif, webp, svg.
- Very specific: line 27
Follow the steps in references/auth.md to resolve the API key and base URL.
- Distinctive: line 69
If the server returns a non-JSON response or an unexpected HTTP status (e.g.
≈ “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
Upload Image to Lab Nocturne
Upload an image file to the Lab Nocturne Images API and return the CDN URL.
Invocation
/upload <path> — where <path> is the file to upload. Also triggered naturally (e.g. "upload this screenshot", "host this image", "get me a URL for this png").
Instructions
1. Resolve the file path
- The user provides a file path as the argument (e.g.
/upload ./screenshot.png). - If no path is given, ask the user which file to upload.
- Verify the file exists using
lson the path. If it does not exist, tell the user and stop. - Verify the extension is one of:
jpg,jpeg,png,gif,webp,svg. If not, tell the user the file type is not supported and list the allowed types.
2. Authenticate
Follow the steps in references/auth.md to resolve the API key and base URL.
3. Upload the file
Run:
curl -s -w '\n%{http_code}' -X POST \
-F "file=@\"<resolved_path>\"" \
-H "Authorization: Bearer <api_key>" \
<base_url>/uploadThe -w '\n%{http_code}' appends the HTTP status code on a separate line. Parse the last line as the status code and everything before it as the response body.
4. Handle the response
Success (HTTP 201) — the response body is:
{
"id": "img_...",
"url": "https://cdn.labnocturne.com/...",
"size": 123456,
"mime_type": "image/png",
"uploaded_at": "2025-01-01T00:00:00Z"
}Present to the user:
- Image ID: the
idfield - CDN URL: the
urlfield - Size: the
sizefield, formatted as human-readable (e.g. "1.2 MB")
Error — see references/auth.md for common error codes. Additional upload-specific codes:
code | Suggested fix |
missing_file | Internal skill error — report to user |
file_size_exceeded | Test keys are limited to 10MB, live keys to 100MB. Compress the image or upgrade. Use /stats to check current usage |
quota_exceeded | Storage quota full. Use /files to find old uploads, then /delete <id> to free space, or upgrade |
unsupported_file_type | Only jpg, png, gif, webp, svg are supported |
upload_failed | Server error — try again in a moment |
If the server returns a non-JSON response or an unexpected HTTP status (e.g. 502, 503), tell the user the API may be temporarily unavailable and suggest retrying.
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.

