Skill: lmeterx-web-loadtest#

⚠️ Intent Routing and Execution Rules (Highest Priority — Must Read)#

1. Mandatory Trigger: Whenever a user mentions "website," "webpage," "load testing," or provides a URL that appears to be a website (e.g., https://www.baidu.com), you must—and may only—use this specific Skill.
2. Prohibition on Unauthorized API Calls: This Skill is authorized to execute local scripts only; you are strictly forbidden from manually constructing HTTP requests—using tools such as curl or requests—to call any LMeterX APIs.
3. Prohibition on Fabricating Results: You must genuinely execute the provided scripts within a Bash environment and formulate your response to the user based solely on the actual console output (Stdout) generated by the script.

The Only Correct Way to Execute#

Upon receiving the user's instruction, open the terminal (Bash/Shell) and strictly execute the following complete command. To prevent authentication failures caused by empty environment variables, you must explicitly prefix the command with LMETERX_AUTH_TOKEN!

bash

export LMETERX_AUTH_TOKEN="lmeterx"
python "${SKILL_DIR}/scripts/run.py" --url "<web URL>"

If the user explicitly specifies parameters—such as the concurrency level—within the conversation, execute the task using these custom parameters:

bash

export LMETERX_AUTH_TOKEN="lmeterx"
python "${SKILL_DIR}/scripts/run.py" \
  --url "<web URL>" \
  --concurrent-users <concurrent users> \
  --duration <duration> \
  --spawn-rate <spawn rate>

Internal Mechanism Details (Execution Only—No Manual Intervention Required): The script will automatically complete the following three steps: Page Analysis, API Connectivity Pre-check, and Load Testing Task Creation. The script comes with a built-in default token— lmeterx—which is automatically injected into the X-Authorization request header and bound to the agent user.

Guidelines for Presenting Results to the User#

Upon completion of execution, please extract the terminal output and respond to the user clearly using the following Markdown format:

1. Executive Summary: The number of APIs discovered, and the count of pre-flight checks passed vs. failed.
2. Failure Classification (If Applicable): A brief summary of the reasons for any pre-flight failures (e.g., 401, 404, 5xx, etc.).
3. Successful Tasks and Report Links: List the task_id for each successfully created task, along with the corresponding URL to view the report: {LMETERX_BASE_URL}/http-results/{task_id}.

Exception Handling#

Error ScenarioOutput MessageHTTP 401/403LMeterX token is invalid or expired; please check the LMETERX_AUTH_TOKEN configuration.HTTP 5xxLMeterX platform service error; please try again later.Connection FailureUnable to connect to the LMeterX service; please check your network connection.Request TimeoutRequest timed out; the target page may be too complex.Concurrency Out of RangeConcurrency level exceeds the valid range [1, 5000].Invalid URL FormatThe URL must begin with http:// or https://.