ox-inventory — Claude Code skill: features and install
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.
MIT 104 installs ★ 20 updated 2026-10-17
npx skills add germanfndez/fiveai-skills --skill ox-inventory -a claude-codeWhat ox-inventory does
The skill shows how to call ox_inventory exports and keep server-side changes separate from client-side display logic. Item grants and removals belong on the server; client exports handle presentation and UI choices. When code introduces an item, the skill includes its definition in data/items.lua.
For a trade, it orders the checks and changes: call CanCarryItem, take payment, run AddItem, then inspect the result. AddItem can fail when the inventory exceeds its weight limit or has no free slots. Calls use exports.ox_inventory; there is no global table.
Start ox_lib and the framework core before ox_inventory. The skill covers ox_core, esx, and qbx_core, and recommends hooks for reacting to moves, inventory openings, or purchases instead of polling.
What it helps with
- grant or remove an item on the server
- check an item's count and available capacity
- register a stash or shop
- define an item in
data/items.lua - react to inventory actions with hooks
Example prompts for the agent
- Write server-side code to grant an item and check whether it succeeded.
- Register a stash for this location in
ox_inventory. - Move this inventory logic from
qb-inventorytoox_inventory.
How to install ox-inventory
1Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-inventory -a claude-code2Manually: put the files in place
~/.claude/skills/ox-inventory/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ox-inventory/
1Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-inventory -a codex2Manually: put the files in place
.agents/skills/ox-inventory/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-inventory -a cursor2Manually: put the files in place
.cursor/skills/ox-inventory/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install germanfndez/fiveai-skills skills/ox-inventory2Manually: put the files in place
.github/skills/ox-inventory/SKILL.md1Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-inventory -a gemini-cli2Platform CLI
gemini skills install https://github.com/germanfndez/fiveai-skills --path skills/ox-inventoryManually: put the files in place
.devin/skills/ox-inventory/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-inventory -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 ox-inventory
How do I install ox-inventory in Claude Code?
Run npx skills add germanfndez/fiveai-skills --skill ox-inventory -a claude-code. The skill file is at ~/.claude/skills/ox-inventory/SKILL.md.
What does ox-inventory do?
It guides Lua code for ox_inventory items, stashes, shops, and hooks. It also distinguishes server-side inventory changes from client-side display logic.
Which frameworks does ox-inventory support?
It supports ox_core, esx, and qbx_core. ox_lib and the framework core must start before ox_inventory.
Source text
SKILL.md · MIT
--- name: ox-inventory description: "Trigger: ox_inventory, items, stash, AddItem, RemoveItem, metadata, item registration, inventory hooks, shops. Server and client exports for ox_inventory." license: MIT metadata: author: germanfndez version: "1.0.0" --- # ox_inventory Slot-based inventory with weight, metadata, stashes, shops and hooks. Supports ox_core, esx and qbx_core. ## Activation Contract Load this skill when the user asks to give, take, count or check items, register a stash or shop, define a new item, react to inventory actions, or migrate from qb-inventory or esx inventory. ## Hard Rules - Call everything through `exports.ox_inventory:<fn>(...)`. There is no global table. - Grant, remove and count items on the SERVER only. Client exports are for display and UI decisions. - `AddItem` can fail. Always check the return value: the player may be over weight or out of slots. - Check `CanCarryItem` BEFORE taking payment or removing the traded item, never after. - Never invent item names. An item must exist in `data/items.lua` or it silently fails. - `inv` is a player source, an identifier, or a stash id. Passing the wrong one returns nil, not an error. - Metadata makes items non-stackable when it differs. Do not put volatile data in metadata. ## Decision Gates | Goal | Call | |---|---| | Give an item | `AddItem(inv, item, count, metadata, slot)` | | Take an item | `RemoveItem(inv, item, count, metadata, slot)` | | Check space first | `CanCarryItem(inv, item, count, metadata)` | | How many does the player have | `GetItemCount(inv, item, metadata, strict)` | | Read one slot | `GetSlot(inv, slot)` | | Find items across slots | `Search(inv, 'slots'\|'count', item, metadata)` | | Persistent storage | `RegisterStash(...)` | | Short-lived storage | `CreateTemporaryStash(properties)` | | React to a player action | `registerHook(event, cb, options)` | ## Execution Steps 1. Confirm `ox_inventory` starts after `ox_lib` and the framework core. 2. Decide the side: mutation is server, display is client. 3. For a trade or reward, order the calls: `CanCarryItem` -> take payment -> `AddItem` -> verify the return. 4. Define any new item in `data/items.lua` before referencing it. Read rules/items.md. 5. Use hooks instead of polling when reacting to moves, opens or purchases. ## Output Contract Return runnable Lua using `exports.ox_inventory`, with the server/client split explicit. Include the `data/items.lua` entry whenever a new item is introduced. ## References - rules/server-exports.md — item and inventory functions on the server. - rules/client-exports.md — weight, current weapon, opening inventories. - rules/items.md — defining items in data/items.lua. - rules/stashes.md — stashes, shops and temporary storage. - rules/hooks.md — registerHook and cancelling actions. Upstream docs: https://overextended.dev/ox_inventory
© germanfndez · MIT · germanfndez/fiveai-skills