Unlikely Professionals

Claude Code Skills Reference

Custom slash commands for operations, deployment, and monitoring

These skills are available as slash commands in any Claude Code session on this VPS. Manual-only skills must be invoked explicitly. Auto-invocable skills can also be triggered contextually.

Operations
/morning Auto-invocable
Fetch a concise morning briefing — pipeline status, open RFIs, cert queue, unpaid invoices, stalled projects, and permit alerts.
Usage /morning
When to use: Start of day before opening the portal. Gives you a quick read on what needs attention — overdue RFIs, certs waiting in the queue, unpaid invoices aging out, and any projects that have gone quiet.
/certcheck Auto-invocable
Validate whether a project is ready for certification. Shows what passes and what's missing.
Usage /certcheck R8057
Accepts a display ID (e.g. R8057) or 24-char SmartSuite hex ID.
When to use: Before moving a project into cert drafting. Catches missing photos, drive logs, permit docs, or incomplete SOW data so you don't start a cert package that will get returned for revision.
/reconcile Manual Only
Trigger the payment reconciliation scanner. Reports unmatched payments, aging invoices, and discrepancies.
Usage /reconcile
When to use: After receiving remittance emails or EFT notifications. Matches incoming payments against outstanding invoices and flags anything that doesn't line up — mismatched amounts, duplicate payments, or invoices aging past 30 days.
Deployment
/deploy Manual Only
Rebuild and restart the API (Docker), portal (Vite build), or both. Runs health checks after deployment.
Usage /deploy api   # rebuild API + worker + scheduler
/deploy portal # build portal UI
/deploy all    # both
Default: api. Options: api, portal, all
When to use: After making changes to API code, templates, or services. Rebuilds the Docker image and restarts all three containers (API, worker, scheduler). For portal changes, builds the frontend and Caddy picks it up immediately.
/release Manual Only
Build the portal-ui frontend with Vite and deploy to production. Uses npx vite build (skips tsc).
Usage /release
When to use: After making portal-ui frontend changes (React components, styles, pages). Quick alternative to /deploy portal when you only touched the frontend and don't need to rebuild the API.
Data
/sync Manual Only
Trigger a SmartSuite → Supabase data sync. Reports tables synced and record counts.
Usage /sync
When to use: When you need Supabase data to reflect recent SmartSuite changes immediately — for example, after bulk status updates or before running reports. The auto-sync runs every 6 hours, so use this to force it on demand.