hashgraph-online/awesome-codex-plugins / plugins/carsxe/carsxe-codex-plugin/skills/auth
auth
UnverifiedSet 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.
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- If valid: proceed to step 2.
- If invalid: tell the user "That API key is invalid. Please check your key at https://api.carsxe.com/dashboard/developer" and stop.
-
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_KEYfor the current session so all skills work immediately without restarting:- Run the appropriate shell command for the user's platform to export
CARSXE_API_KEYwith the validated value.
- Run the appropriate shell command for the user's platform to export
-
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.
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: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | 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: 318k | Updated | Claude CodeCodex | Unverified | 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: 318k | Updated | Claude CodeCodex | Unverified | Install |