Author and validate Warp software factory definition files against the server schema.
npx skills add https://github.com/warpdotdev/warp --skill factory-files
Please help me install this Agent Skill. Skill: factory-files Source: https://github.com/warpdotdev/warp/tree/main/resources/bundled/skills/factory-files Command: npx skills add https://github.com/warpdotdev/warp --skill factory-files
Editing Warp software factory definitions (factory.yaml, Agent, Automation, Scorer, Runner, and Webhook files) is error-prone because the format is owned by warp-server and changes over time. This Skill guides correct authoring of those files and validates the tree against the live server parser, avoiding stale local schema copies that report wrong diagnostics.
Ask the agent to create or edit a factory resource file in the repository rooted at factory.yaml and validate the tree with the bundled validation script before opening a pull request.
High-intent search queries and answers about installing and using this skill.
Run the bundled validator with Python 3.8 or newer: python3 scripts/validate_factory_files.py <factory-root>. It submits the tree's resource files to the warp-server validation endpoint, which runs the real parser and returns diagnostics with FF_* codes, paths, and line numbers.
Agents live at agents/<name>/agent.md and automations at automations/<name>/automation.md, with YAML frontmatter and a Markdown body as the prompt. Fetch the schema for the tree's schemaVersion from the warp-server schema endpoint first, since the server owns the format and unknown fields are errors.
Exit code 2 means the tree was not validated at all, typically because the server was unreachable, answered with an error, or the directory lacks a factory.yaml. It is neither a pass nor a failure, and you should report that validation did not run rather than claiming the files are correct.
No. The skill deliberately carries no local schema copy because a bundled copy goes stale against the server and reports confident, wrong diagnostics. When the server cannot be reached, the correct outcome is to state that the tree was not checked.
FF_UNKNOWN_FIELD means a field is not in the schema for the declared schemaVersion; check spelling against the fetched schema. FF_INVALID_TRIGGER indicates a structurally wrong trigger, such as a schedule.cron_fired trigger declaring both schedule.cron and filter.schedule_ids.
Do not use it for agent-definition Markdown belonging to other tools, for trees without a factory.yaml, or to operate a live factory. Operating a registered factory, sending work, or inspecting task status is handled through Factory MCP instead.
avav25Validate Windsurf assets, skills, templates, and checklists for repository integrity.
lushly-devGuide BotCore plugin development from protocol implementation to distribution.
AradotsoDefine standard Agent Skills with SKILL.md frontmatter for cross-platform loading.
flaviogragnolatiCall tRPC procedures from server-side code using createCallerFactory and router.createCaller().
