ox-target — Claude Code skill: features and installation
This Claude Code skill builds FiveM interactions with ox_target. It activates for target options, interaction zones, or migrations from qb-target.
MIT 102 installs ★ 20 updated 2026-10-17
npx skills add germanfndez/fiveai-skills --skill ox-target -a claude-codeWhat ox-target does
The skill writes Lua code for FiveM interactions through exports.ox_target. It helps choose a target function for a local or networked entity, a model, a global target, or a zone, then shapes the options and visibility checks. For a new resource, it adds dependency lines to fxmanifest.lua.
Actions can use client-side onSelect or server-side serverEvent. The server handler must validate arguments again when an action grants money or items, or changes state. Zone and entity functions run on the client. In server.cfg, start ox_target after ox_lib. The skill does not generate qb-target syntax.
What it helps with
- add an interaction to a ped, vehicle, or door
- target every instance of a chosen model
- create a zone with interaction options
- migrate interactions from
qb-targettoox_target
Example prompts for the agent
- Add a third-eye interaction to this ped.
- Create a spherical interaction zone here.
- Migrate this
qb-targetcode toox_target.
How to install ox-target
1Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-target -a claude-code2Manually: put the files in place
~/.claude/skills/ox-target/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ox-target/
1Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-target -a codex2Manually: put the files in place
.agents/skills/ox-target/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-target -a cursor2Manually: put the files in place
.cursor/skills/ox-target/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install germanfndez/fiveai-skills skills/ox-target2Manually: put the files in place
.github/skills/ox-target/SKILL.md1Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-target -a gemini-cli2Platform CLI
gemini skills install https://github.com/germanfndez/fiveai-skills --path skills/ox-targetManually: put the files in place
.devin/skills/ox-target/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add germanfndez/fiveai-skills --skill ox-target -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-target
How do I install ox-target in Claude Code?
Run npx skills add germanfndez/fiveai-skills --skill ox-target -a claude-code. The skill file is installed at ~/.claude/skills/ox-target/SKILL.md.
What does ox-target do?
It helps write FiveM Lua interactions with exports.ox_target, including targets for entities, models, players, and zones. It also covers migration from qb-target.
What does ox-target need to work?
In server.cfg, start ox_target after ox_lib. Zone and entity functions run on the client.
Source text
SKILL.md · MIT
--- name: ox-target description: "Trigger: ox_target, third-eye, targeting, interaction zone, qb-target migration. Add targetable entities, models, players and zones with exports.ox_target." license: MIT metadata: author: germanfndez version: "1.0.0" --- # ox_target Third-eye targeting for FiveM. Replaces qb-target and bt-target. Supports ox_core, esx and qbx_core. ## Activation Contract Load this skill when the user asks to make something interactable: "press E on this ped", "third eye", "target option", "add an interaction to this vehicle/door/prop", or when migrating from qb-target. ## Hard Rules - Call every function through `exports.ox_target:<fn>(...)`. There is no global `ox_target` table. - `onSelect` runs on the CLIENT. Never trust its arguments server-side: re-validate in the `serverEvent` handler. - Always pass `name` on an option you intend to remove later. Removal is by name, not by index. - `distance` defaults to the resource default; set it explicitly for anything above ~2.5m. - Zone and entity functions are CLIENT-side only. - Prefer `addLocalEntity` for entities you spawned yourself; use `addEntity` only for networked entities and expect the id to change on respawn. ## Decision Gates | Target | Function | |---|---| | One entity you spawned locally | `addLocalEntity(entities, options)` | | A networked entity (net id) | `addEntity(entities, options)` | | Every instance of a model | `addModel(models, options)` | | Every ped / vehicle / object / player | `addGlobalPed` / `addGlobalVehicle` / `addGlobalObject` / `addGlobalPlayer` | | Everything, no filter | `addGlobalOption(options)` | | A location, not an entity | `addBoxZone` / `addSphereZone` / `addPolyZone` | ## Execution Steps 1. Confirm `ox_target` is started AFTER `ox_lib` in `server.cfg`. 2. Pick the function from the Decision Gates table. 3. Build the options array. Read rules/options.md for every allowed field. 4. Gate visibility with `groups`, `items` or `canInteract` rather than checking inside `onSelect`. 5. Route the action: `onSelect` for client logic, `serverEvent` for anything that grants money, items or state. 6. Store the returned zone id if the zone must be removed later. ## Output Contract Return runnable Lua using `exports.ox_target`. Include the `fxmanifest.lua` dependency lines when the resource is new. Never emit qb-target syntax. ## References - rules/setup.md — install, fxmanifest, convars, framework support. - rules/options.md — every field of the option table. - rules/entities.md — entity, model and global targets. - rules/zones.md — box, sphere and poly zones. - rules/migration.md — qb-target to ox_target. Upstream docs: https://overextended.dev/ox_target
© germanfndez · MIT · germanfndez/fiveai-skills