Menú
Validate Unix shell installers and npm postinstall flows honestly from a Windows host.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Resolve knowledge gaps: fetch unresolved gaps, assess sensitivity, generate research queries, ingest findings, and close gaps with a resolution slug.
Interrupt-driven alerts: detect and surface new contradictions, stale pages, resolved gaps, and embedding drift. Priority-classified with deduplication.
Ingest meeting notes, articles, documents, and conversations into Quaid. Handles idempotent ingestion for exact-byte duplicates and vault-backed sync.
Keep the brain healthy: detect and resolve contradictions via the correction / supersede workflow, validate referential integrity, triage knowledge gaps, find orphaned pages, and compact the database.
Answer questions from the brain using FTS5 + semantic search + structured queries. Synthesize across multiple pages. Cite sources.
Agent-guided binary upgrades: version check, channel detection, download via install.sh (or manual asset fetch + SHA-256 verify), and post-upgrade validation.
| name | cross-platform-installer-validation |
| description | Validate Unix shell installers and npm postinstall flows honestly from a Windows host. |
| domain | validation |
| confidence | high |
| source | earned |
Use this when install or release validation must happen on Windows while the product's primary install paths target Unix shells or Linux/macOS npm environments.
.sh files for CRLF before running them under WSL.sh can fail before any real installer logic executes.TMPDIR when invoking shell installers from WSL./tmp and use repo-local scratch directories so validation is reproducible and policy-compliant.curl (or other dependency) earlier in PATH.postinstall.js through a small harness that overrides process.platform / process.arch and mocks https.get.ENOTFOUND, 404s) when a real supported-platform npm lifecycle is unavailable.EBADPLATFORM on Windows or missing Node in WSL) separately from product blockers (missing release tags, package-name collisions).