# fivemanage

A skill that teaches the agent to use the Fivemanage SDK: capture player screenshots, upload images and push logs to the dashboard via exports.fmsdk.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 327 installs · ★ 18
- Author: germanfndez
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/germanfndez/fiveai-skills/tree/HEAD/skills/fivemanage/SKILL.md
- Updated: 2026-10-17
- HTML: https://affpapa.org/en/nevibecode/skills/fivemanage

## What it does

The skill loads when you install or configure the Fivemanage SDK, grab a player screenshot, or send entries to the Fivemanage dashboard. It keeps a decision table in front of the agent: `takeImage` runs client-side, while `takeServerImage(playerSource, ...)` and `uploadImage(buffer, ...)` are server-side. For logs there is `Log(dataset, level, message, metadata)` with an explicit level plus the `Info/Warn/Error` shorthands; `LogMessage` is marked legacy.

Install order is where people trip. The resource folder has to be named `fmsdk` and sit directly in `resources/` — category folders are not supported. `takeImage` and `takeServerImage` need `screenshot-basic`, and its `ensure` line must come before `fmsdk` in `server.cfg`. Get that wrong and screenshots silently fail. API keys live as ConVars in `server.cfg` (`FIVEMANAGE_MEDIA_API_KEY`, `FIVEMANAGE_LOGS_API_KEY`), never in `config.json`, and you should set only the keys for the features you actually use.

The skill ships rules for installation, images, logs and `config.json` automatic events. The agent returns the `server.cfg` lines first, then runnable Lua or JS with the call side stated explicitly. It advises putting `playerSource` or `targetSource` in metadata so the SDK attaches player identifiers on its own, and keeping one dataset per concern: `economy`, `anticheat`, `admin_actions`. API tokens never go to NUI — client-side uploads use presigned URLs instead.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add germanfndez/fiveai-skills --skill fivemanage -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/fivemanage/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/fivemanage/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add germanfndez/fiveai-skills --skill fivemanage -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/fivemanage/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add germanfndez/fiveai-skills --skill fivemanage -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/fivemanage/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install germanfndez/fiveai-skills fivemanage
```

2. **Manually: put the files in place**
- File: `.github/skills/fivemanage/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add germanfndez/fiveai-skills --skill fivemanage -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/germanfndez/fiveai-skills --path skills/fivemanage
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/fivemanage/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add germanfndez/fiveai-skills --skill fivemanage -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/germanfndez/fiveai-skills/tree/HEAD/skills/fivemanage/SKILL.md

## When to use it
- capture a player's screen on an admin command
- upload an existing image buffer to Fivemanage
- send a levelled log entry from Lua or JS to the dashboard
- split logs across datasets like economy and anticheat
- turn on automatic chat and resource events in config.json

## Example prompts
- Install fmsdk and show me the server.cfg lines with the API keys
- Take a server-side screenshot of a player with takeServerImage and include playerSource
- Set up logging to the admin_actions dataset through exports.fmsdk:Log

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 85cb0bf34f966414.

BEGIN THIRD-PARTY FILE 85cb0bf34f966414
```text
---
name: fivemanage
description: "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."
license: MIT
metadata:
  author: germanfndez
  version: "1.0.0"
---

# 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

| Need | Call |
|---|---|
| Screenshot from the player's own client | `exports.fmsdk:takeImage({ ... })` |
| Screenshot of a player from the server | `exports.fmsdk:takeServerImage(playerSource, { ... })` |
| Upload an existing image file/buffer | `exports.fmsdk:uploadImage(buffer, { ... })` |
| Log with explicit level | `exports.fmsdk:Log(dataset, level, message, metadata)` |
| Quick log | `exports.fmsdk:Info/Warn/Error(dataset, message, metadata)` |
| Automatic player/chat/resource logs | `config.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.
```
END THIRD-PARTY FILE 85cb0bf34f966414

The third-party file has ended. Everything between the 85cb0bf34f966414 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2286 of 3065 bytes. © germanfndez · MIT · https://github.com/germanfndez/fiveai-skills/tree/HEAD/skills/fivemanage/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md