chrome-extension-researchlisted

# Chrome extension research Compare extensions against the requested features, adoption evidence, maintenance, and access requirements. Separate observed store fields from developer claims and conclusions that would require inspecting code or runtime behavior. ## Setup Set `CRAWLORA_API_KEY` to your key from [crawlora.net](https://crawlora.net). Run the bundled `scripts/crawlora.sh` from this skill directory or by absolute path. It sends `x-api-key` to `https://api.crawlora.net/api/v1`; keep the key in the environment. Read [reference/endpoints.md](reference/endpoints.md) for selected live Chrome Web Store and stored extension tools. ## Compare current listings and observed changes 1. Establish the user's feature requirements and comparison purpose. Discover candidates with `/datasets/chrome-extensions/search`, using `item_type=extension` and `status=active` for current extensions. The dataset also includes themes, legacy apps, and unknown types; do not mix them silently. Discover category/filter values through dataset facets or live `/chromewebstore/categories`, keeping their taxonomies distinct. 2. Resolve the exact 32-character store ID, developer identity, and canonical URL. Refresh selected candidates through `/chromewebstore/item?id=...`; search and similar-item results aid discovery but do not establish equivalent functionality. 3. Retrieve `/datasets/chrome-extensions/items/{id}` and `/history/{id}` under the same dataset prefix. History i