image-stats
Skill1 starsChanged 9 months agoMITView on GitHub
View image storage usage, quota, and statistics for Lab Nocturne. Check how many images are stored, how much space is used, and remaining capacity. Storage monitoring for AI agents managing hosted images and CDN assets. Use this skill whenever the user asks about storage, usage, quota, capacity, or how many images they have — even indirectly like 'am I running low on space'. Triggered by /stats or naturally.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- deleteSkill
- filesSkill
- generate-keySkill
- image-deleteSkill
- image-filesSkill
- image-keySkill
- image-uploadSkill
- statsSkill
- uploadSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Follow the steps in references/auth.md to resolve the API key and base URL.
- Very specific: line 51
If usage_percent >= 80, warn the user they are approaching their storage limit.
- Very specific: line 52
If usage_percent >= 95, strongly warn the user they are nearly out of storage and uploads may fail soon.
≈ “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
Usage Statistics
View storage usage and quota statistics for your Lab Nocturne Images account.
Invocation
/stats — also triggered naturally (e.g. "show my image stats", "how much storage am I using", "check my quota", "am I running out of space").
Instructions
1. Authenticate
Follow the steps in references/auth.md to resolve the API key and base URL.
2. Fetch statistics
Run:
curl -s -w '\n%{http_code}' \
-H "Authorization: Bearer <api_key>" \
<base_url>/statsParse 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:
{
"storage_used_bytes": 1234567,
"storage_used_mb": 1.18,
"file_count": 5,
"quota_bytes": 104857600,
"quota_mb": 100,
"usage_percent": 1.18
}Present to the user as a summary:
- Files: the
file_countvalue - Storage used: the
storage_used_mbvalue formatted with units (e.g. "1.18 MB of 100 MB") - Usage: the
usage_percentvalue with a visual indicator (e.g. "1.18% used") - If
usage_percent>= 80, warn the user they are approaching their storage limit. Suggest using/filesto review uploads and/delete <id>to free space - If
usage_percent>= 95, strongly warn the user they are nearly out of storage and uploads may fail soon. Suggest cleanup or upgrading
Error — see references/auth.md for common error codes. If the server returns a non-JSON response or an unexpected HTTP status, tell the user 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.

