flide
Installation
SKILL.md
Flide
When to use this skill
Use for the OmniJev/Flide inference engine, its CLI and System One API, not as an automatic substitute for another Jev backend. Flide uses shared state for decision questions; benchmark claims are workload and hardware dependent.
Instructions
- Read operation.md, then identify the target host, Python environment, model, GPU memory, data sensitivity and requested operation. Run
python3 "$SKILL_DIR/scripts/preflight.py"after resolvingSKILL_DIRto this skill directory; it only inspects local metadata and paths, not runtime readiness. - Before installation or execution, obtain authorization appropriate to the operation: package/model downloads and their licenses, GPU allocation, local server startup, network exposure and data sent to a model or API. Do not use credentials or accept gated model terms without authorization.
- If approved, follow the upstream install and serve examples in the reference. Bind explicitly to loopback: upstream's default is
0.0.0.0, not loopback. Do not expose the service or enable remote media fetching without explicit approval and appropriate security controls. - Submit only approved test data to the user's authorized endpoint; inspect the response and errors. Verify exact forking with
flide verifyon representative inputs when authorized. It loads a model and consumes GPU resources; it is not an offline preflight. - Report exact commands, model, environment and observed outputs. Do not infer GPU compatibility or successful inference from package presence, and do not claim the upstream performance figures as measured results.
Examples
- “Serve OneJev with Flide locally” → inspect prerequisites, ask for download/GPU/server approval, bind to
127.0.0.1, then test with approved data. - “Configure Jev's review backend” → use
jev-control-plane, not this skill unless Flide is explicitly part of the requested setup.