Skip to content
Back to search

nirvana-os-engine

Nirvana-OS engine: ready-to-run agentic operations. One sentence in, finished work out. Source-available engine for companies, squads and mind-clones. Runtime-agnostic: Claude Code, Codex, Gemini-CLI, Antigravity, Hermes.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/gutomec/nirvana-os-engine with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/gutomec/nirvana-os-engine'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/gutomec--nirvana-os-engine/badge.svg)](/listings/gutomec--nirvana-os-engine)

HTML

<a href="/listings/gutomec--nirvana-os-engine"><img src="/api/listings/gutomec--nirvana-os-engine/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Run the one-liner at the top of this page: the `bash` line on macOS, Linux and WSL, the PowerShell line on Windows. Node is not needed. If [Bun](https://bun.sh) is missing, the installer puts it in your user folder (`~/.bun`) without sudo or admin rights and carries on.

Before you run it:

- **macOS:** nothing to prepare. - **Windows (PowerShell):** nothing to prepare, and no administrator rights. - **Linux (Ubuntu):** `sudo apt update && sudo apt install -y curl unzip`. - **Windows with WSL (Ubuntu):** run `wsl --install` in a PowerShell opened as administrator, reboot, open the Ubuntu app and create your Linux user. Then install `curl` and `unzip` as on Linux and run the `bash` line inside Ubuntu. Your AI agent (Claude Code, Codex, Antigravity) must be installed inside Ubuntu too, and your projects belong in `~`, not under `/mnt/c`, which is slow.

What it changes on your machine:

- the engine in `~/.nirvana/skills`; - the `nirvana` skill linked into every agent runtime it finds: `~/.claude/skills`, `~/.codex/skills`, `~/.gemini/config/skills` (Antigravity), `~/.pi/agent/skills` and `~/.agents/skills` (OpenClaw); - `nrv` and `nrv-hermes` in `~/.local/bin`, plus one PATH line in your shell profile (the user PATH on Windows); - audit hooks in Claude Code, Antigravity and Codex; - the empty content folders `~/squads`, `~/businesses` and `~/businesses/_library/dna`.

Running it again is safe. **Close the terminal and open a new one** so `nrv` is on your PATH, and check with `nrv --version`. Then ask your agent: *"Check that Nirvana-OS is installed correctly."* It runs `nrv doctor`. Exit 1 means warnings only; exit 2 lists what failed.

The step-by-step guide for each system, the beta and troubleshooting are on the [documentation site](https://gutomec.github.io/nirvana-os-engine/install.html) (in Portuguese) and in [INSTALL.md](./INSTALL.md), with the other routes (the `nirvana` skill through skills.sh, installing from a clone).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 250 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. <img src="./docs/assets/banner-week1.png" alt="Nirvana-OS: one sentence in, finished work out. Parallel agent workflows converge through quality gates." width="100%">
  3. # Nirvana-OS
  4. **Ready-to-run agentic operations.** One sentence in. Finished work out.
  5. [![GitHub stars](https://img.shields.io/github/stars/gutomec/nirvana-os-engine)](https://github.com/gutomec/nirvana-os-engine/stargazers)
  6. [![version](https://img.shields.io/github/v/release/gutomec/nirvana-os-engine?label=version)](./CHANGELOG.md)
  7. [![CI](https://github.com/gutomec/nirvana-os-engine/actions/workflows/smoke.yml/badge.svg)](https://github.com/gutomec/nirvana-os-engine/actions/workflows/smoke.yml)
  8. [![license](https://img.shields.io/badge/license-SUL-lightgrey)](./LICENSE)
  9. **macOS, Linux and WSL**
  10. ```bash
  11. curl -fsSL https://gutomec.github.io/nirvana-os-engine/install.sh | bash
  12. ```
  13. **Windows (PowerShell)**
  14. ```powershell
  15. irm https://gutomec.github.io/nirvana-os-engine/install.ps1 | iex
  16. ```
  17. [Documentation](https://gutomec.github.io/nirvana-os-engine/) · [Packs](https://squads.sh/pt/packs) · [Illustrated install](https://gutomec.github.io/nirvana-os-engine/install.html) · [Beta](https://gutomec.github.io/nirvana-os-engine/beta.html) · [Changelog](./CHANGELOG.md)
  18. **Read this in your language:** [English](./README.md) · [Português](./README.pt-BR.md) · [Español](./README.es.md) · [中文](./README.zh.md) · [हिन्दी](./README.hi.md) · [العربية](./README.ar.md)
  19. </div>
  20. ---
  21. ## You talk to your agent. Your agent runs Nirvana.
  22. You already work with a terminal agent: Claude Code, Codex, Antigravity, Pi, Grok or another. One prompt gets one good answer. Real work takes a researcher, a writer, a reviewer and an operator, with a record of who did what.
  23. Nirvana-OS gives your agent that organization. You ask in plain language, and the agent uses Nirvana to pick the right businesses, squads and mind-clones, dispatch them, check what comes back and show you the receipt. You do not learn a new interface and you do not type commands day to day. The commands further down are the reference your agent uses, and they are there for you when you want them.
  24. ## What it is
  25. Nirvana-OS is a Bun-native, runtime-agnostic multi-agent system. It runs on top of the agent you already use and never replaces it. It works with three kinds of content, all of them folders on your machine:
  26. | Pillar | What it is | Where it lives |
  27. |---|---|---|
  28. | **Businesses** | Organizations with an org chart. A dispatched business runs as one agent that plays its seats, uses squads through their cards and channels mind-clones | `~/businesses/` |
  29. | **Squads** | Portable agent teams with agents, tasks and workflows the dispatched agent follows as its method | `~/squads/` |
  30. | **Mind-clones** | Persona DNA in five layers, so an agent thinks and writes with a specific expert's method | `~/businesses/_library/dna/` |
  31. The engine ships with no content. You create businesses, squads and clones by asking your agent, or you install a pack from [squads.sh](https://squads.sh/pt/packs).
  32. ## Install
  33. This README describes 0.15.4, the current **stable** release, which the one-liner at the top of this page installs. Node is not needed. If [Bun](https://bun.sh) is missing, either installer puts it in your user folder (`~/.bun`) without sudo or admin rights and carries on.
  34. Before you run it:
  35. - **macOS:** nothing to prepare.
  36. - **Windows (PowerShell):** nothing to prepare, and no administrator rights.
  37. - **Linux (Ubuntu):** `sudo apt update && sudo apt install -y curl unzip`.
  38. - **Windows with WSL (Ubuntu):** run `wsl --install` in a PowerShell opened as administrator, reboot, open the Ubuntu app and create your Linux user. Then install `curl` and `unzip` as on Linux and run the `bash` command inside Ubuntu. Your AI agent (Claude Code, Codex, Antigravity) must be installed inside Ubuntu too, and your projects belong in `~`, not under `/mnt/c`, which is slow.
  39. What it changes on your machine:
  40. - the engine in `~/.nirvana/skills`;
  41. - the `nirvana` skill linked into every agent runtime it finds: `~/.claude/skills`, `~/.codex/skills`, `~/.gemini/config/skills` (Antigravity), `~/.pi/agent/skills` and `~/.agents/skills` (OpenClaw);
  42. - `nrv` and `nrv-hermes` in `~/.local/bin`, plus one PATH line in your shell profile (the user PATH on Windows);
  43. - audit hooks in Claude Code, Antigravity and Codex;
  44. - the empty content folders `~/squads`, `~/businesses` and `~/businesses/_library/dna`.
  45. Running it again is safe. **Close the terminal and open a new one** so `nrv` is on your PATH, and check with `nrv --version`; it prints `0.15.4`. Then ask your agent: *"Check that Nirvana-OS is installed correctly."* It runs `nrv doctor`. Exit 1 means warnings only; exit 2 lists what failed.
  46. Through `curl | bash` the installer asks no questions. To pick a performance profile at install time, pass it through: replace the final `bash` with `bash -s -- --profile=balanced`. You can also set it later by asking your agent (see [Settings](#settings)).
  47. The step-by-step guide for each system is on the [documentation site](https://gutomec.github.io/nirvana-os-engine/install.html) (in Portuguese), with a [page for betas](https://gutomec.github.io/nirvana-os-engine/beta.html), and in [INSTALL.md](./INSTALL.md), with the other routes (the `nirvana` skill through skills.sh, installing from a clone).
  48. ## Start a project
  49. Open the folder you want to work in, start your agent there, and say: *"Set up this folder as a Nirvana-OS project."* The agent runs `nrv init .`, which writes `.nirvana/project.yaml` and a short note in `AGENTS.md`, `CLAUDE.md` and `GEMINI.md`. Deliverables land in `outputs/` inside the project.
  50. That note keeps your agent working as usual. It uses Nirvana only when your request calls for it:
  51. - you name it ("use Nirvana to…", "via nirvana");
  52. - you name or point to one of your businesses, squads or mind-clones ("my launch company", "the copy squad", "in Hormozi's voice"), including a pack name;
  53. - you ask for the work, or part of it, to run on another runtime ("use Codex to review it").
  54. If you want Nirvana to orchestrate every deliverable in a project, say *"orchestrate everything in this project with Nirvana"*. The agent runs `nrv init . --orchestrators=always`. Open a new session for the change to take hold. A project set up on 0.14 keeps its full contract until you run `nrv init .` again, which switches it to the on-demand note in place (`--orchestrators=always` keeps the full contract) and keeps your own lines.
  55. From then on you talk to your agent in plain language and it uses Nirvana-OS. You do not type commands day to day.
  56. ## What to ask your agent
  57. | You say | Your agent runs |
  58. |---|---|
  59. | "What businesses / squads / mind-clones do I have?" | `nrv list-businesses`, `nrv list-squads`, `nrv list-clones` |
  60. | "Use Nirvana to write the launch copy for X." | the harness: picks the business, writes a brief, `nrv dispatch … --exec` |
  61. | "Run this through the copy squad, on Codex." | `nrv dispatch --squad <slug> … --exec --runtime codex` |
  62. | "Stop that run." | `nrv run-track stop <run>` |
  63. | "Change the headline in what you delivered." | `nrv revise <project> "<change>"` |
  64. | "Show me what that run did." | `nrv audit-view <project>` |
  65. | "Install the dependencies of all my squads." | `nrv activate --all` |
  66. | "Update Nirvana-OS." | `nrv update` |
  67. | "Update my Genesis Circle pack." | `nrv update genesis-circle` |
  68. | "Put Nirvana in economy mode." | `nrv config set execution.profile economy --global` |
  69. Bigger requests work the same way:
  70. ```text
  71. Use Nirvana-OS to create a company called podcast-empire that produces, publishes,
  72. and monetizes 3 podcasts at once. Each show has its own niche, an AI host, an
  73. editorial calendar, and an independent monetization funnel. Around 7 employees.
  74. ```
  75. ```text
  76. Use Nirvana-OS to turn the public work of <author> into a complete AI mind-clone.
  77. ```
  78. ```text
  79. Use Nirvana-OS to produce a launch package: market research, landing-page copy,
  80. and a competitive teardown.
  81. ```
  82. The agent orchestrates and never writes the deliverable itself. Each business it picks gets its own brief and its own run, in parallel when the parts are independent.
  83. <div align="center">
  84. <img src="./docs/assets/nirvana-promo-en-readme.gif" alt="One prose order in, a whole AI conglomerate assembles and delivers" width="100%">
  85. </div>
  86. ## Packs
  87. Packs are curated businesses, squads and mind-clones sold on [squads.sh](https://squads.sh/pt/packs). The flagship is [Genesis Circle](https://squads.sh/pt/nirvana-os).
  88. 1. Buy the pack on squads.sh and download its zip from your dashboard.
  89. 2. Unzip the whole archive and open a terminal in the folder that holds `setup.sh`:
  90. - macOS: double-click the zip, type `cd ` in Terminal, drag the folder onto the window and press Enter;
  91. - Windows: right-click the zip, choose **Extract All**, open the folder, right-click an empty area and choose **Open in Terminal**;
  92. - Linux and WSL: `cd ~/Downloads && unzip <file>.zip -d <folder> && cd <folder>`. On WSL, first copy the zip from `/mnt/c/Users/<user>/Downloads` to `~/Downloads`.
  93. 3. Run the setup:
  94. - macOS, Linux and WSL: `bash setup.sh`
  95. - Windows: `powershell -ExecutionPolicy Bypass -File setup.ps1`
  96. Setup installs Bun if needed, installs or updates the engine, copies the content into `~/squads`, `~/businesses` and `~/businesses/_library/dna`, rebuilds the indexes and stores the pack's license in `~/.nirvana-license/packs/<pack>/`. It never replaces the engine with an older release, so a beta stays a beta.
  97. 4. Talk to your agent: *"Use Nirvana to list what the Genesis Circle pack gave me"*, then ask for work by naming a business, a squad or the pack.
  98. **Activating squads.** A squad's dependencies install on demand the first time it runs, in its own environment under `~/.nirvana/envs/<squad>`. To prepare them all up front, ask your agent: *"Activate all my Nirvana squads."* It runs `nrv activate --all`, which covers Node and Python packages, system programs, API keys and environment variables, MCP servers and models. The agent gets the list of failures with the exact command that fixes each one, and asks your permission before anything that uses `brew`, `sudo` or `winget`, and for any API key. A first run on a big pack takes several minutes.
  99. **Updating a pack.** Ask your agent to update it, or run `nrv update <pack-slug>`, for example `nrv update genesis-circle`. Components you edited are backed up under `~/.nirvana/backups/packs/<pack>/` before the update replaces them. If the update fails with a license error, download the pack again from squads.sh and run its setup once more; that also refreshes the license.
  100. ## Updating the engine
  101. Ask your agent to update Nirvana-OS, or run `nrv update`. It backs up `~/.nirvana/skills` first and keeps your settings and content. `nrv update --check` names the release it would install without changing anything.
  102. An update never moves the engine to an older release. A stable engine moves only to a newer stable, so a 0.14 engine moves to 0.15.4. A beta moves to the newest greater release, beta or stable, so a beta becomes the stable release that follows it. After an engine update, `nrv update` also checks every installed pack that has a license and says when one has a newer version.
  103. ## Betas
  104. Betas are GitHub prereleases, and the one-liner at the top never installs one. A beta is installed by pinning its tarball: replace `v<version>` below with its tag from the [release list](https://github.com/gutomec/nirvana-os-engine/releases). The tag has a leading `v`; without it the download returns 404.
  105. macOS, Linux and WSL:
  106. ```bash
  107. curl -fsSL https://gutomec.github.io/nirvana-os-engine/install.sh | NIRVANA_ENGINE_URL=https://github.com/gutomec/nirvana-os-engine/releases/download/v<version>/nirvana-os-engine.tar.gz bash
  108. ```
  109. Windows (PowerShell), as one line:
  110. ```powershell
  111. $env:NIRVANA_ENGINE_URL='https://github.com/gutomec/nirvana-os-engine/releases/download/v<version>/nirvana-os-engine.tar.gz'; irm https://gutomec.github.io/nirvana-os-engine/install.ps1 | iex
  112. ```
  113. Then, if the window is still open, run `Remove-Item Env:NIRVANA_ENGINE_URL`: while the variable is set, `nrv update` reinstalls the pinned tarball. The Windows commands use single quotes because a double quote lost in a paste leaves PowerShell waiting on `>>`.
  114. Once on a beta, `nrv update` and every pack setup keep you on the beta channel: newer betas, then the stable release that follows.
  115. **Back to stable.** On Windows, open a new PowerShell and run `Remove-Item Env:NIRVANA_ENGINE_URL`; an error saying it does not exist is fine. Run the plain one-liner from the top of this page. It installs the latest stable over the beta and keeps your content, packs and settings. Check that `nrv --version` no longer shows `beta`, then run `nrv init .` again in each project you used with the beta ([details](./INSTALL.md#back-to-stable-from-a-beta)).
  116. ## Settings
  117. Settings change when you ask. *"Put Nirvana in economy mode"*, *"maximum quality"* or *"what is configured?"* are enough; your agent runs `nrv config` and tells you what changed.
  118. A profile moves several settings at once:
  119. | Profile | Effort | Context ceiling per worker | Review | Visual checks by workers |
  120. |---|---|---|---|---|
  121. | `max` | xhigh | none (runtime default) | every delivery, up to two rounds | on |
  122. | `balanced` | high | 400k tokens | when a rule asks for it | off |
  123. | `economy` | medium | 200k tokens | only on request | off |
  124. A profile never picks the model; your runtime's own configuration does. A setting you change explicitly wins over the profile. `nrv config list` shows every setting, its value and where it came from. The full reference is [docs/configuration.md](./docs/configuration.md). Profiles exist only from 0.15 on.
  125. **Per project.** The orchestrator writes each brief with a brief template. The engine ships four: `slim` (the default: short labelled lines, the user's words kept in a file), `standard` (the six sections), `detailed` (the six plus a suggested structure, the method and one criterion per item) and `karpathy`, after Andrej Karpathy's [post on X](https://x.com/karpathy/status/2105819303471976479) and his [2025 Year in Review](https://karpathy.bearblog.dev/year-in-review-2025/): slim plus a plain-language summary, a diagram and, when it helps, an HTML explainer, at more tokens per delivery. `nrv config set briefing.template detailed --project` picks one for a project, and `nrv brief templates` lists them. To change one or add your own, say `juridico`, run `nrv brief init juridico --from standard --project`: the copy in `.nirvana/brief-templates/` wins over `~/.nirvana/brief-templates/` and over the engine's. `briefing.altitude` still works as a deprecated alias. Rules in free text go in the project's `CLAUDE.md`, `AGENTS.md` or `GEMINI.md`, above the Nirvana block that `nrv init` rewrites; your agent reads them and carries them into the briefs it writes. Asking is enough: *"in this project, use detailed briefs"*, *"add to this project's CLAUDE.md: every deliverable in Brazilian Portuguese"*.
  126. ## Why "the work is done" means something here
  127. An orchestrator can announce anything in its final message. Nirvana-OS backs each delivery with things you can open on disk.
  128. - **Audit trail.** Every dispatch, gate verdict and delivery is an append-only event in `~/.harness-logs/<date>/audit.jsonl`. Every `--exec` run also leaves a record in the project's `.nirvana/run-kernel.sqlite`. `nrv audit-view <project>` shows the chain.
  129. - **Checked on disk.** `verify-deliverable` compares what the brief promised with the files that exist, and the quality gate runs rubrics per file type, with correction rounds when it fails. A run whose serious failures survive the corrections is withheld, not delivered.
  130. - **Briefs with criteria.** Each brief carries the user's request verbatim and observable "done when" criteria; the ones marked `(blocking)` decide whether the delivery passes.
  131. - **Spend under your control.** No cost ceiling is set unless you ask for one (*"cap each run at US$ 5"* sets `budget.default_max_cost_usd`).
  132. ## Command reference
  133. For agents and power users. `nrv help` lists everything; `nrv <command> --help` gives each command's options. Full reference: [docs/CLI.md](./docs/CLI.md).
  134. | Command | What it does |
  135. |---|---|
  136. | `nrv doctor` | Health check: runtimes, hooks, skills links, dependencies, registries, licenses |
  137. | `nrv init <dir>` | Make a folder a Nirvana project (`--orchestrators=always`, `--scope=project\|merge\|global`) |
  138. | `nrv list-businesses` / `list-squads` / `list-clones` | Browse the three registries |
  139. | `nrv find "<need>"` / `nrv search "<topic>"` | Ranked candidates for a request / keyword search across the libraries |
  140. | `nrv brief template\|templates\|check\|decide\|init` | The brief the orchestrator writes for one business, from a brief template |
  141. | `nrv dispatch <business> --brief-file <file> --exec` | Run a business on a brief; `--squad <slug>[:<capability>]`, `--agent-x` or `--auto` name other targets. Refuses without `--exec` |
  142. | `nrv run-track status\|stop <run>` | Read a run's state, or stop it cleanly |
  143. | `nrv revise <project> "<change>"` | Change a delivery in the same runtime session |
  144. | `nrv audit-view <project>` | The audit chain of a run |
  145. | `nrv activate <squad>\|--all` | Prepare a squad's environment in `~/.nirvana/envs/<squad>` ahead of time |
  146. | `nrv config list\|get\|set\|unset\|explain` | Settings, with `--global` or `--project` |
  147. | `nrv update [--check]` / `nrv update <pack>` | Update the engine / a pack |
  148. | `nrv validate <squad\|business\|clone> <slug> [--fix]` | Admission gate for one entity |
  149. | `nrv glance` | Web cockpit (`--read-only` to browse only) |
  150. | `nrv uninstall --engine` | Remove the engine and keep your content |
  151. ## FAQ
  152. **Do I need to know how to code?** No. You describe outcomes in plain language; your agent runs Nirvana, and the businesses and squads write, check and deliver.
  153. **Does it replace my agent?** No. It runs on top of it. Dispatched work runs on the runtime of your session unless you name another: Claude Code, Codex, Antigravity, Pi, Kimi, Grok, Qwen Code or OpenCode.
  154. **Where does my work live?** On your machine: content in `~/businesses`, `~/squads` and `~/businesses/_library/dna`, deliverables in each project's `outputs/`. There is no Nirvana cloud in the loop.
  155. **What if nothing in my library fits?** The request still runs, on `agent-x`, the generalist. You can also ask your agent to create the business or squad that is missing.
  156. **Windows?** Native, through Bun, with no WSL needed. If you prefer WSL, install everything inside Ubuntu, your agent included.
  157. ## Troubleshooting
  158. - **PowerShell shows `>>` and waits.** A quote was left open in the paste. Press Ctrl+C or open a new window, then paste the single line again.
  159. - **macOS prints "Saving session… [Processo concluído]" after you close Terminal.** That is Terminal closing the shell, not an error.
  160. - **The install returns 404.** The tag is missing its leading `v`, or that release does not exist.
  161. - **A pack update fails with a license error.** Download the pack again from squads.sh and run its setup.
  162. - **Anything else.** `nrv doctor` checks the whole install and `nrv install --check` checks the hooks and the PATH. More in [INSTALL.md](./INSTALL.md#troubleshooting).
  163. ## License, authorship, and status
  164. Author: **Luiz Gustavo Vieira Rodrigues (gutomec / Prospecteezy)**. No co-authors.
  165. License: the Nirvana-OS Sustainable Use License (SUL) v1.0. The source is published and openly readable, and the engine is free to use. It is source-available, not an OSI-approved open-source license, and certain commercial uses require a separate commercial license. Read [LICENSE](./LICENSE) before relying on any summary, including this one.
  166. Status: beta (0.x, currently 0.15.4). The engine works today and installs in minutes. Expect the surface to keep moving until 1.0.
skills/businesses/scripts/index-businesses.cmd · Bundled script · 19 lines · 1 finding marked
  1. @echo off
  2. REM index-businesses.cmd — Windows wrapper. Runs the .ts via Bun (or Node 22+ as fallback).
  3. REM Cross-platform: this file is for Windows native (cmd.exe / PowerShell).
  4. where /q bun
  5. if %ERRORLEVEL% EQU 0 (
  6. bun "%~dp0index-businesses.ts" %*
  7. exit /b
  8. )
  9. where /q node
  10. if %ERRORLEVEL% EQU 0 (
  11. node --experimental-strip-types --no-warnings "%~dp0index-businesses.ts" %*
  12. exit /b
  13. )
  14. echo [index-businesses] FAIL: neither 'bun' nor 'node' found on PATH. >&2
  15. echo Install Bun: powershell -c "irm bun.sh/install.ps1 ^| iex" >&2
  16. exit /b 4
skills/businesses/scripts/inspect-business.cmd · Bundled script · 19 lines · 1 finding marked
  1. @echo off
  2. REM inspect-business.cmd — Windows wrapper. Runs the .ts via Bun (or Node 22+ as fallback).
  3. REM Cross-platform: this file is for Windows native (cmd.exe / PowerShell).
  4. where /q bun
  5. if %ERRORLEVEL% EQU 0 (
  6. bun "%~dp0inspect-business.ts" %*
  7. exit /b
  8. )
  9. where /q node
  10. if %ERRORLEVEL% EQU 0 (
  11. node --experimental-strip-types --no-warnings "%~dp0inspect-business.ts" %*
  12. exit /b
  13. )
  14. echo [inspect-business] FAIL: neither 'bun' nor 'node' found on PATH. >&2
  15. echo Install Bun: powershell -c "irm bun.sh/install.ps1 ^| iex" >&2
  16. exit /b 4
skills/businesses/scripts/list-businesses.cmd · Bundled script · 19 lines · 1 finding marked
  1. @echo off
  2. REM list-businesses.cmd — Windows wrapper. Runs the .ts via Bun (or Node 22+ as fallback).
  3. REM Cross-platform: this file is for Windows native (cmd.exe / PowerShell).
  4. where /q bun
  5. if %ERRORLEVEL% EQU 0 (
  6. bun "%~dp0list-businesses.ts" %*
  7. exit /b
  8. )
  9. where /q node
  10. if %ERRORLEVEL% EQU 0 (
  11. node --experimental-strip-types --no-warnings "%~dp0list-businesses.ts" %*
  12. exit /b
  13. )
  14. echo [list-businesses] FAIL: neither 'bun' nor 'node' found on PATH. >&2
  15. echo Install Bun: powershell -c "irm bun.sh/install.ps1 ^| iex" >&2
  16. exit /b 4
skills/businesses/scripts/validate-business.cmd · Bundled script · 19 lines · 1 finding marked
  1. @echo off
  2. REM validate-business.cmd — Windows wrapper. Runs the .ts via Bun (or Node 22+ as fallback).
  3. REM Cross-platform: this file is for Windows native (cmd.exe / PowerShell).
  4. where /q bun
  5. if %ERRORLEVEL% EQU 0 (
  6. bun "%~dp0validate-business.ts" %*
  7. exit /b
  8. )
  9. where /q node
  10. if %ERRORLEVEL% EQU 0 (
  11. node --experimental-strip-types --no-warnings "%~dp0validate-business.ts" %*
  12. exit /b
  13. )
  14. echo [validate-business] FAIL: neither 'bun' nor 'node' found on PATH. >&2
  15. echo Install Bun: powershell -c "irm bun.sh/install.ps1 ^| iex" >&2
  16. exit /b 4
skills/harness/scripts/decide.cmd · Bundled script · 19 lines · 1 finding marked
  1. @echo off
  2. REM decide.cmd — Windows wrapper. Runs the .ts via Bun (or Node 22+ as fallback).
  3. REM Cross-platform: this file is for Windows native (cmd.exe / PowerShell).
  4. where /q bun
  5. if %ERRORLEVEL% EQU 0 (
  6. bun "%~dp0decide.ts" %*
  7. exit /b
  8. )
  9. where /q node
  10. if %ERRORLEVEL% EQU 0 (
  11. node --experimental-strip-types --no-warnings "%~dp0decide.ts" %*
  12. exit /b
  13. )
  14. echo [decide] FAIL: neither 'bun' nor 'node' found on PATH. >&2
  15. echo Install Bun: powershell -c "irm bun.sh/install.ps1 ^| iex" >&2
  16. exit /b 4

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.