fivem-dev — Claude Code skill for FiveM resource development
An orchestrator for FiveM resources on QBox, QBCore and ESX that fetches natives, framework APIs and asset models instead of guessing them.
npx skills add melihbozkurt10/fivem-dev-plugin --skill fivem-dev -a claude-codeWhat fivem-dev does
The skill targets the usual FiveM failure mode: a native or framework call gets invented, and the resource breaks on the server. The agent is told never to guess function names or parameters. When something is unclear it pulls the docs with WebFetch, and if a function does not exist it says so and suggests an alternative.
A content map keeps the agent from loading everything at once. It reads only what the request needs: framework detection, a separate file per framework (QBox, QBCore, ESX), Lua patterns, a NUI guide for HTML/CSS/JS, client-server architecture, thread management, an fxmanifest.lua reference and an ox_lib guide. For GTA V props, vehicles and peds it points you to PlebMasters Forge. Tool access is limited to read, write, edit, glob, grep, Bash and WebFetch.
Network access matters here. Without WebFetch the agent cannot verify a native or an export, so you end up checking everything by hand. Worth knowing before you rely on it in an offline setup.
What it helps with
- confirm a native's exact name and parameter order
- find the right QBox, QBCore or ESX export or event
- build a NUI menu in HTML and JS for a resource
- split logic between client and server without wasting ticks
- look up a prop or vehicle model name for spawning
Example prompts for the agent
- Verify the native for giving a weapon to a ped and show its parameters
- How do I get player data server-side in QBCore?
- Build a NUI menu with ox_lib and a progress bar
How to install fivem-dev
1Skills CLI (Vercel)
npx skills add melihbozkurt10/fivem-dev-plugin --skill fivem-dev -a claude-code2Manually: put the files in place
~/.claude/skills/fivem-dev/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fivem-dev/
1Skills CLI (Vercel)
npx skills add melihbozkurt10/fivem-dev-plugin --skill fivem-dev -a codex2Manually: put the files in place
.agents/skills/fivem-dev/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add melihbozkurt10/fivem-dev-plugin --skill fivem-dev -a cursor2Manually: put the files in place
.cursor/skills/fivem-dev/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install melihbozkurt10/fivem-dev-plugin fivem-dev2Manually: put the files in place
.github/skills/fivem-dev/SKILL.md1Skills CLI (Vercel)
npx skills add melihbozkurt10/fivem-dev-plugin --skill fivem-dev -a gemini-cli2Platform CLI
gemini skills install https://github.com/melihbozkurt10/fivem-dev-pluginManually: put the files in place
.devin/skills/fivem-dev/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add melihbozkurt10/fivem-dev-plugin --skill fivem-dev -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about fivem-dev
How do I install fivem-dev in Claude?
Run npx skills add melihbozkurt10/fivem-dev-plugin --skill fivem-dev -a claude-code. The skill file then lives at ~/.claude/skills/fivem-dev/SKILL.md.
What does fivem-dev do?
It helps you write FiveM resources for QBox, QBCore and ESX. The agent fetches natives, framework APIs and asset data from documentation rather than recalling them.
Which frameworks and languages are supported?
QBox, QBCore and ESX, plus Lua and NUI in JavaScript or TypeScript. Each framework has its own file with exports and patterns.