能力标签

⚙️

Agent工作流

克劳德工作流

基于 Shell · 无代码搭建完整 AI 自动化流程

英文名：claude-starter-kit

⭐ 9 Stars 🍴 1 Forks 💻 Shell 📄 MIT 🏷 AI 8.0分

8.0AI 综合评分

ai-agentsautomationshell

⬇ 下载源码 ZIP ⚙️ 配置说明 📺 TG 频道

✦ AI Skill Hub 推荐

经 AI Skill Hub 精选评估，克劳德工作流获评「强烈推荐」。这款Agent工作流在功能完整性、社区活跃度和易用性方面表现出色，AI 评分 8.0 分，适合有一定技术背景的用户使用。

📚 深度解析

克劳德工作流是一套完整的 AI Agent 自动化工作流方案。随着 AI 能力的不断提升，基于 Agent 的自动化工作流正在成为提升个人和团队效率的核心方式。区别于传统的 RPA 自动化（模拟鼠标键盘操作），AI Agent 工作流通过理解任务意图、动态规划执行路径，能够处理更复杂的非结构化任务。

克劳德工作流工作流的设计遵循"最小配置，最大复用"原则：核心逻辑已经封装好，用户只需配置自己的 API Key 和业务参数即可快速上手。工作流内置错误处理和重试机制，在网络波动或 API 限速等情况下仍能稳定运行，适合作为生产环境的自动化基础设施。

在实际部署时，建议先在测试环境中运行 3-5 次，验证各个环节的输出结果符合预期，再部署到生产环境。AI Skill Hub 评分 8.0 分，是同类 Agent 工作流中的精选推荐。

📋 工具概览

克劳德工作流是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。

GitHub Stars

⭐ 9

开发语言

Shell

支持平台

macOS / Linux

维护状态

轻量级项目，按需更新

开源协议

MIT

AI 综合评分

8.0 分

工具类型

Agent工作流

Forks

📖 中文文档

以下内容由 AI Skill Hub 根据项目信息自动整理，如需查看完整原始文档请访问底部「原始来源」。

📌 核心特色

可视化 Agent 工作流编排，无需编写复杂代码
支持多步骤自动化任务链，实现全流程无人值守
与外部 API、数据库和第三方服务无缝集成
内置错误处理与自动重试机制，保障稳定运行
提供可复用的自动化模板，快速在同类场景部署

🎯 主要使用场景

自动化日常重复性工作，将精力集中于创造性任务
构建数据采集 → 处理 → 输出的完整自动化管线
实现跨平台、跨系统的数据流转和业务协同

以下安装命令基于项目开发语言和类型自动生成，实际以官方 README 为准。

安装命令

# 克隆仓库
git clone https://github.com/byerlikaya/claude-starter-kit
cd claude-starter-kit

# 查看安装说明
cat README.md

# 按 README 完成环境依赖安装后即可使用

📋 安装步骤说明

访问 GitHub 仓库获取工作流文件
在对应平台（Dify / Flowise / Make 等）中找到「导入工作流」功能
上传工作流文件
按照提示配置必要的环境变量和 API Key
运行测试确认流程正常后投入使用

以下用法示例由 AI Skill Hub 整理，涵盖最常见的使用场景。

常用命令 / 代码示例

# 查看帮助
claude-starter-kit --help

# 基本运行
claude-starter-kit [options] <input>

# 详细使用说明请查阅文档
# https://github.com/byerlikaya/claude-starter-kit

以下配置示例基于典型使用场景生成，具体参数请参照官方文档调整。

配置示例

# claude-starter-kit 配置说明
# 查看配置选项
claude-starter-kit --config-example > config.yml

# 常见配置项
# output_dir: ./output
# log_level: info
# workers: 4

# 环境变量（覆盖配置文件）
export CLAUDE_STARTER_KIT_CONFIG="/path/to/config.yml"

📑 README 深度解析真实文档完整度 40/100 查看 GitHub 原文 →

以下内容由系统直接从 GitHub README 解析整理，保留代码块、表格与列表结构。

简介

What's inside

11 agents — see the table above.
30 skills — the single source of "how", one per area (full catalogue below).
6 slash commands — /brainstorm · /plan · /review · /ship · /handoff · /simplify.
Hooks — guard-bash.sh (tool-level gate), pre-commit + commit-msg (trace + secret scan), context-usage.sh and session-guard.sh (session measurement).
CLAUDE.md — behavior, the three principles, workflow, Definition of Done, token discipline, and prohibitions.

<details> <summary><b>Full skill catalogue</b> — all 30, generated from each skill</summary>

Skill	What it does
`a11y`	Frontend accessibility audit (WCAG): semantic HTML, keyboard access, focus management, contrast, ARIA, screen readers.
`adr`	Architecture Decision Record: context-decision-consequences, for decisions that are expensive to reverse.
`api-design`	API contract design: resource naming, error model, versioning, pagination, backward compatibility, OpenAPI.
`brainstorm`	Divergent discovery BEFORE planning: turn a fuzzy ask into 2–4 scoped options + named unknowns, pick a direction, hand to spec-planning.
`ci-pipeline`	CI pipeline discipline: lint→build→test→quality→security, fail-fast, deterministic build, secret handling, PR gates.
`code-review`	Code review discipline: severity-ranked, reasoned feedback on whether a change improves the system's overall code health.
`commit-message`	Conventional Commits: reads the staged diff and proposes `type(scope): summary`, with body/footer when needed.
`db-migration`	Apply schema migrations safely: detect the tool, classify the change by risk, gate destructive ones behind approval, back up in prod,…
`dependency-audit`	Dependency audit: known CVEs, licence compliance, abandoned/outdated packages, lockfile integrity, and a justification for every new…
`devarch-module`	DevArchitecture backend pattern: MediatR CQRS handler/command/query, IResult/IDataResult, Autofac AOP chain, FluentValidation, i18n.
`docs-writer`	Keeps documentation in sync with the code: README, usage and related docs when a public API or behavior changes.
`frontend-rn-expo`	OPTIONAL, stack-specific: React Native + Expo (prebuild).
`frontend`	Stack-agnostic frontend discipline (web · mobile · desktop): component structure, state, data fetching, loading/empty/error states,…
`handoff`	Session handover: when context fills, a phase closes, or the topic changes, write an action-oriented handover to docs/SESSION_STATE.md,…
`i18n-integrity`	Translation integrity: every key present in every language, no hardcoded strings, consistent placeholders and plurals.
`incident-runbook`	Production incident response: diagnose → mitigate → resolve, then a blameless postmortem and a repeatable runbook.
`iterate`	Refine-to-Done loop: repeat until tests green + review clean + nothing deferred; bounded.
`observability`	Stack-agnostic observability: structured logs, correlation ids, metrics and traces; no PII or secrets in logs.
`performance`	Stack-agnostic performance: measure first, find the bottleneck, then optimise.
`privacy-compliance`	KVKK/GDPR audit method: data inventory, purpose/basis/retention, minimisation, consent, transparency, data-subject rights, cross-border…
`red-team`	Attacker's-eye test of LLM/agent defenses: instruction hijacking, data exfiltration and tool abuse through untrusted content; verifies…
`reflect`	Retrospective self-audit after nontrivial work: unverified assumptions, skipped items, is-this-the-right- approach — findings, not code.
`release`	Versioning and CHANGELOG: SemVer mapped from Conventional Commits, Keep a Changelog format, tagging, pre-release gates.
`security-scan`	Stack-agnostic security audit: map the attack surface, trace untrusted input to dangerous calls, surface dependency and configuration flaws.
`sonarqube-check`	SonarQube quality gate (language-agnostic): 0 Bugs · 0 Vulnerabilities · 0 Security Hotspots · 0 Code Smells, build 0 warnings / 0…
`spec-planning`	Spec-first planning: task breakdown, measurable acceptance criteria, dependency order, risk priority.
`testing`	The how of testing: pyramid, AAA, isolation, risk coverage, determinism.
`token-budget`	Context/token discipline: subagent isolation, output = summary, move-to-file, delegation threshold, lean skills.
`trace-scan`	Trace scan (§4.1/§4.2): before a commit, scans the staged changes and the message for AI traces (co-author trailers, footers, robot…
`vps-deploy`	Deploy to a VPS safely: runtime detection, reverse proxy + SSL, atomic swap, keep the previous version, post-deploy health gate,…

</details>

---

Install & run

Two entry points: start.sh sets up a fresh project; adopt (adopt.sh) hands the kit over to an existing one. Pick any channel — each runs the same two commands.

npx — nothing to install:

npx @byerlikaya/claude-starter-kit          # fresh project
npx @byerlikaya/claude-starter-kit adopt    # existing project
npx @byerlikaya/claude-starter-kit@latest update   # refresh a project that already has the kit

Homebrew:

brew install byerlikaya/tap/claude-starter-kit
claude-starter-kit          # fresh project
claude-starter-kit adopt    # existing project

Release tarball — no package manager:

gh release download --repo byerlikaya/claude-starter-kit -p '*.tgz' && tar xzf claude-starter-kit-*.tgz
bash start.sh               # fresh project
bash adopt.sh              # existing project

Just want the agents & skills inside your existing Claude Code (no scaffolding)? /plugin marketplace add byerlikaya/claude-starter-kit then /plugin install claude-starter-kit@byerlikaya.

Windows: the kit is bash-based — run it inside Git Bash (from git-scm.com) for the smoothest experience; WSL works as a fallback.

🔁 Update an installed project

npx @byerlikaya/claude-starter-kit@latest update    # `update` is an alias of `adopt`; run it at the project root

At install time the kit stamps .claude/kit.conf with the profile, the backend stack and which installer ran, plus .claude/VERSION. The updater reads that stamp and refreshes the project in the shape it was installed in: a --backend project does not get frontend agents grafted back on, and a --dotnet project keeps its devarch-module pattern skill. Where the stamp is absent, the updater derives the shape from the installed files and writes it. Compare cat .claude/VERSION against npm view @byerlikaya/claude-starter-kit version to see whether an update is waiting.

	On update
`.claude/` agents · skills · commands · hooks · eval	refreshed from the new version
`.claude/DISCIPLINE.md`	overwritten — it is kit-owned, so keep nothing of your own in it
`./CLAUDE.md`	never touched — your project rules stay exactly as you wrote them
`.claude/settings.json`	merged schema-aware; your own hooks and permissions survive
your own agents and skills (no `-csk` suffix)	untouched

Like adopt, an update needs a git repo and lands on a kit-adopt-<timestamp> branch, staged and uncommitted — review the diff, then commit to accept or reset to discard.

If a project's CLAUDE.md carries the discipline inline instead of importing it, discipline updates cannot reach that project. The updater detects this, shows which lines hold the inline block, and offers to replace them with the single @.claude/DISCIPLINE.md import — writing a backup first, on a branch you review. Decline and nothing is touched; your project section and your own rules survive either way.

---

Workflow

/plan (ambiguous scope) → expert agents build → /review (security · quality · test) → /ship (DoD gate; proposes the commit, waits for approval) → when context fills up, /handoff → /clear.

🎯 aiskill88 AI 点评 A 级 2026-07-12

高质量的开源AI工作流项目