lark-cli-path-fix

Diagnose lark-cli PATH resolution issues across bash and zsh sessions.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/eatbreads/.agents --skill lark-cli-path-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-cli-path-fix
Source: https://github.com/eatbreads/.agents/tree/main/skills/lark-cli-path-fix
Command: npx skills add https://github.com/eatbreads/.agents --skill lark-cli-path-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Diagnose and recover a working lark-cli invocation when the tool exists on disk but the current shell cannot resolve it.

Core Features & Use Cases

  • Diagnose path-resolution issues across bash and zsh
  • Compare outputs between shells to identify PATH drift
  • Assist with project-local installations under ~/.local and common directories

Quick Start

Run the diagnostic script to verify your environment and apply the minimal fixes.

Frequently Asked Questions about lark-cli-path-fix

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

FAQPage Schema
How do I fix lark-cli command not found when the binary exists on disk?

Fix lark-cli command not found errors by diagnosing PATH drift across bash and zsh sessions. The skill verifies the binary location on disk, compares command resolution between shells, and suggests explicit export path commands to recover invocation.

Why does lark-cli work in bash but fail to resolve in zsh?

lark-cli may fail in zsh due to PATH drift in shell init files. The skill performs environment checks across bash and zsh to compare command resolution outputs, identify the configuration discrepancy, and suggest targeted path export fixes.

How to diagnose PATH drift for a project-local installation under ~/.local?

Diagnose PATH drift for project-local installations under ~/.local by running environment checks across shell sessions. The skill verifies the binary location, detects missing path exports in init files, and applies minimal fixes to restore local tool invocation.

Can I use lark-cli-path-fix to recover tool invocation across different shell sessions?

Yes, you can recover lark-cli invocation across different shell sessions. The skill applies to both bash and zsh, compares command resolution outputs between them to detect PATH drift, and suggests explicit commands or path exports to restore access.

What is the best way to resolve shell PATH drift for node and lark-cli tools?

The best way to resolve PATH drift for lark-cli is to run environment diagnostics that compare shell command resolution. The skill identifies common drift scenarios in init files and suggests minimal export fixes or zsh -lic invocations to restore the tool path.