About this skill

Problem

When a script or agent needs to read CS2 skin data programmatically, manually checking pages is hard to reproduce. This skill turns CSQAQ API lookups into an executable flow: sync interface docs, locate the target endpoint, then call it with explicit parameters.

How It Works

It relies on CSQAQ_API_TOKEN for authentication. On first use, it syncs metadata from docs.csqaq.com and builds a local endpoint catalog. You can inspect fields such as path, method, operationId, and tags, then call the endpoint by operationId or path + method. Write-style requests can include --json-body, --body-file, or --raw-body. Typical queries include current skin price, historical price trend, market trade data, and item details.

Scope and Notes

The skill is intended for engineers who already have a CSQAQ account and understand API token usage. Treat the token as sensitive and do not commit it to repositories or log it. Re-sync local docs if CSQAQ endpoints change. It does not provide trading, payment, or forecasting; returned fields depend on the CSQAQ API.

Screenshots

Use Cases

Monitor CS2 skin prices by pulling the current market price endpoint into a local database.
Review price trends by calling the history endpoint for a selected skin over multiple days.
Verify item data by querying detailed fields such as name and category, then exporting a comparison.
Prepare a market-data script by syncing API docs and locating the target path and method.

Best For

Python engineers with a CSQAQ account who need scriptable CS2 price and trade data lookups.
Data analysts cleaning game-asset data who need item details and historical prices.
Automation engineers adding market capabilities to a trading assistant and wrapping CSQAQ API calls.
Frontend or backend engineers maintaining market dashboards who need price and trade fields from an API.