Configure a CarsXE API key by validating it with the CarsXE API, saving it for future sessions, and setting it for the current session. It can also check an existing key without changing it.
Set and save the CarsXE API key. Use this when the user provides a CarsXE API key, asks to configure the plugin, or when the session starts without a key loaded.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
When the user provides a CarsXE API key or asks to configure the plugin:
Validate the key against the CarsXE API:
GET https://api.carsxe.com/v1/auth/validate?key=<USER_PROVIDED_KEY>&source=codex_plugin
Persist the validated key for future sessions by writing it to the plugin config file using Node.js:
node -e "
const fs = require('fs');
const os = require('os');
const path = require('path');
const dir = process.env.PLUGIN_DATA || process.env.CLAUDE_PLUGIN_DATA || path.join(os.homedir(), '.carsxe');
fs.mkdirSync(dir, { recursive: true });
fs.writeFileSync(path.join(dir, 'config.json'), JSON.stringify({ api_key: process.env.CARSXE_KEY_INPUT }));
console.log('Saved to ' + path.join(dir, 'config.json'));
" --env CARSXE_KEY_INPUT=<USER_PROVIDED_KEY>
This uses an environment variable to pass the key to the script, avoiding inline credential exposure.
Set CARSXE_API_KEY for the current session so all skills work immediately without restarting:
CARSXE_API_KEY with the validated value.Confirm:
"CarsXE API key validated and saved. Future sessions will load it automatically."
Verify only: If the user asks to verify their current key without changing it, call the validate endpoint with the existing CARSXE_API_KEY value and report the result.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Plan worthwhile local tasks by checking dependencies, effects, resources, and platform boundaries, then execute the exact approved plan. It can use safe parallel work or suitable Apple-silicon backends when the project exposes them.
Record deferred engineering decisions and temporary workarounds in a debt registry, with context such as effort, ongoing cost, affected area, and payoff trigger. Entries receive short labels so they can be reviewed or dropped later.
Generate or compare AI agent code for LangChain, EINO, AutoGen, AgentScope, and CrewAI using framework-specific templates, API mappings, conventions, and project structures. Reference files include verification dates to help identify potentially outdated guidance.
Investigate a reproducible bug, test failure, or unexpected page behavior, then make a narrowly scoped fix. The workflow calls for a regression test before changing code, verifies the fix, and reports remaining risks and evidence while avoiding unrelated refactoring or feature work.
Build an AI agent project through six collaborative stages, from requirements and architecture to tools, prompts, code generation, and verification. Start framework-independent, then generate a runnable project for frameworks such as LangChain, EINO, AutoGen, AgentScope, or CrewAI.
Audit a project or learning workflow for scope drift, conflicting plans, inconsistent names, and code quality concerns. The skill reads project files and code, then reports evidence, severity, and suggested next steps without changing files.