SkillAgentSearch skills...

lacy

Talk to your shell — commands run, questions go to AI. No prefixes.

Install / Use

npx skills add lacymorrow/lacy

Installs into whichever agent you are using.

About this skill
📦

Other

Other agent config

Quality Score

82/100

Supported Platforms

Claude Code

Tags

Our assessment of lacy

lacy scores 82/100 on our quality scale, 3224th of 4,613 Development & Engineering skills we index.

Its Other is 9.6 KB long, well organised into 21 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.

It has 30 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
29/30
Structure
20/20
Description
12/15
Adoption
6/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 15 days ago, so lacy is actively maintained.
  • Our last check on 2026-10-21 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (2 minor notes below). An AI review of the same text found nothing harmful.

  • noteInstalls by piping a downloaded script into a shellline 45
    curl -fsSL https://lacy.sh/install | bash
  • noteInstalls by piping a downloaded script into a shellline 155
    curl -fsSL https://lacy.sh/install | bash -s -- --uninstall

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

lacy compared with similar skills

All 4 of these similar skills score higher than lacy; compare them before choosing.

SkillScoreStarsUpdatedFormat
lacy (this skill)by lacymorrow823015d agoOther
taste-skillby Leonxlnx100110.6k1d agoCLAUDE.md
Agent-Reachby Panniantong100109.2ktodayCLAUDE.md
headroomby headroomlabs-ai10078.9ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10069.8ktodayCLAUDE.md

Frequently asked questions

How do I install lacy?
Run npx skills add lacymorrow/lacy. The install tabs above show the steps for each supported agent.
Which AI agents does lacy work with?
It is written for Claude Code, as a Other file. Other agents that read the same format can often use it too.
Is lacy safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (2 minor notes below). An AI review of the same text found nothing harmful. It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is lacy still maintained?
The repository was last updated 15 days ago, so lacy is actively maintained.
<p align="center"> <a href="https://lacy.sh"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/lacymorrow/lacy/HEAD/.github/assets/logo-horizontal-dark.svg"> <img src="https://raw.githubusercontent.com/lacymorrow/lacy/HEAD/.github/assets/logo-horizontal.svg" alt="Lacy" width="220"> </picture> </a> </p> <p align="center"><strong>Talk to your shell.</strong> Commands run. Questions go to AI. No prefixes. No context switching. You just type.</p> <p align="center"> <a href="https://www.npmjs.com/package/lacy"><img alt="npm version" src="https://img.shields.io/npm/v/lacy?style=flat"></a> <a href="https://www.npmjs.com/package/lacy"><img alt="npm downloads" src="https://img.shields.io/npm/dm/lacy?style=flat"></a> <a href="https://github.com/lacymorrow/lacy/actions/workflows/ci.yml"><img alt="CI" src="https://img.shields.io/github/actions/workflow/status/lacymorrow/lacy/ci.yml?style=flat&label=CI"></a> <a href="https://github.com/lacymorrow/lacy/stargazers"><img alt="GitHub stars" src="https://img.shields.io/github/stars/lacymorrow/lacy?style=flat"></a> <a href="https://fsl.software"><img alt="License: FSL-1.1-MIT" src="https://img.shields.io/badge/License-FSL--1.1--MIT-blue?style=flat"></a> </p> <p align="center"> <img src="https://raw.githubusercontent.com/lacymorrow/lacy/HEAD/docs/demo-full.gif" alt="Lacy Shell demo — commands run in shell, questions go to AI" width="680" /> </p>

Why Lacy?

  • No new tools to learn — Lacy works with your existing AI CLI (Claude Code, Gemini, OpenCode, Codex, Lash). It's a complement, not a replacement.
  • Zero friction — No slash commands, no hotkeys, no separate terminal. Type naturally and Lacy routes it. A real-time color indicator shows you what will happen before you press enter.
  • Smart detection — Lacy classifies input using word analysis, not AI. It's instant. Commands like ls -la stay green (shell). Questions like what files are here turn magenta (AI). If a command fails with natural language patterns, it silently reroutes to AI.

Works with ZSH and Bash 4+ on macOS, Linux, and WSL.

Install

Supported installation methods: npm, curl, homebrew, git

Install using npx

npx lacy

Install using curl

curl -fsSL https://lacy.sh/install | bash
<details> <summary>Other methods</summary>
# Homebrew
brew tap lacymorrow/tap
brew install lacy

# Manual
git clone https://github.com/lacymorrow/lacy.git ~/.lacy
echo 'source ~/.lacy/lacy.plugin.zsh' >> ~/.zshrc
</details>

How It Works

Real-time visual feedback shows what will happen before you hit enter:

<p align="center"> <img src="https://raw.githubusercontent.com/lacymorrow/lacy/HEAD/docs/demo-indicator.gif" alt="Green indicator for shell commands, magenta for AI" width="680" /> </p>

Commands execute in your shell. Natural language goes to your AI agent. No prefixes, no context switching — you just type.

| Input | Routes to | Why | | ------------------------------ | ---------- | ------------------------------------------- | | ls -la | Shell | Valid command | | what files are here | AI | Natural language | | git status | Shell | Valid command | | do we have a way to install? | AI | Reserved word — never a real command | | fix the bug | AI | Multi-word, not a command | | kill the process on 3000 | Shell → AI | Valid command, but fails — rerouted | | go ahead and fix it | Shell → AI | "go" is valid, but "ahead" triggers reroute | | !rm -rf * | Shell | ! prefix forces shell |

The first word of your input is also syntax-highlighted in real-time: green for shell commands, magenta for AI queries.

Smart rerouting (auto mode): When a valid command contains natural language patterns (3+ bare words with articles, pronouns, etc.) and fails, lacy shows a hint and automatically re-sends it to the AI agent. Shell reserved words like do, then, in, else are routed directly to the agent — they pass command -v but are never standalone commands.

Terminal context: When you ask the AI a question, lacy automatically includes your current directory, git branch, recent commands, and exit codes, but only what changed since your last query. In supported terminals (tmux, screen, iTerm2, Terminal.app), it also captures the visible screen output so the agent can see error messages and stack traces.

Modes

<p align="center"> <img src="https://raw.githubusercontent.com/lacymorrow/lacy/HEAD/assets/mode-indicators.jpeg" alt="Shell and Agent mode indicators" width="480" /> </p>

| Mode | Behavior | Activate | | --------- | ----------------------- | ---------------------------- | | Auto | Smart routing (default) | mode auto | | Shell | Everything to shell | mode shell or Ctrl+Space | | Agent | Everything to AI | mode agent or Ctrl+Space |

Supported Tools

Lacy auto-detects your installed AI CLI. All tools handle their own auth — no API keys needed.

<p align="center"> <img src="https://raw.githubusercontent.com/lacymorrow/lacy/HEAD/assets/supported-tools.jpeg" alt="Supported AI CLI tools" width="680" /> </p>
tool set claude    # Use Claude Code
tool set lash      # Use Lash
tool set auto      # Auto-detect (first available)

Or edit ~/.lacy/config.yaml:

agent_tools:
  active: claude # lash, claude, opencode, gemini, codex, custom, or empty for auto

Commands

| Command | Description | | --------------------------- | -------------------- | | mode | Show current mode | | mode [shell\|agent\|auto] | Switch mode | | tool | Show active AI tool | | tool set <name> | Set AI tool | | ask "query" | Direct query to AI | | Ctrl+Space | Toggle between modes |

CLI

After installation, the lacy command is available (no Node required):

lacy setup        # Interactive settings (tool, mode, config)
lacy status       # Show installation status
lacy doctor       # Diagnose common issues
lacy update       # Pull latest changes
lacy config edit  # Open config in $EDITOR
lacy uninstall    # Remove Lacy Shell
lacy help         # Show all commands

Uninstall

lacy uninstall
# or
npx lacy --uninstall
# or
curl -fsSL https://lacy.sh/install | bash -s -- --uninstall

Configuration

Config file: ~/.lacy/config.yaml

agent_tools:
  active: claude # lash, claude, opencode, gemini, codex, or empty for auto

modes:
  default: auto # shell, agent, auto

api_keys:
  openai: "sk-..." # Only needed if no CLI tool installed
  anthropic: "sk-ant-..."

Troubleshooting

No AI response — Check tool to see if a tool is detected. Install one: npm i -g lashcode or brew install claude.

Colors not showing — Ensure your terminal supports 256 colors (green=34, magenta=200, blue=75).

Command rerouted unexpectedly — In auto mode, commands with natural language patterns that fail are re-sent to the AI. Switch to mode shell to disable this, or prefix with !.

Emergency bypass — Prefix any command with ! to force shell execution: !rm -rf node_modules

Releasing

Requires Bun, gh, and npm login.

bun run release          # interactive — prompts for patch/minor/major
bun run release patch    # patch bump  (1.5.3 → 1.5.4)
bun run release minor    # minor bump  (1.5.3 → 1.6.0)
bun run release major    # major bump  (1.5.3 → 2.0.0)
bun run release 2.0.0    # explicit version

The script handles the full release flow:

  1. Bumps version in both package.json files
  2. Commits with release: v<version> and tags
  3. Pushes to GitHub and creates a GitHub release
  4. Publishes the npm package (prompts for OTP if required)

Support This Project

Lacy Shell is free and open source. If it saves you time, consider sponsoring the project:

Sponsor

Your support keeps development active and helps cover infrastructure costs.

Contributors Welcome

Lacy is open source and contributions are welcome! Whether you're fixing a typo, adding a feature, or improving docs, we'd love your help.

Star History

<a href="https://star-history.com/#lacymorrow/lacy&Date"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=lacymorrow/lacy&type=Date&theme=dark" /> <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=lacymorrow/lacy&type=Date" /> <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=lacymorrow/lacy&type=Date" /> </picture> </a>

License

FSL-1.1-MIT — Functional Source License v1.1 with MIT Future License (converts to MIT after 2 years). See fsl.software for the full text.

Related Skills

View on GitHub
GitHub Stars30
CategoryDevelopment
Updated15d ago
Forks3

Languages

Shell

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low1 info