Lmeterx HTTP Loadtest

Skill: lmeterx-http-loadtest

Intent Routing Rules (Highest Priority)

When to USE this Skill

• User provides a regular HTTP API URL (e.g. https://api.example.com/users, https://app.com/api/orders)
• User provides a curl command targeting a business API
• URL contains paths like /api/, /graphql, /v2/, /rest/ etc. (but NOT /v1/chat/completions or /v1/messages)
• User says "压测这个API/接口/端点" and the URL is NOT an LLM endpoint

When NOT to use this Skill

Quick Decision Rule

URL ends with /v1/chat/completions or /v1/messages → lmeterx-llm-loadtest
URL is a normal webpage (HTML page for browsers)   → lmeterx-web-loadtest
Everything else (REST/GraphQL/business API)        → THIS SKILL

Execution Rules

1. Mandatory: You must and may only execute the provided script via Bash.
2. Prohibition: Do NOT manually construct HTTP requests using curl or requests to call LMeterX APIs.
3. Prohibition: Do NOT fabricate results. Execute the script and respond based on actual stdout output.

The Only Correct Way to Execute

With URL:

export LMETERX_AUTH_TOKEN="${LMETERX_AUTH_TOKEN:-<YOUR_AUTH_TOKEN>}"
python "${SKILL_DIR}/scripts/run.py" \
  --url "<API URL>" \
  --method GET

With curl command:

export LMETERX_AUTH_TOKEN="${LMETERX_AUTH_TOKEN:-<YOUR_AUTH_TOKEN>}"
python "${SKILL_DIR}/scripts/run.py" \
  --curl '<full curl command>'

With custom load parameters:

export LMETERX_AUTH_TOKEN="${LMETERX_AUTH_TOKEN:-<YOUR_AUTH_TOKEN>}"
python "${SKILL_DIR}/scripts/run.py" \
  --url "<API URL>" \
  --method POST \
  --header "Authorization: Bearer <token>" \
  --header "Content-Type: application/json" \
  --body '{"key": "value"}' \
  --concurrent-users 100 \
  --duration 600 \
  --spawn-rate 50

Parameters

Presenting Results to the User

After execution, present:

1. Target Info: Method + URL
2. Pre-check Result: Pass/Fail with categorized failure reason
3. Task ID and Report URL: {LMETERX_BASE_URL}/http-results/{task_id}

Exception Handling