image-key
Skill1 starsChanged 9 months agoMITView on GitHub
Generate a free test API key for Lab Nocturne image storage. No signup or email required — get an instant key with 10MB file limit and 7-day retention. Start uploading and hosting images immediately. Use this skill whenever the user wants to set up image storage, get an API key, or is getting started with Lab Nocturne — even if they just say 'I need somewhere to host images'. Triggered by /generate-key or naturally.
- Reads credentials
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- deleteSkill
- filesSkill
- generate-keySkill
- image-deleteSkill
- image-filesSkill
- image-statsSkill
- image-uploadSkill
- statsSkill
- uploadSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Use the output if set, otherwise default to https://images.labnocturne.com.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Generate Test API Key
Generate a test API key for the Lab Nocturne Images API.
Invocation
/generate-key — also triggered naturally (e.g. "get me an image storage API key", "set up image hosting", "I need somewhere to host images").
Instructions
1. Resolve the base URL
printenv LABNOCTURNE_BASE_URLUse the output if set, otherwise default to https://images.labnocturne.com.
2. Generate the key
Run:
curl -s -w '\n%{http_code}' <base_url>/keyParse the last line as the HTTP status code and everything before it as the response body.
3. Handle the response
Success (HTTP 200) — the response body is:
{
"api_key": "ln_test_...",
"type": "test",
"message": "Test key created! ...",
"limits": {
"max_file_size_mb": 10,
"storage_mb": 100,
"bandwidth_gb_per_month": 1,
"rate_limit_per_hour": 100
},
"docs": "https://images.labnocturne.com/docs"
}Present to the user:
- API Key: the
api_keyvalue - Type: the
typevalue - Limits: list each limit from the
limitsobject in human-readable form - How to use: tell the user to set
export LABNOCTURNE_API_KEY=<api_key>in their shell so other skills (/upload,/files,/stats,/delete) pick it up automatically
Error — key generation rarely fails. If it does, tell the user the error message and suggest trying again in a moment. If the server returns a non-JSON response or unexpected HTTP status, the API may be temporarily unavailable.
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.

