germanfndezgermanfndez/fiveai-skills/skills/fivem-deployment/SKILL.md

fivem-deployment

Skill19 starsChanged 2 months agoMITView on GitHub

Trigger: server artifacts, FXServer, txAdmin, server.cfg, gamebuild, sv_enforceGameBuild, update server, deploy, EOL, recommended build. Pick, pin and deploy a supported FXServer build.

In this repository12 other files it gives its agents.
- skill-creatorSkill
- esx-frameworkSkill
- fivemanageSkill
- fivem-basicsSkill
- fivem-nuiSkill
- fivem-securitySkill
- lua-basicsSkill
- ox-inventorySkill
- oxlibSkill
- oxmysqlSkill
- ox-targetSkill
- qbcore-frameworkSkill

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Never state a build number from memory.
line 20
Very specific:
Never recommend sv_scriptHookAllowed true.
line 26
Distinctive:
If the current build is older than 35245, flag the October 15 2026 compatibility cutoff.
line 49

≈ “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

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 ensured 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

Fetch the lifecycle JSON for the platform (linux or win32) and read recommended, latest, support_policy, support_policy_eol.
Compare the user's current build against recommended and against its own support_policy_eol entry.
If the current build is older than 35245, flag the October 15 2026 compatibility cutoff.
Set sv_enforceGameBuild per the Legacy/Enhanced rule above, or omit it to take the default.
Audit server.cfg against rules/server-cfg.md before deploying.
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/

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