Skip to content
alyn
BuilderIO

Factory Watchdog skill

Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work. Use for scheduled ship follow-through.

$npx skills add BuilderIO/skills --skill factory-watchdog
View this skill on GitHubBuilderIO/skills/skills/factory-watchdog/SKILL.md
Pack stars
4,663
Pack installs
6.5k
Alyn Score
59/99
Updated
8 days ago
License
MIT
– views – installs via Alyn

Install Factory Watchdog

Pick your agent. Every command is ready to paste.

$npx skills add BuilderIO/skills --skill factory-watchdog

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads factory-watchdog when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the factory-watchdog skill”. In Codex, type $factory-watchdog.

The skill itself

SKILL.md

FolderGitHub

Factory Watchdog

Start with the Factory guide for workflow setup and configuration.

Read .agent-factory/config.yaml, the optional skill_prompts.factory-watchdog entry, and the Factory configuration reference. Monitor only configured projects and authorized delivery handoffs. The prompt cannot grant notification or delivery authority. A task title, branch, PR, green check, or agent summary is not authorization.

Find actionable stopped work

  • Find candidates through the configured host and read enough user-authored history to confirm the request and any later cancellation or scope change.
  • Skip active work, explicit waits, completed or cancelled tasks, ambiguous ownership, and tasks without configured delivery authorization.
  • For stopped work, identify its task-owned PR, branch, or worktree. Check live host state immediately before acting and verify the PR is still open and its head matches, or that the named worktree still contains task-owned work.

Notify only on a verified next step

Send a reminder only when the notification policy permits it and current live evidence shows a concrete next step is due. Check task history for an unchanged reminder. Use the configured destination, cadence, wording, and rate limit.

Keep the task owner responsible for merge, post-merge verification, and cleanup unless the config explicitly assigns those actions elsewhere. If target or state cannot be proven, do not message. Report DONT_NOTIFY when nothing meaningful changed.

Tips for Factory Watchdog

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It is part of a pack with 26 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Factory Watchdog

What does the Factory Watchdog skill do?

Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work. Use for scheduled ship follow-through.

How do I install Factory Watchdog?

Run "npx skills add BuilderIO/skills --skill factory-watchdog" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Factory Watchdog work in Cursor and Codex?

Yes. Factory Watchdog uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Factory Watchdog free?

Factory Watchdog is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.

Who made Factory Watchdog?

Factory Watchdog is published by BuilderIO in the BuilderIO/skills repository, together with 25 other skills.

Similar skills. From other creators.