Skip to content

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

recalls-ymm

Verified

Check safety recalls by year, make, and model (no VIN) using the CarsXE Recalls by YMM API. Use this when the user asks about recalls for a model line, or has year/make/model but no VIN.

FileKindSize
SKILL.mdskill md1.3 KB
---
name: recalls-ymm
description: Check safety recalls by year, make, and model (no VIN) using the CarsXE Recalls by YMM API. Use this when the user asks about recalls for a model line, or has year/make/model but no VIN.
license: MIT
version: 1.0.0
author: CarsXE
---

When the user asks about recalls or safety issues for a year/make/model and does **not** have a VIN:

1. Make an HTTP GET request to the CarsXE Recalls by YMM API:
   ```
   GET https://api.carsxe.com/v1/recalls-ymm?key={CARSXE_API_KEY}&year={YEAR}&make={MAKE}&model={MODEL}&source=codex_plugin
   ```
   `year` must be a 4-digit model year between 1900 and the current model year plus one. If year, make, or model are missing, ask for them before calling the API.
2. Present recall details:
   - Total `recall_count` and `has_recalls`
   - For each recall: NHTSA campaign number, manufacturer, component, summary, consequence, remedy, report date
   - Highlight `park_it`, `park_outside`, or over-the-air remedy flags
3. If no recalls exist, clearly confirm the model line has no safety recalls.
4. Emphasize this is a model-line result, not a specific vehicle. If they later provide a VIN, use the `vehicle-recalls` skill (`/v1/recalls`) instead. For many VINs, use `recalls-batch`.
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: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall