mcpField
F
fivemanage

fivemanage

github.com/germanfndezDevelopment19330 installsUpdated 2w ago
Repository

About fivemanage

A skill for configuring and using the Fivemanage SDK in FiveM, aimed at developers who handle screenshots, image uploads, and centralized logs. It clarifies client/server exports, API key setup, and metadata practices.

Key features

  1. 01Capture client and server screenshots
  2. 02Upload image files or buffers
  3. 03Send dataset-based logs
  4. 04Configure automatic event logging
  5. 05Apply API key and metadata rules

Use cases

  1. 01Capture a player's screenshot
  2. 02Upload an existing image from a server resource
  3. 03Record categorized gameplay or admin events
  4. 04Configure SDK installation and server.cfg

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/germanfndez/fiveai-skills --skill fivemanage

After installing, type/fivemanagein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
configuration.md
images.md
installation.md
logs.md
reference-links.md

Details

From the project README

Fivemanage SDK

Screenshots, image uploads and centralized logs for FiveM through exports.fmsdk.

Activation Contract

Load this skill when the user installs or configures the Fivemanage SDK, captures or uploads player screenshots, sends logs to the Fivemanage dashboard, or calls any exports.fmsdk function in Lua or JavaScript.

Hard Rules

  • The resource folder must be named fmsdk and sit directly in resources/; category folders are not supported.
  • screenshot-basic is required for takeImage / takeServerImage and must ensure BEFORE fmsdk in server.cfg.
  • API keys are ConVars in server.cfg (FIVEMANAGE_MEDIA_API_KEY, FIVEMANAGE_LOGS_API_KEY), never in config.json. Set only the keys for the features used.
  • takeImage is CLIENT-side; takeServerImage(playerSource, ...) and uploadImage(buffer, ...) are SERVER-side.
  • Log(dataset, level, message, metadata) is the primary log export; Info/Warn/Error(dataset, message, metadata) are fixed-level shorthands. LogMessage is legacy.
  • Include playerSource / targetSource in metadata so the SDK attaches player identifiers automatically.
  • Never expose API tokens to NUI; use presigned URLs for client-side uploads.

Decision Gates

NeedCall
Screenshot from the player's own clientexports.fmsdk:takeImage({ ... })
Screenshot of a player from the serverexports.fmsdk:takeServerImage(playerSource, { ... })
Upload an existing image file/bufferexports.fmsdk:uploadImage(buffer, { ... })
Log with explicit levelexports.fmsdk:Log(dataset, level, message, metadata)
Quick logexports.fmsdk:Info/Warn/Error(dataset, message, metadata)
Automatic player/chat/resource logsconfig.json inside fmsdk

Execution Steps

  1. Verify install order and ConVars (read rules/installation.md).
  2. Pick the side and export from Decision Gates.
  3. Attach metadata (name, description, playerSource) so entries are searchable.
  4. Choose a dataset per concern (economy, anticheat, admin_actions).
  5. Enable automatic events in config.json when useful (read rules/configuration.md).

Output Contract

Return the server.cfg lines when installing, then runnable Lua or JS using exports.fmsdk with the side explicit and metadata included.

References

  • rules/installation.md — download, folder placement, server.cfg order, API keys.
  • rules/images.md — takeImage, takeServerImage, uploadImage, metadata.
  • rules/logs.md — Log, Info/Warn/Error, LogMessage, datasets, identifiers.
  • rules/configuration.md — config.json, automatic events, presigned URLs.
  • rules/reference-links.md — official docs and SDK download.

Upstream docs: https://docs.fivemanage.com/fivem-sdk/installation

Comments

Markdown supported