# factory-files

factory-files is a Claude Code skill that authors Warp software factory files in a repo tree rooted at factory.yaml and validates them on the server before a pull request.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 720 repo stars
- Author: dominikmartn
- License: AGPL-3.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/dominikmartn/harp/tree/HEAD/resources/bundled/skills/factory-files/SKILL.md
- Updated: 2026-11-10
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/factory-files

## What it does

The skill covers what defines a factory in a repository: `factory.yaml`, `agents/<name>/agent.md`, automations, runners, scorers, benchmarks and webhooks. Resource names come from the path, so renaming an agent means moving its directory. The format belongs to warp-server, and no copy of it sits in the skill; the schema for the tree's `schemaVersion` is pulled from two unauthenticated endpoints, `https://app.warp.dev/api/v1/factory-files/schemas` and `https://app.warp.dev/api/v1/factory-files/schemas/<schemaVersion>`.

Before a pull request the bundled `scripts/validate_factory_files.py` runs on Python 3.8 or newer and hands the tree to the server, which parses it the same way the apply path does. Exit `0` means nothing was reported, `1` means diagnostics to fix, `2` means the tree was not checked at all. Server state stays out of scope: model IDs, environment and secret names, runner names, MCP server IDs, and Linear or Slack aliases are resolved when the plan is applied.

Reaching the Warp server is part of the job. Without it the validator returns `2` and the files stay unchecked. No credential is needed; `WARP_API_KEY` is forwarded when the environment already carries one and dropped for a single retry on 401 or 403. Sending work to a live factory or reading task status belongs to `factory-mcp` instead.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add dominikmartn/harp --skill factory-files -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/factory-files/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/factory-files/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add dominikmartn/harp --skill factory-files -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/factory-files/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add dominikmartn/harp --skill factory-files -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/factory-files/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install dominikmartn/harp resources/bundled/skills/factory-files
```

2. **Manually: put the files in place**
- File: `.github/skills/factory-files/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add dominikmartn/harp --skill factory-files -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/dominikmartn/harp --path resources/bundled/skills/factory-files
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/factory-files/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/dominikmartn/harp/tree/HEAD/resources/bundled/skills/factory-files/SKILL.md

## When to use it
- add an automation to a factory tree
- edit an agent prompt without touching its frontmatter
- run the server parser over the tree before a pull request
- write a scorer rubric into the Markdown body
- trace a diagnostic after a schema version change

## Example prompts
- Add an automation that fires whenever a new pull request opens.
- Validate the factory tree and list every diagnostic it reports.
- Update the rubric in `scorers/review/scorer.md` and keep the frontmatter as it is.

## Similar
- [mastra-factory](https://affpapa.org/en/nevibecode/skills/mastra-factory.md) — skill · 6200 installs
- [factory-pattern](https://affpapa.org/en/nevibecode/skills/factory-pattern.md) — skill · 658 installs
- [agent-factory](https://affpapa.org/en/nevibecode/skills/agent-factory.md) — skill · ★ 907 repo stars
- [upload-insecure-files](https://affpapa.org/en/nevibecode/skills/upload-insecure-files.md) — skill · 3800 installs
- [skill-factory](https://affpapa.org/en/nevibecode/skills/basher83-skill-factory.md) — skill · 1 install
- [dag-factory](https://affpapa.org/en/nevibecode/skills/dag-factory.md) — skill · 438 installs

From the same set: [dominikmartn/harp](https://affpapa.org/en/nevibecode/by/dominikmartn/harp.md) — 62 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
