# Claude Skill Factory — Build & Install Claude Code Skills

> Claude Skill Factory ships ready-made skills and slash commands to build, validate, and install Claude Code skills as repeatable team assets.

## Install

Save the content below to `.claude/skills/` or append to your `CLAUDE.md`:

## Quick Use

1. Clone the repo:
   ```bash
   git clone https://github.com/alirezarezvani/claude-code-skill-factory
   cd claude-code-skill-factory
   ```
2. Install the included Prompt Factory skill:
   ```bash
   cp -r generated-skills/prompt-factory ~/.claude/skills/
   ```
3. Verify:
   - Open Claude Code and confirm the installed skill appears and can answer one guided prompt request.

## Intro

Claude Skill Factory ships ready-made skills and slash commands to build, validate, and install Claude Code skills as repeatable team assets.

- **Best for:** Claude Code users who want a structured way to generate and share skills/prompts
- **Works with:** Claude Code (skills, slash commands), local filesystem, team repos for versioning
- **Setup time:** 10–25 minutes

## Practical Notes

- Quant: start by installing 1 skill and measure time-to-first-use (clone → install → first output).
- Quant: keep generated skills in a repo and review via PRs weekly to avoid prompt drift.

## Pattern: treat skills like code

To keep skills maintainable:
- store them in your repo,
- review changes via PR,
- and keep small, testable boundaries (inputs/outputs).

## Suggested workflow

1. Use the builder commands to generate a first draft.
2. Run validation and package outputs.
3. Install into `~/.claude/skills/` and test on one real task.
4. Promote only the stable ones into your team baseline.

This reduces the “random prompt folder” problem and makes skills reusable across projects.

### FAQ

**Q: Do I have to install everything?**
A: No. Start with one included skill (Prompt Factory) and expand after you trust the workflow.

**Q: Where should skills live long-term?**
A: In a team repo, with PR review, then installed to user machines as a deployment step.

**Q: How do I verify quality?**
A: Run the same task twice and check outputs for consistency, safety, and useful structure.

## Source & Thanks

> Source: https://github.com/alirezarezvani/claude-code-skill-factory
> License: MIT
> GitHub stars: 764 · forks: 149

---

<!-- ZH -->

## 快速使用

1. 克隆仓库：
   ```bash
   git clone https://github.com/alirezarezvani/claude-code-skill-factory
   cd claude-code-skill-factory
   ```
2. 安装内置的 Prompt Factory 技能：
   ```bash
   cp -r generated-skills/prompt-factory ~/.claude/skills/
   ```
3. 验证：
   - 打开 Claude Code，确认技能已出现，并完成一次引导式 prompt 生成。

## 简介

Claude Skill Factory 提供可直接安装的技能与一组 slash 命令，帮助你生成、校验并安装 Claude Code skills；把零散的提示词工程沉淀为可复用、可协作、可版本化的团队资产。

- **适合谁：** 希望系统化生成并共享 skills/prompts 的 Claude Code 用户
- **可搭配：** Claude Code（skills 与 slash commands）、本地文件系统、用于版本化的团队仓库
- **准备时间：** 10–25 分钟

## 实战建议

- 量化建议：先装 1 个技能，记录从 clone→install→首次产出的总耗时。
- 量化建议：把生成的 skills 放进仓库并走 PR 评审，每周复查，避免 prompt 漂移。

## 常用打法：把技能当作代码来维护

要让技能可维护：
- 放进仓库，
- 走 PR 评审，
- 并保持输入/输出边界清晰且可测试。

## 推荐流程

1. 用 builder 命令生成初稿。
2. 校验输出并打包。
3. 安装到 `~/.claude/skills/`，用一个真实任务验证。
4. 只把稳定的技能升级到团队 baseline。

这样可以避免“随手堆 prompt 文件夹”，让技能跨项目复用。

### FAQ

**需要一次性装很多吗？**
答：不需要。先从一个技能（如 Prompt Factory）开始，验证流程后再扩展。

**长期放哪维护？**
答：放团队仓库并走 PR；安装到个人机器作为部署步骤。

**怎么验证质量？**
答：同一任务跑两次，检查输出是否稳定、安全且结构有用。

## 来源与感谢

> Source: https://github.com/alirezarezvani/claude-code-skill-factory
> License: MIT
> GitHub stars: 764 · forks: 149


---
Source: https://tokrepo.com/en/workflows/claude-skill-factory-build-install-claude-code-skills
Author: Skill Factory