
fivem-deployment
Trigger: server artifacts, FXServer, txAdmin, server.cfg, gamebuild, svenforceGameBuild, update server, deploy, EOL, recommended build. Pick, pin and deploy a supported FXServer build.
- Installs
- 65
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/germanfndez/fiveai-skills --skill fivem-deployment- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads fivem-deployment automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
recommendedandlatestfrom the changelogs API before answering. - Ignore the
criticalandoptionalfields. 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_eolfor the exact build in use. sv_replaceExeToSwitchBuildsis deprecated as of build 35245. Never emit it.- On Enhanced,
sv_enforceGameBuildaccepts only1(base game, no DLC); numeric build values are Legacy-only. sv_enforceGameBuildcan only be set at startup, never at runtime.- Never recommend
sv_scriptHookAllowed true. It makes the server vulnerable. - Resource load order in
server.cfgis literal: dependencies must beensured 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 (
linuxorwin32) and readrecommended,latest,support_policy,support_policy_eol. - Compare the user's current build against
recommendedand against its ownsupport_policy_eolentry. - If the current build is older than 35245, flag the October 15 2026 compatibility cutoff.
- Set
sv_enforceGameBuildper the Legacy/Enhanced rule above, or omit it to take the default. - Audit
server.cfgagainst 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/
FAQ
What does the fivem-deployment skill do?
Trigger: server artifacts, FXServer, txAdmin, server.cfg, gamebuild, svenforceGameBuild, update server, deploy, EOL, recommended build. Pick, pin and deploy a supported FXServer build.
How do I install fivem-deployment?
Run npx skills add https://github.com/germanfndez/fiveai-skills --skill fivem-deployment in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/fivem-deployment/ (personal) or .claude/skills/fivem-deployment/ (project).
Which AI agents can use fivem-deployment?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is fivem-deployment safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains fivem-deployment?
It is published by germanfndez in germanfndez/fiveai-skills. It has 65 recorded installs.
More from germanfndez/fiveai-skills
fivem-nui
germanfndez/fiveai-skills
Trigger: NUI, uipage, SendNUIMessage, SetNUIFocus, RegisterNUICallback, HTML/CSS/JS for FiveM, FiveM menu UI. Build FiveM NUI pages, wire Lua-browser messaging, callbacks and focus.
fivem-security
germanfndez/fiveai-skills
Trigger: security, anti-cheat, exploit, secure events, validate client data, server authority, distance check, rate limit, review server code. Harden FiveM net events and server-side validation.
lua-basics
germanfndez/fiveai-skills
Trigger: Lua code, Lua functions, tables, variables, conditionals, error handling, naming conventions, review Lua, optimize Lua. Write effective, performant Lua for FiveM resources.
fivemanage
germanfndez/fiveai-skills
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.
esx-framework
germanfndez/fiveai-skills
Trigger: ESX, esextended, xPlayer, PlayerData, ESX.GetPlayerFromId, ESX.RegisterServerCallback, ESX jobs, economy, inventory. Build ESX Legacy resources with server/client functions, xPlayer methods, callbacks and events.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.