Skip to content
Back to search

advai-cli

Local-first CLI for agent skills, browser automation, knowledge bases, external CLIs, and terminal AI chat.

Safety scan

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

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/advai-x--advai-cli/badge.svg)](/listings/advai-x--advai-cli)

HTML

<a href="/listings/advai-x--advai-cli"><img src="/api/listings/advai-x--advai-cli/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.

Requirements

- Python `3.10+` - Node.js `14+` only if you install through npm - A local Python runtime is still required when using the npm package - `opencli` is required only for external CLI discovery, install, and passthrough execution - A compatible browser extension/runtime is required only if you want to use `advai browser`

Install from PyPI

pip install advai-cli

Install from npm

npm install -g advai-cli

The npm package creates a private Python virtual environment during `postinstall` and installs the matching `advai-cli` version from PyPI into that environment.

Install from Homebrew

brew tap Advai-X/tap
brew install advai-cli

Install with the bootstrap script

./install.sh

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 · 531 lines

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

  1. <p align="center">
  2. <img src="docs/assets/hero.png" alt="advai-cli hero" width="100%" />
  3. </p>
  4. <h1 align="center">advai-cli</h1>
  5. <p align="center">
  6. A unified CLI for local skills, browser automation, external CLIs, and terminal AI chat.
  7. </p>
  8. <p align="center">
  9. <a href="https://github.com/Advai-X/advai-cli/actions/workflows/ci.yml"><img src="https://github.com/Advai-X/advai-cli/actions/workflows/ci.yml/badge.svg" alt="CI" /></a>
  10. <a href="https://pypi.org/project/advai-cli/"><img src="https://img.shields.io/pypi/v/advai-cli" alt="PyPI Version" /></a>
  11. <a href="https://www.npmjs.com/package/advai-cli"><img src="https://img.shields.io/npm/v/advai-cli" alt="npm Version" /></a>
  12. <a href="https://pypi.org/project/advai-cli/"><img src="https://img.shields.io/pypi/pyversions/advai-cli" alt="Python Versions" /></a>
  13. <a href="LICENSE"><img src="https://img.shields.io/pypi/l/advai-cli" alt="License" /></a>
  14. <a href="https://github.com/Advai-X/advai-cli/stargazers"><img src="https://img.shields.io/github/stars/Advai-X/advai-cli?style=flat" alt="GitHub stars" /></a>
  15. <a href="https://github.com/Advai-X/advai-cli/issues"><img src="https://img.shields.io/github/issues/Advai-X/advai-cli" alt="GitHub issues" /></a>
  16. </p>
  17. <p align="center">
  18. <a href="#why-advai-cli">Why</a> •
  19. <a href="#installation">Installation</a> •
  20. <a href="#quick-start">Quick Start</a> •
  21. <a href="#browser-automation">Browser</a> •
  22. <a href="#common-commands">Commands</a> •
  23. <a href="#tui">TUI</a> •
  24. <a href="#development">Development</a>
  25. </p>
  26. `advai-cli` is a unified command-line interface for managing local skills, driving a Chrome extension-backed browser bridge, working with external CLIs, and chatting with AI from the terminal through a single `advai` entrypoint.
  27. It is designed as a lightweight Python-first core with npm and Homebrew distribution options, making it easy to install in different developer environments while keeping the runtime model simple, local-first, and predictable.
  28. ## Why advai-cli
  29. - One entrypoint for runtime inspection, local skill management, external CLI workflows, and terminal-native AI chat
  30. - Chrome extension-backed browser automation through `advai browser`
  31. - Python core for a small, dependency-light implementation
  32. - npm wrapper for teams that prefer JavaScript-based distribution
  33. - Homebrew formula for macOS-friendly installation
  34. - OpenAI-compatible backend support for flexible AI provider integration
  35. - Local-first state stored under `~/.advai`
  36. ## Highlights
  37. - Inspect the current installation, runtime, and recommended update command with `advai info` and `advai update`
  38. - Manage locally installed skills with install, list, info, update, and uninstall commands
  39. - Sync installed skills into platform-specific agent directories such as Cursor, Claude Code, Codex, TRAE, and more
  40. - Open, inspect, extract, and automate browser sessions with `advai browser`
  41. - Discover and install supported third-party CLIs through the OpenCLI ecosystem
  42. - Create local knowledge bases, add documents, search content, and resync from source files
  43. - Proxy supported external CLIs through `advai cli <name> ...`
  44. - Launch a terminal chat UI with configurable model, base URL, system prompt, and transcript export
  45. ## Architecture
  46. ```mermaid
  47. flowchart LR
  48. U[Developer] --> A[advai command]
  49. subgraph Distribution
  50. P[PyPI package]
  51. N[npm wrapper]
  52. B[Homebrew formula]
  53. end
  54. P --> A
  55. N --> A
  56. B --> A
  57. A --> C[Python CLI core]
  58. C --> S[Local Skills Manager]
  59. C --> BB[Browser Bridge]
  60. C --> O[OpenCLI Bridge]
  61. C --> T[Terminal TUI]
  62. C --> I[Runtime Inspection]
  63. S --> FS[~/.advai/skills]
  64. BB --> BSD[~/.advai/browser]
  65. BB --> EXT[Browser extension + local daemon]
  66. T --> API[OpenAI-compatible API]
  67. O --> OC[opencli binary]
  68. ```
  69. ## Installation
  70. ### Requirements
  71. - Python `3.10+`
  72. - Node.js `14+` only if you install through npm
  73. - A local Python runtime is still required when using the npm package
  74. - `opencli` is required only for external CLI discovery, install, and passthrough execution
  75. - A compatible browser extension/runtime is required only if you want to use `advai browser`
  76. ### Install from PyPI
  77. ```bash
  78. pip install advai-cli
  79. ```
  80. ### Install from npm
  81. ```bash
  82. npm install -g advai-cli
  83. ```
  84. The npm package creates a private Python virtual environment during `postinstall`
  85. and installs the matching `advai-cli` version from PyPI into that environment.
  86. ### Install from Homebrew
  87. ```bash
  88. brew tap Advai-X/tap
  89. brew install advai-cli
  90. ```
  91. ### Install with the bootstrap script
  92. ```bash
  93. ./install.sh
  94. ```
  95. ## Quick Start
  96. ### 1. Verify the installation
  97. ```bash
  98. advai --help
  99. advai info
  100. ```
  101. ### 2. Configure AI access
  102. ```bash
  103. export ADVAI_API_KEY=your_api_key
  104. ```
  105. ### 3. Start the terminal chat UI
  106. ```bash
  107. advai tui
  108. ```
  109. ### 4. Explore local skills and external CLIs
  110. ```bash
  111. advai skill list
  112. advai cli list
  113. ```
  114. ### 5. Verify browser automation
  115. ```bash
  116. advai browser doctor
  117. advai browser open demo https://example.com
  118. advai browser exec demo "document.title"
  119. ```
  120. ## Browser Automation
  121. `advai browser` provides a Chrome extension-backed automation layer for opening pages, executing JavaScript, waiting for selectors, interacting with inputs, reading network events, and taking screenshots.
  122. ### What it uses
  123. - `advai-cli` provides the command surface, browser bridge client, and built-in local daemon
  124. - A compatible browser extension/runtime provides the live browser connection
  125. - Browser bridge state is stored under `~/.advai/browser`
  126. - The current release uses a fixed internal extension context for browser routing
  127. ### Setup
  128. 1. Install the Chrome extension from the [Chrome Web Store](https://chromewebstore.google.com/detail/advai-cli/fnjeefdjpejiifogeplommidekkbpopn?hl=zh-CN&utm_source=ext_sidebar)
  129. 2. Make sure the local browser runtime is available on this machine
  130. 3. Open the extension once in Chrome to complete the first-run setup
  131. 4. Sign in to any sites you want to automate in that browser context
  132. 5. Run `advai browser doctor` to confirm the daemon and extension are reachable
  133. If the daemon is not already running, browser commands can auto-start the built-in advai browser daemon.
  134. ### Core workflow
  135. ```bash
  136. advai browser doctor
  137. advai browser open demo https://example.com
  138. advai browser open demo https://example.com --replace
  139. advai browser wait demo --selector "h1"
  140. advai browser exec demo "document.title"
  141. advai browser type demo "#search" "advai browser"
  142. advai browser click demo "button[type=submit]"
  143. advai browser screenshot demo --output page.png
  144. ```
  145. ### Common browser commands
  146. | Command | Description |
  147. | --- | --- |
  148. | `advai browser doctor` | Show daemon status, selected context, and connected extensions |
  149. | `advai browser extensions` | List connected extension contexts |
  150. | `advai browser open <session> <url>` | Open a URL in a named browser session |
  151. | `advai browser open <session> <url> --replace` | Reuse the current tab if the session already has one |
  152. | `advai browser navigate <session> <url>` | Navigate the current page |
  153. | `advai browser state <session>` | Show the current session state |
  154. | `advai browser exec <session> "<js>"` | Execute JavaScript in the current page |
  155. | `advai browser wait <session> --selector <css>` | Wait until a selector exists |
  156. | `advai browser click <session> <selector>` | Click an element |
  157. | `advai browser type <session> <selector> <text>` | Type text into an input |
  158. | `advai browser get <session> [--selector <css>]` | Read page or element details |
  159. | `advai browser extract <session> [code]` | Extract structured data from the page |
  160. | `advai browser screenshot <session> --output <file>` | Save a screenshot to disk |
  161. | `advai browser tabs list <session>` | List tabs for a session |
  162. | `advai browser network start <session> --pattern <text>` | Start network capture |
  163. | `advai browser network read <session>` | Read captured network events |
  164. ### Notes
  165. - Browser sessions are named explicitly, such as `demo`, `zhihu`, or `checkout-flow`
  166. - `open` creates a new tab by default; use `open --replace` to reuse the current tab for the session
  167. - Commands wait for the active internal browser context before sending automation actions
  168. - The browser bridge is local-first and does not require a remote automation service
  169. - If `doctor` reports that browser support is missing, verify that the browser extension/runtime is installed and reachable locally
  170. ## Common Commands
  171. These are the canonical commands to use in docs, screenshots, and promotional assets:
  172. ```bash
  173. advai info
  174. advai browser doctor
  175. advai browser open demo https://example.com
  176. advai skill list
  177. advai cli list
  178. advai tui
  179. ```
  180. | Command | Description |
  181. | --- | --- |
  182. | `advai --help` | Show the main command help |
  183. | `advai info` | Show runtime, installation, and environment details |
  184. | `advai update` | Print the recommended update command for the current install method |
  185. | `advai browser doctor` | Show browser bridge status and connected extension contexts |
  186. | `advai browser open <session> <url>` | Open a URL in a named browser session |
  187. | `advai browser open <session> <url> --replace` | Reuse the current tab if the session already has one |
  188. | `advai browser exec <session> "<js>"` | Execute JavaScript in the selected browser context |
  189. | `advai browser screenshot <session> --output <file>` | Save a browser screenshot to disk |
  190. | `advai tui` | Start the terminal chat interface |
  191. | `advai skill list` | List locally installed skills |
  192. | `advai skill info <name>` | Show local metadata for a skill |
  193. | `advai skill install <github-url> [--skill <name>]` | Install skill definitions from a GitHub repo |
  194. | `advai skill install <github-url> --platform <key>` | Install and sync a skill to one or more target platforms |
  195. | `advai skill update [name]` | Refresh one or all installed skills |
  196. | `advai skill uninstall <name>` | Remove an installed skill |
  197. | `advai skill sync <name> --platform <key>` | Sync an installed skill into one or more platform skills directories |
  198. | `advai skill unsync <name> --platform <key>` | Remove synced platform targets for a skill |
  199. | `advai skill platform list` | List built-in and custom skill platforms |
  200. | `advai skill platform add <key> --name <name> --path <dir>` | Register a custom skill platform |
  201. | `advai skill platform override <key> --path <dir>` | Override a platform skills directory |
  202. | `advai skill platform clear-override <key>` | Reset platform path overrides |
  203. | `advai cli list` | List installable external CLIs from OpenCLI |
  204. | `advai cli info <name>` | Show details for an external CLI |
  205. | `advai cli install <github-url> [--cli <name>]` | Register external CLI definitions from a GitHub repo |
  206. | `advai cli update <name> --yes` | Update an external CLI without confirmation |
  207. | `advai cli uninstall <name> --yes` | Uninstall an external CLI without confirmation |
  208. | `advai cli <name> ...` | Execute a supported external CLI through `advai` |
  209. | `advai kb create <name>` | Create a local knowledge base |
  210. | `advai kb doc add <name> <path>` | Copy a document into a knowledge base |
  211. | `advai kb search <name> <query>` | Search stored knowledge base documents |
  212. | `advai kb sync <name>` | Refresh stored documents from their source files |
  213. ## TUI
  214. The TUI connects to any OpenAI-compatible `/chat/completions` backend and runs entirely inside the terminal.
  215. ### Useful examples
  216. ```bash
  217. advai tui
  218. advai tui --agent default
  219. advai tui --model gpt-4o-mini
  220. advai tui --base-url https://api.openai.com/v1
  221. advai tui --system-prompt "You are a concise terminal coding assistant."
  222. advai tui --timeout 180
  223. ```
  224. ### Environment variables
  225. `advai-cli` supports both `ADVAI_*` and part of the standard `OPENAI_*` naming for compatibility.
  226. | Variable | Required | Default | Description |
  227. | --- | --- | --- | --- |
  228. | `ADVAI_API_KEY` | Yes* | none | API key for the AI backend |
  229. | `ADVAI_BASE_URL` | No | `https://api.openai.com/v1` | Base URL for an OpenAI-compatible API |
  230. | `ADVAI_AGENT` | No | `default` | Default agent used by `advai tui` |
  231. | `ADVAI_AGENTS` | No | `default` | Comma-separated agents shown by the interactive `/agent` picker |
  232. | `ADVAI_MODEL` | No | `gpt-4o-mini` | Default model used by `advai tui` |
  233. | `ADVAI_MODELS` | No | built-in model list | Comma-separated models shown by the interactive `/model` picker |
  234. | `ADVAI_SYSTEM_PROMPT` | No | built-in prompt | Initial system prompt |
  235. | `ADVAI_TIMEOUT` | No | `120` | Request timeout in seconds |
  236. | `ADVAI_SKILLS_SH_TOKEN` | No | none | Optional token for `skills.sh` API-first skill search/detail lookups; falls back to HTML when unset or unavailable |
  237. | `OPENAI_API_KEY` | Yes* | none | Fallback if `ADVAI_API_KEY` is not set |
  238. | `OPENAI_BASE_URL` | No | none | Fallback if `ADVAI_BASE_URL` is not set |
  239. | `OPENAI_MODEL` | No | none | Fallback if `ADVAI_MODEL` is not set |
  240. \* `ADVAI_API_KEY` or `OPENAI_API_KEY` must be set before running `advai tui`.
  241. ### In-session TUI commands
  242. ```bash
  243. /help
  244. /clear
  245. /agent
  246. /agent default
  247. /model
  248. /model gpt-4o-mini
  249. /system You are a helpful assistant.
  250. /save ./chat.md
  251. /exit
  252. ```
  253. Run `/agent` with no arguments to open an interactive agent picker.
  254. Run `/model` with no arguments to open an interactive model picker. Use the up and down arrow keys to choose a model, then press Enter to confirm.
  255. ## Skills
  256. Skills are stored locally under `~/.advai/skills`.
  257. ```bash
  258. advai skill list
  259. advai skill search design --source skills_sh
  260. advai skill platform list
  261. advai skill info demo-skill
  262. advai skill install https://github.com/your-org/skill-repo
  263. advai skill install https://github.com/your-org/skill-repo --skill demo-skill
  264. advai skill install https://github.com/your-org/skill-repo --skill demo-skill --platform cursor
  265. advai skill install find-skills --source skills_sh
  266. advai skill install skills.sh:vercel-labs/skills/find-skills
  267. advai skill install https://skills.sh/vercel-labs/skills/find-skills
  268. advai skill sync demo-skill --platform trae
  269. advai skill sync demo-skill --platform omp_agent --project-dir /path/to/repo
  270. advai skill unsync demo-skill --platform cursor
  271. advai skill platform add custom_agent --name "Custom Agent" --path ~/.custom-agent/skills
  272. advai skill platform override cursor --path ~/.cursor/skills
  273. advai skill update demo-skill
  274. advai skill uninstall demo-skill
  275. ```
  276. ### Supported platforms
  277. `advai skill sync --platform <key>` currently includes `51` built-in platform adapters, plus custom platform support through `advai skill platform add`.
  278. #### Coding platforms
  279. | Key | Platform |
  280. | --- | --- |
  281. | `adal` | AdaL |
  282. | `amp` | Amp |
  283. | `antigravity` | Antigravity |
  284. | `augment` | Augment |
  285. | `bob` | IBM Bob |
  286. | `claude_code` | Claude Code |
  287. | `cline` | Cline |
  288. | `codebuddy` | CodeBuddy |
  289. | `codex` | Codex |
  290. | `command_code` | Command Code |
  291. | `continue` | Continue |
  292. | `cortex` | Cortex Code |
  293. | `crush` | Crush |
  294. | `cursor` | Cursor |
  295. | `deepagents` | Deep Agents |
  296. | `droid` | Droid |
  297. | `firebender` | Firebender |
  298. | `gemini_cli` | Gemini CLI |
  299. | `github_copilot` | GitHub Copilot |
  300. | `goose` | Goose |
  301. | `grok` | Grok |
  302. | `iflow` | iFlow CLI |
  303. | `junie` | Junie |
  304. | `kilo_code` | Kilo Code |
  305. | `kimi` | Kimi Code CLI |
  306. | `kiro` | Kiro CLI |
  307. | `kode` | Kode |
  308. | `mcpjam` | MCPJam |
  309. | `mistral_vibe` | Mistral Vibe |
  310. | `mux` | Mux |
  311. | `neovate` | Neovate |
  312. | `omp_agent` | OMP Agent |
  313. | `openhands` | OpenHands |
  314. | `opencode` | OpenCode |
  315. | `pi` | Pi |
  316. | `pochi` | Pochi |
  317. | `qoder` | Qoder |
  318. | `qwen_code` | Qwen Code |
  319. | `replit` | Replit |
  320. | `roo_code` | Roo Code |
  321. | `trae` | TRAE IDE |
  322. | `trae_cn` | TRAE CN |
  323. | `warp` | Warp |
  324. | `windsurf` | Windsurf |
  325. | `zencoder` | Zencoder |
  326. #### Lobster platforms
  327. | Key | Platform |
  328. | --- | --- |
  329. | `autoclaw` | AutoClaw |
  330. | `easyclaw` | EasyClaw |
  331. | `hermes` | Hermes Agent |
  332. | `openclaw` | OpenClaw |
  333. | `qclaw` | QClaw |
  334. | `workbuddy` | WorkBuddy |
  335. #### Custom platforms
  336. - Use `advai skill platform add <key> --name <name> --path <dir>` to register any additional agent or internal platform that stores skills on disk.
  337. - Use `advai skill platform override <key> --path <dir>` or `--project-path <dir>` to adapt built-in platform paths to your local setup.
  338. Current scope:
  339. - GitHub installs read from the repository root `skills/` directory instead of copying the whole repo
  340. - If the repo `skills/` directory contains one skill, `advai` installs it automatically
  341. - If the repo `skills/` directory contains multiple skills, `advai` prompts whether to install all of them; use `--skill <name>` to choose one explicitly
  342. - `advai skill search <query>` can discover skills from provider-backed sources such as `skills.sh`
  343. - `advai skill update <name>` reuses the saved install source metadata, including provider-backed sources such as GitHub and `skills.sh`
  344. - `advai skill install` supports GitHub repository URLs, provider-prefixed specs such as `skills.sh:<owner>/<repo>/<skill>`, and `skills.sh` skill page URLs
  345. - Built-in platform adapters cover common coding and lobster-style agents, and custom platforms can be added locally
  346. - `advai skill sync` supports `symlink` and `copy` modes for writing skills into platform-specific directories
  347. - `advai skill install <github-url> --platform <key>` installs locally first, then syncs into each selected platform
  348. - `advai skill install <name> --source skills_sh` searches `skills.sh`; interactive terminals can choose from multiple matches, while `--yes` requires an unambiguous result
  349. - `skills.sh` search and detail lookups prefer the official API when `ADVAI_SKILLS_SH_TOKEN` (or `SKILLS_SH_TOKEN` / `VERCEL_OIDC_TOKEN`) is set, and fall back to public HTML pages otherwise
  350. - `skills.sh` installs currently resolve to the underlying GitHub repository and selected skill slug before local installation
  351. - `advai skill uninstall <name>` removes the local skill and cleans up any synced platform targets recorded in metadata
  352. - Platforms with project-local skills directories can be targeted with `--project-dir`
  353. ## External CLI Integration
  354. External CLI support is powered by `opencli`.
  355. ```bash
  356. advai cli list
  357. advai cli info demo-cli
  358. advai cli install https://github.com/your-org/cli-repo
  359. advai cli install https://github.com/your-org/cli-repo --cli demo-cli
  360. advai cli update demo-cli --yes
  361. advai cli uninstall demo-cli --yes
  362. advai cli demo-cli --help
  363. ```
  364. Notes:
  365. - `advai cli list`, `advai cli info`, `advai cli install`, `advai cli update`, and `advai cli uninstall` require `opencli` to be installed and available on `PATH`
  366. - GitHub CLI installs read from the repository root `clis/` directory and register each selected CLI via `opencli external register`
  367. - If the repo `clis/` directory contains multiple CLIs, `advai` prompts whether to install all of them; use `--cli <name>` to choose one explicitly
  368. - Dynamic passthrough execution works only for CLIs exposed by the local OpenCLI registry
  369. - `advai-cli` does not reimplement third-party CLIs; it provides a consistent entrypoint and installation surface
  370. ## Knowledge Bases
  371. Knowledge bases are stored locally under `~/.advai/kbs`.
  372. `advai kb` is also designed to be OKF-friendly. Based on the Open Knowledge Format (OKF) direction described by Google Cloud, the current implementation already works well with knowledge bundles that are organized as markdown files on disk, including files that contain YAML frontmatter.
  373. ```bash
  374. advai kb create team-wiki
  375. advai kb doc add team-wiki ./README.md
  376. advai kb search team-wiki homebrew
  377. advai kb sync team-wiki
  378. ```
  379. Current scope:
  380. - `advai kb create <name>` initializes a local knowledge base directory and metadata file
  381. - `advai kb doc add <name> <path>` copies a source document into the knowledge base and tracks its original path
  382. - `advai kb search <name> <query>` performs a simple case-insensitive text search over stored document content
  383. - `advai kb sync <name>` refreshes stored copies from the original source paths and reports any missing files
  384. - OKF-friendly ingestion: markdown-based knowledge docs can be added directly without conversion
  385. - YAML frontmatter is preserved as plain text, so OKF metadata remains searchable and does not get stripped during add or sync
  386. - This version does not yet implement full OKF-aware parsing, validation, or structured metadata querying; it focuses on filesystem-native storage and simple text retrieval first
  387. ## Project Structure
  388. ```text
  389. advai/
  390. ai_client.py OpenAI-compatible HTTP client
  391. browser_bridge.py Chrome extension bridge client
  392. cli.py Main CLI entrypoint
  393. cli_manager.py Install detection, update commands, OpenCLI integration
  394. kb.py Local knowledge base storage and search helpers
  395. skill_platforms.py Platform adapter registry and path resolution
  396. skills.py Local skill metadata management
  397. tui.py Terminal chat UI
  398. bin/
  399. advai.js npm bridge that launches the private Python environment
  400. install-python.js npm postinstall script that creates the private virtualenv
  401. docs/
  402. assets/
  403. hero.png README hero image
  404. Formula/
  405. advai-cli.rb Homebrew formula
  406. install.sh Bootstrap installer
  407. ```
  408. ## Development
  409. ### Run from source
  410. ```bash
  411. python -m venv .venv
  412. source .venv/bin/activate
  413. pip install -e .
  414. advai --help
  415. python -m advai.cli info
  416. ```
  417. ### Packaging model
  418. - PyPI ships the Python implementation directly
  419. - npm creates a private virtual environment and installs the matching PyPI release into it
  420. - Homebrew installs the Python package through a formula-managed virtual environment
  421. ## Operational Notes
  422. - Local state lives under `~/.advai`
  423. - Browser bridge logs and pid files are stored under `~/.advai/browser`
  424. - Knowledge bases are stored under `~/.advai/kbs`
  425. - Skills are stored under `~/.advai/skills`
  426. - The recommended self-update command changes depending on whether the tool was installed via `pip`, `npm`, or `brew`
  427. - npm installation requires Python `3.10+` and prepares a private environment during `postinstall`
  428. ## License
  429. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

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