Skip to content

hashgraph-online/awesome-codex-plugins / plugins/carsxe/carsxe-codex-plugin/skills/ymm-options

ymm-options

Unverified

List year, make, model, trim, or variant options for cascading vehicle dropdowns using the CarsXE YMM Options API. Use this when the user wants available years, makes, models, trims, or which years a vehicle was sold — not full specs.

When the user wants to browse available years, makes, models, trims, or variants (dropdowns, "what years was X sold", "which models does Toyota have in 2023"):

  1. Make an HTTP GET request to the CarsXE YMM Options API. Include only filters the user provided:
    GET https://api.carsxe.com/v1/ymm-options?key={CARSXE_API_KEY}&source=codex_plugin[&dimension={DIMENSION}][&year={YEAR}][&make={MAKE}][&model={MODEL}][&trim={TRIM}]
    
    dimension is optional: years | makes | models | trims | variants. make is required for dimension=models. model is required for dimension=trims, and for dimension=variants unless both year and make are set. trim is a substring filter (ignored for years/makes/models).
  2. If dimension is omitted, infer the next list: no filters → years; year → makes; make → models; make + model → variants.
  3. Present the single returned list. Show message if present. For bulk variants (dimension=variants + year + make, no model), mention modelCount — that is the billed unit count — and warn before making that call.
  4. Offer to fetch the next dropdown level or to run the year-make-model skill (/v1/ymm) for full specs of a chosen year/make/model.
  5. If the API key is missing, tell the user to set the CARSXE_API_KEY environment variable (see AGENTS.md).
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 318kUpdated Claude CodeCodexUnverifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexUnverifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 318kUpdated Claude CodeCodexUnverifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 318kUpdated Claude CodeCodexUnverifiedInstall