Borrow a Working CLI.
Some CLIs are already built. The N8N, Slack, and Zoom CLIs ship as numbered blueprints from the AI Build Lab Slack channel: download the markdown, hand it to Claude Code, and the install plus auth setup runs itself. Google Workspace, Firecrawl, and MacWhisper are out in the world with standard installers. Install one of these before you build your own. Inherit the plumbing, write your own skills on top.
- A working CLI for one of six services (N8N, Slack, Zoom, Google Workspace, Firecrawl, MacWhisper), installed in under 10 minutes.
- The starter skill catalog that ships with each one. Counts vary by CLI: 40 N8N skills, 33 Slack skills, 100+ Google Workspace skills.
- A decision guide for picking which CLI to install when, and the rule for when to borrow versus build your own from scratch.
Install one with Claude.
Tell Claude which CLI you want from the list below. It walks you through install, auth, and a smoke test, using the placeholder pattern for any credentials.
How this fits in the OS.
Claude Code installed, Python or Node depending on the CLI you pick, and Infisical or 1Password for the credentials each tool needs.
The AI Build Lab blueprints channel for team CLIs (Slack, N8N, Zoom), PyPI or Homebrew for the public ones (Google Workspace, Firecrawl, MacWhisper).
A working CLI for the service you want in under 10 minutes, plus the starter skills that ship with each one. Your time goes to writing workflow skills, not plumbing.
The principle.
Building a CLI from scratch is roughly a one-day job (see Build Your First CLI). That cost is worth paying when the API matters to your work and nothing pre-built fits. It's wasted when someone already shipped a clean one.
The first move on any service: check if a CLI exists. Three places to look:
- The AI Build Lab blueprints channel in Slack. Numbered blueprints (#7, #8, #10, etc.). Each ships as a markdown file. Download the file, save it locally, point Claude Code at it, and the rest runs itself.
- PyPI.
pip searchfor the service name. The team's CLIs all publish here (n8n-toolkit,slack-toolkit). - GitHub. Search for "
<service>-cli" and look for repos with stars, active commits, structured JSON output, and shipped Claude skills. The Google Workspace CLI is the gold standard reference.
If you find one and it covers what you need, install it. Write your own skills on top for the workflows specific to how you actually use the tool. That's the leverage. The plumbing is solved; you spend your time on the part only you can do.
The shelf.
Six CLIs worth knowing about. Three from the AI Build Lab team, three from the broader ecosystem. Each card below has the install command, where to get it, what it covers, and when it's the right pick.
Slack CLI Toolkit
Programmatic control over Slack from the terminal. Send messages, search channels, manage users, post files, react, run any of the 306 Slack web API methods. Posts as a named bot identity, not as you. That's the key fix vs. Slack's MCP (Claude Desktop calls these connectors), which posts as whoever connected it, so every automated message looks like it came from you.
Install: Grab Blueprint #10 from the AI Build Lab Slack blueprints channel and save the markdown file locally (any folder). Then in Claude Code, say:
Claude reads the file, installs slack-toolkit from PyPI, walks you through creating a Slack app, adding scopes, and configuring your bot token with Infisical or 1Password. The blueprint file contains the full setup walkthrough; Claude just executes it.
N8N CLI Toolkit
Full control over your N8N workflow automation instance. List workflows, debug failed executions, search 543+ nodes, export and import workflows, test webhooks, run security audits, manage credentials, switch between multiple N8N instances with one command. Zero external dependencies. Works with N8N Cloud and self-hosted.
Install: Grab Blueprint #8 from the AI Build Lab Slack blueprints channel and save the markdown file locally. Then in Claude Code, say:
Claude installs n8n-toolkit from PyPI, configures your profile with the URL and API key (using Infisical or 1Password for the key), and verifies the install with n8n-cli health. The package is also on PyPI directly if you only want the tool without the guided setup.
Zoom Automation Hub
Meeting management and transcript automation. Pull meeting recordings and transcripts via the Zoom API, route them into your knowledge base, trigger downstream skills like meeting summaries or action-item extraction. Ships with the zoom-cli.py file alongside its blueprint markdown.
Install: Grab Blueprint #5 from the AI Build Lab Slack blueprints channel and save the markdown file locally. Then in Claude Code, say:
Claude installs the CLI, sets up Zoom OAuth, and configures your credentials with Infisical or 1Password. Pairs well with MacWhisper for offline transcription of any audio the Zoom CLI pulls down.
Google Workspace CLI
One CLI for all of Google Workspace. Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, Tasks, Apps Script. Auto-discovers new APIs by reading Google's Discovery Service at runtime. 26.5k GitHub stars. Built in Rust, ships with Claude skills (the repo includes a `.claude` directory).
The most important feature: handles multiple Google accounts cleanly. Per-command credential routing, per-project defaults via CLAUDE.md, per-domain account matching. If you have a personal Google account, a work Google account, and a client Google account, this CLI is built for you.
Install:
Auth setup opens a browser for OAuth. Token is stored encrypted in your OS keyring. No real keys touch the chat.
Firecrawl CLI
Scrape any website to clean markdown. Single page, bulk crawl, or recursive site scrape. The default plumbing the workshop uses for Phase 1 of any CLI build (the API doc scraping step). Generous free tier; paid plan for Cloudflare-protected or high-volume sites.
Install:
If you don't already have it from the CLI Tool Harness blueprint (#7), grab it here. Get a free API key at firecrawl.dev. Store it in Infisical or 1Password as FIRECRAWL_API_KEY. The CLI reads it from your environment, so the real key never touches the chat.
MacWhisper
Local audio transcription. Drop in an audio file, get a transcript. Runs Whisper models locally on your Mac (no API cost, no audio leaving your device). The transcription layer behind the team's 56,000+ ingested YouTube transcripts and meeting recordings.
Install: macOS only. Download from goodsnooze.gumroad.com/l/macwhisper or via Homebrew Cask.
One-time setup. After that, transcription is a drag-and-drop or CLI flag. Pairs with the Zoom Automation Hub for full meeting capture.
When to pick which.
A quick decision guide. If your case isn't on this table, the answer is usually "the cheapest test is to install the closest CLI and see if it covers what you need before building one."
| What you're trying to do | The pick |
|---|---|
| Post messages, search history, or automate Slack workflows | Slack CLI Toolkit (Blueprint #10). Replaces the Slack MCP for anything more than basic posting. |
| Build, debug, or audit N8N workflows. Switch between cloud and self-hosted. | N8N CLI Toolkit (Blueprint #8). Especially if you run multiple N8N instances. |
| Anything Gmail, Drive, Calendar, Docs, Sheets. Especially with multiple Google accounts. | Google Workspace CLI. The multi-account handling alone is worth installing it. |
| Pull meeting transcripts and chat logs from Zoom | Zoom Automation Hub. Pairs with MacWhisper for a full meeting-capture pipeline. |
| Scrape any web page or API doc to markdown | Firecrawl CLI. The default plumbing for Phase 1 of building any other CLI. |
| Transcribe local audio (voice memos, recordings) without sending audio to an API | MacWhisper. Mac only. Runs locally. |
| Nothing on this shelf covers the service I need | Build your own. See Build Your First CLI. |
What to do after install.
Each of these CLIs ships with a starter skill set. The N8N CLI has 40 skills, the Slack CLI has 33, the Google Workspace CLI has 100+. Those cover the common operations the team has run enough times to bottle.
Your skills go on top of those. The CLIs are the plumbing. Your skills are the workflows specific to how you actually use the tool. The "after meeting" skill that pulls a Zoom transcript and posts the action items to a specific Slack channel. The "weekly digest" skill that reads your N8N execution log and emails you the failures. None of those ship with the CLI because no one but you knows where you want them to land.
Every borrowed CLI ships its starter skills already wired, so you are useful with it on day one. What no download can include is the layer that makes it yours: the workflows shaped around your channels, your naming, your cadence. Borrow the plumbing and the starters, then spend the day you saved on the part only you can write.
Where they live. Skills for a cross-project tool (Slack, Google Workspace) live globally in ~/.claude/skills/. Skills for a project-specific tool live in <project>/.claude/skills/. The same rule as the Build Your First CLI guide. Too many globally-available tools dilute the agent's selection accuracy.
Where to go next.
You have the shelf. The natural next moves: