fuelcheck
Fuelcheck
Check AI subscription usage across Claude, Codex, Gemini, and Antigravity from the terminal.
Pre-flight
Before running any fuelcheck command, verify it's installed:
command -v fuelcheck
If NOT found, tell the user:
fuelcheck is not installed. Install it with:
curl -fsSL https://github.com/emanuelarcos/fuelcheck/releases/latest/download/install.sh | shOr if you have Go:
go install github.com/emanuelarcos/fuelcheck/cmd/fuelcheck@latest
More from derek-x-wang/skills
life-os
>
10convex
Build full-stack TypeScript applications with Convex - a reactive backend-as-a-service with real-time database, serverless functions, and automatic caching. Use when working with Convex projects, writing queries/mutations/actions, defining schemas, using the Convex CLI, or integrating Convex with React/Next.js/Node.js applications.
4better-convex
ALWAYS use this skill when working with convex or better-convex. Covers the common end-to-end feature path using cRPC + ORM + auth + React, with setup/bootstrap and niche depth in references.
3manage-my-skills
Manage, update, and install personal agent skills from Derek-X-Wang/skills. Use when the user wants to create, edit, update, or install skills. Handles the full workflow — edit locally, commit, push, then npx skills install.
3cmux-team
Run a Claude Code agent team inside a cmux claude-teams session. Use when the current session was launched via `cmux claude-teams` and you want to spawn teammates that surface as separate cmux panels. Covers detection, the spawn → coordinate → shutdown contract, and a mode index — pick the matching `modes/<mode>.md` for the topology you actually want (feature build, AFK runner, parallel AFK runners, structured debate, parallel research).
3repo-knowledge-share
Cross-project knowledge sharing. Catalogs features and tech stacks across repos so you can reuse implementations. Use when building a feature that another project might already have, when the user asks "has any project done X?", or says "scan this project" / "update knowledge". Also triggers automatically on any invocation if the current project's knowledge is stale (>7 days since last scan).
3