cli-printing-press Agent工作流
cli-printing-press Agent工作流 是 AI Skill Hub 本期精选Agent工作流之一。已获得 2.0k 颗 GitHub Star，综合评分 8.5 分，整体质量较高。我们强烈推荐将其纳入你的 AI 工具库，帮助提升工作效率。
📚 深度解析
cli-printing-press Agent工作流 工作流的设计遵循"最小配置，最大复用"原则：核心逻辑已经封装好，用户只需配置自己的 API Key 和业务参数即可快速上手。工作流内置错误处理和重试机制，在网络波动或 API 限速等情况下仍能稳定运行，适合作为生产环境的自动化基础设施。
在实际部署时，建议先在测试环境中运行 3-5 次，验证各个环节的输出结果符合预期，再部署到生产环境。AI Skill Hub 评分 8.5 分，是同类 Agent 工作流中的精选推荐。
📋 工具概览
cli-printing-press Agent工作流 是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。
📖 中文文档
cli-printing-press Agent工作流 是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。
- 可视化 Agent 工作流编排，无需编写复杂代码
- 支持多步骤自动化任务链，实现全流程无人值守
- 与外部 API、数据库和第三方服务无缝集成
- 内置错误处理与自动重试机制，保障稳定运行
- 提供可复用的自动化模板，快速在同类场景部署
- 自动化日常重复性工作，将精力集中于创造性任务
- 构建数据采集 → 处理 → 输出的完整自动化管线
- 实现跨平台、跨系统的数据流转和业务协同
# 方式一：go install（推荐） go install github.com/mvanhorn/cli-printing-press@latest # 方式二：从源码编译 git clone https://github.com/mvanhorn/cli-printing-press cd cli-printing-press go build -o cli-printing-press . # 方式三：下载预编译二进制 # 访问 Releases 页面下载对应平台二进制文件 # https://github.com/mvanhorn/cli-printing-press/releases
- 访问 GitHub 仓库获取工作流文件
- 在对应平台（Dify / Flowise / Make 等）中找到「导入工作流」功能
- 上传工作流文件
- 按照提示配置必要的环境变量和 API Key
- 运行测试确认流程正常后投入使用
# 查看帮助 cli-printing-press --help # 基本运行 cli-printing-press [options] <input> # 详细使用说明请查阅文档 # https://github.com/mvanhorn/cli-printing-press
# cli-printing-press 配置说明 # 查看配置选项 cli-printing-press --config-example > config.yml # 常见配置项 # output_dir: ./output # log_level: info # workers: 4 # 环境变量（覆盖配置文件） export CLI_PRINTING_PRESS_CONFIG="/path/to/config.yml"
Install
You need both the binary and the Printing Press skills. The skills (/printing-press <app>) are the primary interface; they drive the binary behind the scenes.
The binary alone works (research, generation, verification, scoring) but skips the curated agent loop. The skills alone have nothing to call. Install both.
Prerequisites: Go 1.26.4 or newer, Claude Code or another skills-supported agent, and Node/npm for npx. The skills are tested with Claude Code; install for Codex with --agent codex when you want to try the same slash-command workflow there. Use Claude Code for the best-tested experience.
1. Install
curl -fsSL https://raw.githubusercontent.com/mvanhorn/cli-printing-press/main/scripts/install.sh | bashThe installer runs go install for the generator binary, then refreshes all Printing Press skills through skills@latest add --skill '*'. Restart or reload your agent session after it completes so the refreshed skills are loaded.
Use --cli-only or --skills-only when you only want one side:
curl -fsSL https://raw.githubusercontent.com/mvanhorn/cli-printing-press/main/scripts/install.sh | bash -s -- --cli-only
curl -fsSL https://raw.githubusercontent.com/mvanhorn/cli-printing-press/main/scripts/install.sh | bash -s -- --skills-onlyClaude Code is the default install target. To install or refresh the skills for Codex instead, pass --agent codex:
curl -fsSL https://raw.githubusercontent.com/mvanhorn/cli-printing-press/main/scripts/install.sh | bash -s -- --skills-only --agent codex
npx -y skills@latest list -g -a codex --jsonSee docs/CODEX.md for the Codex-specific notes.
Verify with cli-printing-press --version. If install fails, confirm Go 1.26.4 or newer is installed, Node/npm is installed for npx, and $GOPATH/bin is on your PATH.
Older releases installed a generator binary named printing-press. That legacy entrypoint still works for compatibility, but the canonical generator command is now cli-printing-press so the public catalog installer can own printing-press list, printing-press search, and printing-press install.
<details> <summary><b>Manual install</b></summary>
Install or update the binary:
go install github.com/mvanhorn/cli-printing-press/v4/cmd/cli-printing-press@latestUse Vercel's open-agent-skills CLI to install the Printing Press skills from this repo into a supported agent. Claude Code is the default and tested path:
npx -y skills@latest add mvanhorn/cli-printing-press/skills --skill '*' -g -a claude-code -yFor Codex:
npx -y skills@latest add mvanhorn/cli-printing-press/skills --skill '*' -g -a codex -y
npx -y skills@latest list -g -a codex --jsonTo refresh the skills later without naming individual skills, rerun the installer in skills-only mode:
curl -fsSL https://raw.githubusercontent.com/mvanhorn/cli-printing-press/main/scripts/install.sh | bash -s -- --skills-onlyRestart or reload the target agent after refreshing skills so the new skill text is loaded.
</details>
Once installed, you can start Claude Code from any folder. Codex users should start a fresh Codex session after installing or refreshing skills.
<details> <summary><b>Developer path: load skills from a clone</b></summary>
Use this if you're editing the Printing Press itself and want local skill changes to take effect on the next session start.
git clone https://github.com/mvanhorn/cli-printing-press.git
cd cli-printing-press
claude --plugin-dir . # load this repo's skills directly
claude --plugin-dir . -w # ...in a new git worktree (parallel runs)For a persistent local setup that survives restarts and also loads in background sessions, see Local Plugin Development.
</details>
CLI Printing Press
Nothing is more valuable than time and money. In a world of AI agents, that's speed and token spend. A well-designed CLI is muscle memory for an agent: no hunting through docs, no wrong turns, no wasted tokens. We built the Printing Press to print the best CLIs in the world for agents.
It reads the official API docs, studies every popular community CLI and MCP server, sniffs the web for the APIs nobody published (think Google Flights or Dominos), and applies the power-user playbook Peter Steinberger proved with discrawl and gogcli - local SQLite, compound commands, agent-native flags. It fuses all of that and prints a token-efficient Go CLI plus a Claude Code skill plus an MCP server for any API or any website.
Three CLIs printed by the press, installable today:
- ESPN (sniffed, no official API). "Tonight's NBA playoff games with live score, series state, each team's leading scorer's stat line, and any injury or lineup news from the last 24 hours." Returns everything in one call.
- flight-goat (Kayak nonstop search plus sniffed Google Flights). "Non-stop flights over 8 hours from Seattle for 4 people, Dec 24 to Jan 1, cheapest first." Two sources stitched into one query.
- linear-pp-cli (50ms against a local SQLite mirror). "Every blocked issue whose blocker has been stuck for a week." Compound queries the API can't answer.
Browse the full catalog of printed CLIs at printingpress.dev or in the Printing Press Library, organized by category, most with full MCP servers.
Codex users: see docs/CODEX.md to install the Printing Press skills with --agent codex, verify the install, and understand how that differs from /printing-press <api> codex.
Cursor users: see docs/CURSOR.md for how to install a printed CLI, attach the matching skill, handle auth, and choose CLI vs MCP when your repo does not already document a workflow.
Every endpoint. Every insight. One command.
Discord's API has 300+ endpoints. Most generators stop there - wrap every endpoint, ship it, done. But discrawl - Peter Steinberger's Discord tool - ignores most of them. It ships 11 commands: sync, search, sql, tail, mentions, members. 583 stars.
Why does the 11-command tool win? Because Steinberger saw something Discord's own API designers didn't: conversations are institutional knowledge. Every message thread is a document that should be archived, indexed, and searched locally. Those 11 commands embody that insight. The 300 endpoint wrappers don't.
Until now, you had to choose: breadth (wrap every endpoint) or depth (understand the user). The printing press eliminates that choice. It generates the full API surface AND matches every feature the top competitor has AND adds the discrawl-style intelligence layer AND an MCP server. One spec in. Everything out.
Runtime verification: tests every command against real API or mock server
cli-printing-press verify --dir ./my-pp-cli --spec ./openapi.json --api-key $TOKEN
Live API testing
When you provide an API key at the start, Phase 5 runs read-only tests against the real API:
```
LIVE API TEST RESULTS
Auth: PASS (200 OK on doctor) List: 3/3 passed (users, channels, guilds) Get: 1/1 passed (user abc123) Sync: PASS (5 pages synced, 12 blocks) Search: PASS (3 results for "a")
Verdict: PASS - CLI works against real API ```
Safety: GET only, --limit 1, 10s timeout, stops on 401. Never creates, posts, or deletes anything.
Troubleshooting
/printing-press slash command doesn't appear. Restart or reload the agent session after installing the skills. For Claude Code, run npx -y skills@latest list -g -a claude-code to verify the install. For Codex, run npx -y skills@latest list -g -a codex --json. If you're developing from a clone in Claude Code, confirm claude --plugin-dir . was run from the cloned repo root or use the persistent local setup in Local Plugin Development.
cli-printing-press: command not found after a successful go install. $GOPATH/bin (default ~/go/bin) isn't on your PATH. Add it to your shell profile.
Live API smoke test reports 401. Token unset or stale. Run cli-printing-press auth doctor to see which env vars are missing or suspicious before reading shell config.
Browser-sniff captures no useful endpoints. The site likely uses websockets, gRPC, or aggressive bot detection. Try a HAR export from DevTools (/printing-press --har ./capture.har) instead of the live browser flow.
Codex mode falls back to local generation. Expected behavior after 3 consecutive Codex failures. Standard Opus mode takes over with no manual intervention.
FAQ
Why not Speakeasy, Fern, or openapi-generator? Those wrap endpoints. We wrap endpoints AND generate the discrawl-style data layer (SQLite, FTS5, sync, compound commands) AND the MCP server AND the agent-native UX (typed exit codes, --compact, auto-JSON-when-piped). The output is shaped for an agent that will call it thousands of times a day.
Does it work without Claude? The binary works standalone (research, generation, verification, scoring), and the skills can be installed for Codex with --agent codex. The curated agent loop is tested in Claude Code first, so bring your own review discipline if you use another harness.
Does it require an OpenAPI spec? No. Three input modes: a spec (--spec), a HAR file (--har), or just a URL. The browser-sniff gate launches a browser, captures traffic, and reverse-engineers the spec for sites that don't publish one.
How fresh is the local SQLite cache? Configurable. Without cache.enabled, you run sync manually. With cache.enabled and --data-source auto, the CLI runs a bounded pre-read refresh before serving local data. --data-source local skips refresh; --data-source live bypasses the cache entirely.
What does shipping a CLI cost in tokens? Standard Opus mode runs end-to-end on Opus. Codex mode (/printing-press <api> codex) offloads Phase 3 code generation to Codex CLI for ~60% fewer Opus tokens. Both produce equivalent quality.
Can I run the verification tools on a CLI I built by hand? Yes. cli-printing-press scorecard, dogfood, and verify accept any directory + spec. Tier 1 of the scorecard checks for agent-native patterns; Tier 2 checks paths/auth/data-flow against the spec.
优秀的AI工作流工具，创新性强。通过自动化探索API特性并生成CLI，大幅提升开发效率。代码质量高，社区活跃，持续维护更新。
- 需要让 Claude / Cursor 操作本地工具的 AI 工程师
- 构建多智能体协作系统的 Agent 开发者
- 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
- Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
- API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
- MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
- CLI：直接 npm install -g / pip install，命令行调用
- 云端托管：可放在 Vercel / Railway / Fly.io 等 PaaS 平台
⚡ 核心功能
- 可视化 Agent 工作流编排，无需编写复杂代码
- 支持多步骤自动化任务链，实现全流程无人值守
- 与外部 API、数据库和第三方服务无缝集成
- 内置错误处理与自动重试机制，保障稳定运行
- 提供可复用的自动化模板，快速在同类场景部署
- 需要让 Claude / Cursor 操作本地工具的 AI 工程师
- 构建多智能体协作系统的 Agent 开发者
- 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
- Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
- API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
- MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
👥 适合人群
🎯 使用场景
- 自动化日常重复性工作，将精力集中于创造性任务
- 构建数据采集 → 处理 → 输出的完整自动化管线
- 实现跨平台、跨系统的数据流转和业务协同
⚖️ 优点与不足
- +MIT 协议，可免费商用
- +大幅减少重复性人工操作
- +可视化流程，清晰直观
- +可扩展性强，支持复杂场景
- −初始配置和调试需投入一定时间
- −强依赖外部服务的稳定性
- −复杂场景需具备一定技术基础
AI Skill Hub 为第三方内容聚合平台，本页面信息基于公开数据整理，不对工具功能和质量作任何法律背书。
建议在沙箱或测试环境中充分验证后，再部署至生产环境，并做好必要的安全评估。
✅ MIT 协议 — 最宽松的开源协议之一，可自由商用、修改、分发，仅需保留版权声明。
🔗 相关工具推荐
❓ 常见问题 FAQ
经综合评估，cli-printing-press Agent工作流 在Agent工作流赛道中表现稳健，质量优秀。如果你已有明确的使用需求，可以直接上手体验；如果还在评估阶段，建议对比同类工具后再做决策。
| 原始名称 | cli-printing-press |
| 原始描述 | 开源AI工作流：Every API has a secret identity. This finds it, absorbs every feature from every。⭐2.0k · Go |
| Topics | API集成CLI生成AI工作流开发者工具Go语言 |
| GitHub | https://github.com/mvanhorn/cli-printing-press |
| License | MIT |
| 语言 | Go |
收录时间：2026-05-16 · 更新时间：2026-05-19 · License：MIT · AI Skill Hub 不对第三方内容的准确性作法律背书。