check-prerequisites

name	check-prerequisites
description	Checks prerequisites for CurseForge API workflows, including asking the user for a CurseForge API key, selecting a Python 3.12 runner, and ensuring httpx can run. Use before CurseForge skills that call the CurseForge API.

Check CurseForge Prerequisites

The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are to be interpreted as described in RFC 2119.

Workflow

1. The agent MUST ask the user for a CurseForge API key in the conversation before making CurseForge API calls.
2. If the user does not provide an API key, the agent MUST stop the CurseForge task and report that it cannot continue without the key.
3. The agent MUST NOT write the API key to disk, commit it, or include it in logs or final output.
4. The agent MUST pass the key only as an environment variable or process argument for the current command.
5. The agent MUST check for an available Python 3.12 runner before running CurseForge scripts.

Runner Selection

Use the first available option:

• If uv is available, the agent SHOULD run scripts with Python 3.12 and ephemeral httpx: uv run --no-project --python 3.12 --with httpx python <script> ...
• If pixi is available, the agent SHOULD run scripts with Python 3.12 and ephemeral httpx: pixi exec --spec python=3.12 --spec httpx python <script> ...
• If neither uv nor pixi is available, the agent MUST verify local Python 3.12 and httpx. If either is missing, the agent MUST ask the user to install dependencies before continuing.

Checks

The agent SHOULD use these commands as applicable:

uv --version
pixi --version
python --version
python -c "import httpx; print(httpx.__version__)"

Guardrails

• The agent MUST NOT make CurseForge API calls without header x-api-key=<user key> and Accept=application/json.
• The agent SHOULD prefer uv or pixi because they avoid modifying project dependencies.
• The agent MUST stop and ask the user when dependency installation is required.