Cli2skill
Skill 2233admin/cli2skill
π§ Turn any CLI or MCP server into an Agent Skill β zero process overhead, 98% fewer tokens. Kill MCP zombie processes. Works with Claude Code, Codex, Gemini CLI & 26+ platforms.
npx -y skills add 2233admin/cli2skillAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Turn any CLI or MCP server into an Agent Skill. Use when you want to replace an MCP server with a zero-overhead CLI skill, or generate a skill from any command-line tool's --help output.
SKILL.md
1.9 KB, as published. Nobody here has run it
cli2skill
Convert CLI tools and MCP servers into Agent Skills (markdown files) that any AI coding agent can use. Zero runtime overhead β no persistent processes, no memory leaks.
Prerequisites
pip install cli2skill
Commands
Generate skill from CLI
# Basic β parse --help and generate SKILL.md
cli2skill generate <executable> --name <skill-name> -o ~/.claude/skills/
# Custom executable path
cli2skill generate "python my_tool.py" --name my-tool \
--exe-path "python /full/path/my_tool.py" -o ~/.claude/skills/
# From saved help text
cli2skill generate mytool --help-file help_output.txt -o ~/.claude/skills/
# Skip subcommand parsing (faster, top-level only)
cli2skill generate gh --name github-cli --no-subcommands -o ~/.claude/skills/
Preview parsed metadata
cli2skill preview <executable>
Convert MCP server to skill
# From command
cli2skill mcp npx some-mcp-server --name my-mcp -o ~/.claude/skills/
# From Claude Code settings.json
cli2skill mcp --config ~/.claude/settings.json --server my-server --name my-mcp -o ~/.claude/skills/
# With env vars
cli2skill mcp npx tavily-mcp --name tavily --env API_KEY=xxx -o ~/.claude/skills/
When to use
- You have an MCP server that's just "call -> return result" with no persistent state β replace it with a CLI skill to eliminate process leaks
- You want to give your agent access to any CLI tool without writing a skill by hand
- You're migrating away from MCP servers that accumulate zombie processes
When NOT to use
- MCP servers that need persistent browser sessions, streaming notifications, or multi-client shared state β those genuinely need MCP