factory-files — Claude Code skill: Warp software 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.
AGPL-3.0 ★ 720 updated 2026-11-10
npx skills add dominikmartn/harp --skill factory-files -a claude-codeWhat factory-files 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.
What it helps with
- 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 for the agent
- 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.mdand keep the frontmatter as it is.
How to install factory-files
1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill factory-files -a claude-code2Manually: put the files in place
~/.claude/skills/factory-files/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/factory-files/
1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill factory-files -a codex2Manually: put the files in place
.agents/skills/factory-files/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill factory-files -a cursor2Manually: put the files in place
.cursor/skills/factory-files/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dominikmartn/harp resources/bundled/skills/factory-files2Manually: put the files in place
.github/skills/factory-files/SKILL.md1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill factory-files -a gemini-cli2Platform CLI
gemini skills install https://github.com/dominikmartn/harp --path resources/bundled/skills/factory-filesManually: put the files in place
.devin/skills/factory-files/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about factory-files
How do I install factory-files in Claude Code?
Run npx skills add dominikmartn/harp --skill factory-files -a claude-code. The skill lands at ~/.claude/skills/factory-files/SKILL.md.
What does factory-files do?
It writes and edits the file-based definitions of a Warp software factory and checks the tree with the parser the server uses on apply.
What do I need to run factory-files?
Python 3.8 or newer and a reachable Warp server at https://app.warp.dev. No API key is required; an existing WARP_API_KEY is forwarded when present.