From gaia-ops
Use when the user wants to verify a Gaia installation -- "probemos", "verify", "test installation", "gaia-verify"
npx claudepluginhub metraton/gaia --plugin gaia-opsThis skill uses the workspace's default tool permissions.
Verify that a Gaia installation works correctly across 4 modes. Each mode tests a different delivery surface. Use the mode that matches what was just changed or installed.
Triggers research for existing libraries, tools, and patterns before coding new features. Searches npm, PyPI, MCP/skills, GitHub; evaluates matches and decides adopt/extend/build.
Audits cross-stack repos (C++/Android/iOS/Web), classifies files as project/third-party/artifacts, detects embedded libraries, assigns module verdicts, generates interactive HTML reports.
Reorganizes X and LinkedIn networks: review-first pruning of low-value follows, priority-based add/follow recommendations, and drafts warm outreach in user's voice.
Share bugs, ideas, or general feedback.
Verify that a Gaia installation works correctly across 4 modes. Each mode tests a different delivery surface. Use the mode that matches what was just changed or installed.
"probemos" / "verify" / "test installation"
├─ Just edited source code? -> live
├─ About to publish to npm? -> dry-run
├─ Just published @beta? -> beta
└─ Just published @latest? -> release
If the user does not specify a mode, ask: "Which mode -- live, dry-run, beta, or release?"
Tests the current symlinked installation. Source code is live -- no build step.
When: After editing source files in gaia-dev/
Commands: run gaia-doctor then gaia-status directly (already installed, no npx needed).
No temp directory. No cleanup needed.
Tests the build pipeline -- does npm pack + local install produce a working installation?
When: Before publishing to npm
Step-by-step commands in reference.md. Core flow: npm pack in gaia-dev -> install .tgz in /tmp/gaia-dry-run-{timestamp} -> npx gaia-doctor + npx gaia-status -> clean up.
Tests the published @beta tag on the npm registry.
When: After publishing a beta release via the pipeline
Step-by-step commands in reference.md. Core flow: fresh /tmp/gaia-beta-verify-{timestamp} -> npm install @jaguilar87/gaia@beta -> npx gaia-doctor + npx gaia-status -> clean up.
Tests the published @latest tag on the npm registry.
When: After publishing a stable release via the pipeline
Step-by-step commands in reference.md. Core flow: fresh /tmp/gaia-release-verify-{timestamp} -> npm install @jaguilar87/gaia@latest -> npx gaia-doctor + npx gaia-status -> clean up.
Every mode ends with a structured result:
Mode: <live | dry-run | beta | release>
Version: <version string installed, or "symlinked source" for live>
Doctor: PASS | FAIL
Status: <gaia-status output summary>
Cleanup: done | n/a (live)
If gaia-doctor fails, report the exact error and stop -- do not continue to gaia-status.
/tmp/gaia-{mode}-* directories accumulate; always delete after reporting.