BF fivem
FiveM RP server engineering for QBCore, ESX, and QBox. Use for framework-level scripting, fxmanifest.lua/config.lua validation, resource debugging, dependency orchestration, MLO/streaming fixes, performance optimization (client/server), artifact/gamebuild compatibility, inventory/job/gang systems, and SSH key generation for SFTP.
FiveM RP server engineering for QBCore, ESX, and QBox.
As a process F 30/100 · Will not run — References files that are not bundled: references/fxmanifest_checklist.md, references/config_patterns.md, references/qb_esx_conversion.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/fxmanifest_checklist.md - warning
missing-refreference to a missing file: references/config_patterns.md - warning
missing-refreference to a missing file: references/qb_esx_conversion.md - warning
missing-refreference to a missing file: references/items.md - warning
missing-refreference to a missing file: references/housing_furniture.md - warning
missing-refreference to a missing file: references/debugging.md - warning
missing-refreference to a missing file: references/github_search.md - warning
missing-refreference to a missing file: references/ssh_keys.md - warning
missing-refreference to a missing file: references/ox_lib.md - warning
missing-refreference to a missing file: references/menanak47.md - warning
missing-refreference to a missing file: references/qb_target.md - warning
missing-refreference to a missing file: references/qb_core.md
Process rating: all ten parameters 30/100
- 0Tools and files. 12 referenced file(s) missing: references/fxmanifest_checklist.md, references/config_patterns.md, references/qb_esx_conversion.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (fivem) differs from the folder (fivem-dev)
- 85Steps. 108 steps, 1 vague phrases
- 100Execution cost. Instruction body is 1052 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 331: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 108 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.