Skip to content
Back to skills

Serving

ASecurity

"Routes LightX2V FastAPI service workflows, task APIs,

  • 247 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
devopspythongoshellbashfastapiapi

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 10 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill serving --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Serving?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Serving
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-serving-f37c013b/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-serving-f37c013b)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "serving"
description: "Routes LightX2V FastAPI service workflows, task APIs,
  OpenAI-compatible image endpoints, queue inspection, and result download
  flows."
disable-model-invocation: true
metadata:
  disco-role: operating
license: Apache 2.0
---

# Serving

Use this sub-skill for any LightX2V request that goes through the HTTP service stack instead of the direct pipeline.

## Typical triggers

- "start the LightX2V server"
- "how do I call `/v1/tasks` or `/v1/images`?"
- "how do I poll task status or download the result?"
- "how do I stop a task?"
- "how do I use the sync image endpoint or presigned upload?"
- "how do I debug service status, queue pressure, or client disconnects?"

## Read first

- [`references/api-reference.md`](references/api-reference.md) for the endpoint map and request/response schemas.
- [`references/workflows.md`](references/workflows.md) for the standard start/submit/poll/download sequence and the OpenAI-compatible image flows.
- [`references/troubleshooting.md`](references/troubleshooting.md) for the expected error codes and recovery steps.
- [`scripts/start_server.sh`](scripts/start_server.sh) when you want a shell wrapper for the service entry point.
- [`../../references/troubleshooting.md`](../../references/troubleshooting.md) for cross-cutting import and dependency failures.

## What belongs here

Include:
- `python -m lightx2v.server`
- `ApiServer`, `TaskManager`, `FileService`, and the generation service layer
- `/v1/tasks`, `/v1/images`, `/v1/files`, and `/v1/service`
- image and video queueing, polling, download, and stop flows
- OpenAI-compatible image generation and edit endpoints
- presigned upload handling for synchronous image tasks
- Gradio deployments that sit on top of the same serving stack

Exclude or route elsewhere:
- direct generation without the HTTP API → `sub-skills/inference/`
- controller / encoder / transformer / decoder deployment → `sub-skills/disagg/`
- LoRA, dummy-meta, and conversion helpers → `sub-skills/conversion/`

## Safe starting checks

- `python scripts/check_install.py`
- `python -m lightx2v.server --help`
- `python sub-skills/serving/scripts/check_status.py --url http://127.0.0.1:8000`
- `bash sub-skills/serving/scripts/start_server.sh --help`

## Guidance style

Prefer concrete, user-facing instructions:
- name the endpoint and the request type
- mention whether the request is synchronous or asynchronous
- show which fields are required for images, masks, video, audio, or presigned uploads
- state the expected status transitions and final download path
- call out when a response is JSON versus a binary image/video body

## Decision points

When answering a serving question, separate the problem into these choices:
- transport: sync HTTP, async queue, or OpenAI-compatible endpoint
- media type: image, video, mask, or presigned upload response
- response shape: binary bytes, task JSON, download URL, or status JSON
- control action: poll, download, cancel, inspect queue, or inspect service metadata
- helper script: `check_status.py`, `stop_task.py`, `post_image_task.py`, `post_video_task.py`, `post_openai_image.py`, or `start_server.sh`

Common reminders:
- sync image calls only support `n=1`
- size strings must use `WxH` format for the OpenAI-compatible image API
- the result download route only works after the task reaches `completed`
- presigned uploads return JSON acknowledgment instead of raw image bytes
- the Gradio front-end is a convenience layer over the same serving stack

## What a good answer should contain

For a future agent, a strong answer from this route should usually include:
- the endpoint name and method
- whether the flow is sync or async
- the required request fields and any size / format constraints
- the expected response shape, download path, or cancellation behavior
- the helper script that matches the exact flow, when one exists

If the request is really about how to generate a model output from local code, route back to inference; if it is about how the server accepts and serves that output, keep it here.

Files in this skill

  • SKILL.md4 KB
  • references/api-reference.md3.2 KB
  • references/troubleshooting.md2.9 KB
  • references/workflows.md2.3 KB
  • scripts/check_status.py1.2 KB
  • scripts/post_image_task.py6 KB
  • scripts/post_openai_image.py3.9 KB
  • scripts/post_video_task.py5.9 KB
  • scripts/start_server.sh1.1 KB
  • scripts/stop_task.py1.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.