install-cli

Installs a system-wide wrapper for the zmail CLI via TypeScript interpreter.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cirne/zmail --skill install-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-cli
Source: https://github.com/cirne/zmail/tree/main/.cursor/skills/install-cli
Command: npx skills add https://github.com/cirne/zmail --skill install-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill installs a small wrapper script that lets you run zmail from any directory by delegating to the repository's source via npx tsx, eliminating the need to be in the project folder.

Core Features & Use Cases

  • Creates an executable wrapper at a configurable install location (e.g., ~/.local/bin/zmail) that runs the repo's src/index.ts via npx tsx.
  • Ensures PATH visibility and provides guidance for reinstalling after moving the repo.
  • Enables seamless cross-project use of zmail from any shell or workspace.

Quick Start

Run npm run install-cli to install the wrapper script to your PATH.

Frequently Asked Questions about install-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run zmail from any directory instead of the project folder?

You can run zmail from any directory by installing a CLI wrapper that delegates to the repository source via npx tsx. This eliminates the need to navigate into the project folder before executing commands.

Do I need Node.js and tsx to use a zmail CLI wrapper?

Yes, the zmail CLI wrapper requires Node.js and tsx integration to execute the repository's TypeScript source directly. It leverages npx tsx to run the source files without managing compiled binaries.

What's the best way to expose a local TypeScript CLI globally without managing binaries?

Using a wrapper script that delegates to the source via npx tsx is the best way to expose a local TypeScript CLI globally. This lightweight approach avoids managing binaries while providing consistent, cross-project access.

Why is my zmail wrapper not working after I moved the repository?

Moving the repository breaks the zmail wrapper because the script delegates to the original source path. You need to reinstall the wrapper or update the path configuration to point to the new repository location.

How does the zmail wrapper handle PATH and environment variables?

The zmail wrapper handles PATH and environment variables by configuring the executable script to respect existing PATH visibility and custom ZMAIL_HOME settings. This ensures consistent execution across different shell environments.