Skip to main content
skill CX Codex

fivem-deployment — Claude Code skill: setup and use

The fivem-deployment Claude Code skill selects and checks FXServer builds. It activates for server updates, server.cfg edits, or client connection problems after an update.

MIT 114 installs ★ 20 updated 2026-10-17

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add germanfndez/fiveai-skills --skill fivem-deployment -a claude-code
Open on GitHub

What fivem-deployment does

The skill helps choose an FXServer build, check its support period, and prepare server.cfg for deployment. It fetches build lifecycle data for Linux or Windows, compares the installed build with the recommended one and its EOL date, then audits the configuration.

Production servers use the recommended build; testing a new game DLC calls for the latest one. Support dates vary by build, so the skill checks the EOL entry for the version in use. If that version is below 35245, it flags the compatibility cutoff on October 15 2026.

The skill applies separate sv_enforceGameBuild rules for Legacy and Enhanced, and avoids the deprecated sv_replaceExeToSwitchBuilds. It preserves ensure order in server.cfg, with dependencies loaded before the resources that rely on them. Build checks require data from the changelogs API.

What it helps with

  • choose a recommended or latest FXServer build
  • check an installed build against its support end date
  • trace client connection failures after an update
  • audit server.cfg and resource load order
  • set sv_enforceGameBuild for Legacy or Enhanced

Example prompts for the agent

  • Choose a recommended FXServer build for production and give its support end date.
  • Find out why clients cannot connect after my FXServer update.
  • Audit my server.cfg before deployment and preserve the correct ensure order.

How to install fivem-deployment

1Skills CLI (Vercel)

npx skills add germanfndez/fiveai-skills --skill fivem-deployment -a claude-code

2Manually: put the files in place

~/.claude/skills/fivem-deployment/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/fivem-deployment/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about fivem-deployment

How do I install fivem-deployment in Claude Code?

Run npx skills add germanfndez/fiveai-skills --skill fivem-deployment -a claude-code. The skill file is placed at ~/.claude/skills/fivem-deployment/SKILL.md.

What does fivem-deployment do?

It helps select an FXServer build, check its support period, and prepare server.cfg. It activates for questions about FXServer or txAdmin updates, sv_enforceGameBuild, and client connection failures after an update.

What does fivem-deployment need to check builds?

It uses changelogs API data to read the recommended and latest builds, support policy, and EOL date.

Source text

SKILL.md · MIT
---
name: fivem-deployment
description: "Trigger: server artifacts, FXServer, txAdmin, server.cfg, gamebuild, sv_enforceGameBuild, update server, deploy, EOL, recommended build. Pick, pin and deploy a supported FXServer build."
license: MIT
metadata:
  author: germanfndez
  version: "1.0.0"
---

# FiveM Deployment

Choosing an FXServer artifact, keeping it inside its support window, and writing a server.cfg that starts.

## Activation Contract

Load this skill when the user asks which artifact to run, how to update FXServer or txAdmin, why clients cannot connect after an update, what `sv_enforceGameBuild` should be, or how to write or audit `server.cfg`.

## Hard Rules

- Never state a build number from memory. Read `recommended` and `latest` from the changelogs API before answering.
- Ignore the `critical` and `optional` fields. They are stale-pinned to build 7290 and are not maintained.
- EOL is rolling and per build. A build that works today can expire next week; check `support_policy_eol` for the exact build in use.
- `sv_replaceExeToSwitchBuilds` is deprecated as of build 35245. Never emit it.
- On Enhanced, `sv_enforceGameBuild` accepts only `1` (base game, no DLC); numeric build values are Legacy-only.
- `sv_enforceGameBuild` can only be set at startup, never at runtime.
- Never recommend `sv_scriptHookAllowed true`. It makes the server vulnerable.
- Resource load order in `server.cfg` is literal: dependencies must be `ensure`d before dependents.

## Decision Gates

| Situation | Build to pick |
|---|---|
| Production server | `recommended` from the API |
| Testing a new game DLC | `latest` |
| Currently below 35245 | Upgrade to 35245 or later before October 15 2026 |
| Build's `support_policy_eol` date has passed | Upgrade now; it is out of support |

| Symptom | Read |
|---|---|
| Clients cannot join after an update | rules/compatibility-window.md |
| Choosing or verifying a build | rules/artifacts.md |
| Server will not start / bad convar | rules/server-cfg.md |
| Updating artifacts in place | rules/txadmin.md |

## Execution Steps

1. Fetch the lifecycle JSON for the platform (`linux` or `win32`) and read `recommended`, `latest`, `support_policy`, `support_policy_eol`.
2. Compare the user's current build against `recommended` and against its own `support_policy_eol` entry.
3. If the current build is older than 35245, flag the October 15 2026 compatibility cutoff.
4. Set `sv_enforceGameBuild` per the Legacy/Enhanced rule above, or omit it to take the default.
5. Audit `server.cfg` against rules/server-cfg.md before deploying.
6. Restate the build number, its EOL value, and the source URL in the answer.

## Output Contract

Return the chosen build number, its EOL timestamp, and the API URL you read it from. Emit `server.cfg` lines as runnable `cfg` blocks with `ensure` order intact. Never invent a build number, convar, or txAdmin menu path.

## References

- rules/artifacts.md — changelogs API, recommended vs latest, rolling EOL, picking a build.
- rules/compatibility-window.md — October 15 2026 cutoff, upgrade path, deprecations.
- rules/server-cfg.md — server.cfg essentials, gamebuild, security convars.
- rules/txadmin.md — txAdmin's role in artifact updates and version pairing.

Upstream docs: https://docs.fivem.net/docs/server-manual/setting-up-a-server/

© germanfndez · MIT · germanfndez/fiveai-skills

Similar skills

All skills for DevOps and infrastructure →

From the same set12

The whole set →
lua-basics lua-basics — a skill that makes your coding agent follow Lua conventions for FiveM resources: naming, locals, tables and error handling. CX Codex +1 436installs fivemanage Teaches the agent to use the Fivemanage SDK: capture player screenshots, upload images and push logs to the dashboard via exports.fmsdk. CX Codex +1 367installs esx-framework esx-framework keeps an AI coding agent inside the ESX Legacy API when it writes FiveM resources: server and client sides, player objects, callbacks, jobs, money. CX Codex +1 319installs qbcore-framework qbcore-framework helps build FiveM resources on qb-core by generating server and client Lua code with argument validation, callback handling, and proper Player object methods. CX Codex +1 272installs oxmysql This Claude Code skill writes server-side SQL for FiveM through oxmysql. It activates for database queries and migrations from mysql-async. CX Codex +1 124installs oxlib This Claude Code skill helps write Lua code with ox_lib in FiveM resources. It activates for UI, zones, commands, and client-server requests. CX Codex +1 117installs ox-inventory This Claude Code skill guides Lua work with ox_inventory, from item changes to stashes, shops, and inventory hooks. It activates for requests to register storage or move code from qb-inventory or esx inventory. CX Codex +1 104installs ox-target This Claude Code skill builds FiveM interactions with ox_target. It activates for target options, interaction zones, or migrations from qb-target. CX Codex +1 102installs

Project sponsors

Companies that keep this analytics open