playbooks

home / skills / openclaw / skills / fivem

fivem skill

/skills/dktrn9ne/fivem

This skill helps you fix, validate, and convert FiveM resources for QBcore/ESX, update fxmanifest, add items, and generate SSH keys.

npx playbooks add skill openclaw/skills --skill fivem

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
3.1 KB
---
name: fivem
description: Fix, create, or validate FiveM server resources for QBCore/ESX (config.lua, fxmanifest.lua, items, housing/furniture, scripts, MLOs). Use when asked to debug resource errors, convert ESX↔QB, update fxmanifest versions, add items, or source scripts from GitHub. Also use for SSH key generation for SFTP access.
---

# FiveM (QBCore/ESX)

## Overview
Handle end‑to‑end FiveM resource work: validate/fix configs, update fxmanifest, convert ESX↔QBCore, add items, set up housing/furniture, debug errors, and scaffold simple scripts/MLO notes. Use references for checklists and patterns.

## Workflow Decision Tree
1) **Locate files**: ask for exact path or upload if not in workspace.
2) **Classify task**:
   - fxmanifest update → use `references/fxmanifest_checklist.md`
   - config.lua fix/validation → use `references/config_patterns.md`
   - ESX↔QB conversion → use `references/qb_esx_conversion.md`
   - items add/update → use `references/items.md`
   - housing/furniture → use `references/housing_furniture.md`
   - debug errors → use `references/debugging.md`
   - GitHub script search → use `references/github_search.md`
   - SSH key generation → use `references/ssh_keys.md`
3) **Apply fixes**: edit precisely, preserve structure, keep comments.
4) **Summarize changes** + provide next steps/testing.

## Core Tasks

### 1) Fix/validate config.lua
- Open file, scan for syntax errors (missing commas/brackets, mismatched quotes, duplicate keys).
- Ensure tables are properly closed and item lists are consistent.
- If unclear, ask for error logs or expected behavior.

### 2) Update fxmanifest.lua
- Normalize to recommended fxmanifest version, ensure `fx_version`, `game`, dependencies, and shared/client/server scripts are correct.
- Make sure exports/imports match resource usage.

### 3) Convert ESX ↔ QBCore
- Map framework hooks, player object access, items, jobs, money, inventory, notifications.
- Keep API differences explicit and document changes.

### 4) Add items
- Insert items into the correct shared items file for the target framework (QB/ESX). Keep weight, stack, image references consistent.

### 5) Housing/Furniture setup
- Validate furniture categories, prices, prop names, and placements; ensure config entries match resource expectations.

### 6) Debug errors
- Ask for console error snippet. Trace to file/line and fix; if a dependency is missing, flag it.

### 7) GitHub script search
- Search by resource name + framework + “fivem” + “qbcore/esx”. Provide top 3 candidates with notes.

### 8) SSH key generation (SFTP)
- Generate ed25519 keypair, provide public key for server, and safe storage guidance.

## References
- `references/fxmanifest_checklist.md`
- `references/config_patterns.md`
- `references/qb_esx_conversion.md`
- `references/items.md`
- `references/housing_furniture.md`
- `references/debugging.md`
- `references/github_search.md`
- `references/ssh_keys.md`
- `references/ox_lib.md`
- `references/menanak47.md`
- `references/qb_target.md`
- `references/qb_core.md`

Overview

This skill fixes, creates, and validates FiveM server resources for QBCore and ESX. It covers config.lua, fxmanifest.lua, item lists, housing/furniture configs, simple scripts/MLO notes, and SFTP SSH key generation. Use it to debug resource errors, convert between frameworks, update manifests, or add items safely.

How this skill works

I inspect the requested resource files or ask you to upload paths or error logs. Tasks are classified (fxmanifest, config, conversion, items, housing, debugging, GitHub search, SSH keys) and addressed with focused edits that preserve structure and comments. I summarize applied changes and provide concrete next steps and testing instructions.

When to use it

  • You have a runtime/console error pointing to a resource file.
  • You need ESX↔QBCore conversion for a script or item definitions.
  • You want fxmanifest.lua updated to correct fx_version, dependencies, or script ordering.
  • You need items, weights, or images added to shared item files.
  • You need housing/furniture configs validated or adjusted for placement and pricing.

Best practices

  • Provide the exact file paths and a console error snippet when requesting debug help.
  • Share the target framework (QBCore or ESX) and server version before conversion work.
  • Keep backups of original files; I’ll preserve structure and comments but you should keep an archive copy.
  • Test changes on a staging server and share logs for any remaining errors.
  • Supply asset references (images, model names) when adding items or furniture to avoid broken references.

Example use cases

  • Fix “attempt to index a nil value” error in config.lua by pointing to the exact line or uploading the file.
  • Convert an ESX shop script to QBCore: map player API, inventory calls, and notifications, and return a diff of edits.
  • Update fxmanifest.lua to fx_version cerulean and resolve missing dependency exports/imports.
  • Add multiple new items to shared items file with weights, stack sizes, and image entries.
  • Generate an ed25519 SSH keypair for SFTP access and provide the public key plus storage instructions.

FAQ

Can you convert complex server frameworks automatically?

I convert code patterns and provide detailed edits and notes; very large or custom frameworks may need incremental testing and manual adjustments after conversion.

What do you need to reproduce a runtime error?

A console error snippet, the resource file(s) referenced, and the fxmanifest/config files. If available, the server log and related dependency manifests speed diagnosis.