Fivemanage for FiveM: screenshots, logs, common mistakes and the AI skill

Fivemanage is a hosted service for FiveM servers that stores images and logs and shows them in a dashboard. You install its SDK as a resource named fmsdk, and your other resources call its exports to take screenshots, upload images and send structured logs. If you run a server and want proof attached to reports, or you want to stop grepping txAdmin console output for what a player did, this is the tool. The Fivemanage skill gives your AI assistant the real export names and the install order.

Quick reference

The export is spelled Log with a capital L. Add playerSource to the metadata so staff can filter by player.

Export	Side	What it does
exports.fmsdk:Log(datasetId, level, message, metadata)	Server	Send a log to a dataset; metadata is optional
exports.fmsdk:Info(datasetId, message, metadata)	Server	Same, with the level fixed to info
exports.fmsdk:Warn(datasetId, message, metadata)	Server	Same, with the level fixed to warn
exports.fmsdk:Error(datasetId, message, metadata)	Server	Same, with the level fixed to error
exports.fmsdk:takeImage	Client	Take a screenshot and upload it
exports.fmsdk:takeServerImage	Server	Take a screenshot of a player from the server

Install order in server.cfg: ensure screenshot-basic (only for images), then ensure fmsdk, then your resources. Set FIVEMANAGE_LOGS_API_KEY and FIVEMANAGE_MEDIA_API_KEY with set, only for the features you use.

What the Fivemanage skill gives you

The SKILL.md links to the official docs at docs.fivemanage.com and splits the topics into rule files.

• rules/installation.md. Prerequisites, download, extract into resources, the ensure order in server.cfg and where the API keys go.
• rules/images.md. Client exports.fmsdk:takeImage, server takeServerImage and uploadImage, and the metadata you attach: name, description and playerSource.
• rules/logs.md. Log, the Info, Warn and Error helpers, LogMessage, datasets, playerSource and targetSource, and automatic event logging.
• rules/configuration.md. config.json, automatic events, presigned URLs and a reminder about API keys.
• rules/reference-links.md. Official docs and SDK download links.

Both Lua and JavaScript resources can call the exports.

Common mistakes with Fivemanage

• Committing the API key or exposing it to the client. The key ends up in a public repository or in a client script anyone can dump. Symptom: strangers upload to your account or read your logs. Fix: keep keys in server.cfg or server-side config only, and never send them to the client.
• Not ensuring fmsdk before the resources that use it. Your script calls exports.fmsdk:takeImage and gets "attempt to index a nil value". Fix: put ensure fmsdk in server.cfg above every resource that depends on it.
• Calling server-only functions from the client, or the reverse. takeServerImage and uploadImage are server exports, takeImage is a client export. Symptom: nil export or an error with no upload. Fix: follow rules/images.md and put each call on the side it belongs to.
• Logging without playerSource. The event lands in the dashboard with no player attached, so staff cannot filter by who did it. Fix: pass playerSource (and targetSource when another player is involved) in the log metadata.
• Sending logs on every tick. A Log call inside a Citizen.CreateThread loop floods the dataset and burns your plan limits. Fix: log real events (purchase, ban, death, report) and use Info, Warn and Error to keep the levels meaningful.

Why AI assistants get Fivemanage wrong

Fivemanage is younger than most of the FiveM code an assistant learned from. Ask a generic model for "screenshot on report" and it invents an export like exports.fivemanage:screenshot, mixes up the resource name, or writes a webhook call instead. It also tends to put the API key in a client-side Config table because that is where older scripts kept settings. None of this shows up until the resource starts and the export is nil.

The Fivemanage skill fixes the names and the layers. The assistant reads rules/installation.md for the ensure order and key placement, rules/images.md for which export runs where, and rules/logs.md for the metadata that makes a log useful in the dashboard. The code it writes uses fmsdk exports that exist, on the side of the network where they exist.

To see how a skill compares with other FiveM AI setups, read our comparison.

Install the Fivemanage skill in 30 seconds

1. Click "Download SKILL.md" at the top of this page.
2. Unzip it into the skills or rules folder of your AI tool. The install section below shows the exact path for Claude Code, Cursor and VS Code.
3. Ask the assistant for something concrete, like "take a server screenshot when a player is banned and log it with the admin as playerSource", and check that it uses takeServerImage on the server and keeps the API key out of client code.