hashgraph-online/awesome-codex-plugins / plugins/carsxe/carsxe-codex-plugin/skills/vehicle-specs
vehicle-specs
VerifiedFetch full vehicle specifications from a VIN using the CarsXE API. Use this when the user provides a VIN and wants to know details about a vehicle (make, model, year, engine, trim, equipment, etc.).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.2 KB |
SKILL.md
View on GitHub---
name: vehicle-specs
description: Fetch full vehicle specifications from a VIN using the CarsXE API. Use this when the user provides a VIN and wants to know details about a vehicle (make, model, year, engine, trim, equipment, etc.).
license: MIT
version: 1.0.0
author: CarsXE
---
When the user provides a VIN and asks about vehicle specs, details, or information:
1. Make an HTTP GET request to the CarsXE Specifications API:
```
GET https://api.carsxe.com/specs?key={CARSXE_API_KEY}&vin={VIN}&source=codex_plugin
```
Replace `{CARSXE_API_KEY}` with the value of the `CARSXE_API_KEY` environment variable. Optional params: `deepdata=true` for extended data, `disableIntVINDecoding=true` to skip the international VIN fallback.
2. Present the results in a clean, organized format covering:
- Basic info: Make, Model, Year, Trim
- Engine: type, cylinders, displacement, horsepower, torque
- Transmission & drivetrain
- Fuel type and economy (city/highway/combined)
- Body style, doors, seats
- Standard & optional equipment
3. A valid VIN is exactly 17 characters (letters and numbers, excluding I, O, Q).
4. If the API key is missing, tell the user to set the `CARSXE_API_KEY` environment variable (see AGENTS.md).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |