agentleFS
Sign inStart free
germanfndezgermanfndez/fiveai-skills/skills/fivemanage/SKILL.md

fivemanage

Skill19 starsChanged 2 months agoMITView on GitHub

Trigger: Fivemanage, fmsdk, takeImage, takeServerImage, uploadImage, Log, Info/Warn/Error, player screenshots, logs dashboard. Install and use the Fivemanage SDK for images and centralized logs.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    Never expose API tokens to NUI.

    line 26
  2. Very specific:

    Verify install order and ConVars (read rules/installation.md).

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free