Report
microsoft/data-formulator
Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded…
Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work.
MITAuto-check passed
Install Factory Watchdog
$ npx skills add BuilderIO/skills --skill factory-watchdog -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BuilderIO/skills factory-watchdog --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/factory-watchdog .claude/skills/factory-watchdog && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "factory-watchdog" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-watchdog into .claude/skills/factory-watchdog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-watchdog", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BuilderIO/skills/tree/main/skills/factory-watchdogType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BuilderIO/skills --skill factory-watchdog -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BuilderIO/skills factory-watchdog --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/factory-watchdog .agents/skills/factory-watchdog && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "factory-watchdog" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-watchdog into .agents/skills/factory-watchdog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-watchdog", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/skills --skill factory-watchdog -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BuilderIO/skills factory-watchdog --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/factory-watchdog .cursor/skills/factory-watchdog && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "factory-watchdog" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-watchdog into .cursor/skills/factory-watchdog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-watchdog", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BuilderIO/skills.git --path skills/factory-watchdog--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BuilderIO/skills --skill factory-watchdog -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BuilderIO/skills factory-watchdog --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/factory-watchdog .gemini/skills/factory-watchdog && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "factory-watchdog" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-watchdog into .gemini/skills/factory-watchdog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-watchdog", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BuilderIO/skills factory-watchdogInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BuilderIO/skills --skill factory-watchdog -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/factory-watchdog .github/skills/factory-watchdog && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "factory-watchdog" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-watchdog into .github/skills/factory-watchdog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-watchdog", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/skills --skill factory-watchdog -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BuilderIO/skills factory-watchdog --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/factory-watchdog .opencode/skills/factory-watchdog && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "factory-watchdog" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-watchdog into .opencode/skills/factory-watchdog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-watchdog", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
factory-watchdog- GitHub stars
- 4.5k
- Token cost
- ~461 tokens
- SKILL.md length
- 211 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work.
- Scheduled ship follow-through
- SKILL.md covers Find actionable stopped work and Notify only on a verified next…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Factory Watchdog is an agent skill from BuilderIO/skills. Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work. Use for scheduled ship follow-through.
Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The licence is MIT.
When your agent uses it
- Scheduled ship follow-through
Example prompts
- “/factory-watchdog”
What it can do on your machine
Read from SKILL.md and the folder at commit da158ca. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Factory Watchdog loads about 461 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 211 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from BuilderIO/skills at commit da158ca, republished under its MIT licence (© BuilderIO). 211 words, ~461 tokens.
Download SKILL.mdSave it as
.claude/skills/factory-watchdog/SKILL.md (or your agent's skills folder).- name
- factory-watchdog
- description
- Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work. Use for scheduled ship follow-through.
- installer-group
- factory
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.
© BuilderIO, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/factory-watchdog of BuilderIO/skills.
Open the folder on GitHubat commit da158ca
Compare with similar skills
Factory Watchdog next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Factory Watchdog this skillBuilderIO/skills | 4.5k | — | ~461 | Automated safety check: Pass | MIT | |
| Reportmicrosoft/data-formulator | 18k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Reportalirezarezvani/claude-skills | 28k | 1 repos | ~727 | Automated safety check: Pass | MIT | |
| Bugcrowd Reportingsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.9k | Automated safety check: Pass | MIT | |
| Reportsgarrytan/gbrain | 31k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Watchdogmvschwarz/openrig | 5.9k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Report
alirezarezvani/claude-skills
Generate test report. An agent skill from alirezarezvani/claude-skills.
Bugcrowd Reporting
sickn33/agentic-awesome-skills
Bugcrowd-specific reporting tactics complementing report-writing
Reports
garrytan/gbrain
Save and load timestamped reports. An agent skill from garrytan/gbrain.
Watchdog
mvschwarz/openrig
A skill your agent uses when configuring rig watchdog policies, authoring wake/refocus/alignment-checkpoint messages, or choosing the right intervention level for a stale-owner situation.
Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
More from BuilderIO/skills
All 25 skills in this repoTurn Into App
BuilderIO/skills
Turns a thread, skill, spreadsheet, or Claude/ChatGPT project into a polished, visual Agent-Native app: populated domain screens with the in-app agent working behind contextual controls.
Agent Watchdog
BuilderIO/skills
A skill your agent uses when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log…
Plan Arbiter
BuilderIO/skills
A skill your agent uses when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed…
Plow Ahead
BuilderIO/skills
A skill your agent uses when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done"…
Read The Damn Docs
BuilderIO/skills
A skill your agent uses when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs…
Stay Within Limits
BuilderIO/skills
A skill your agent uses when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window…
Questions about Factory Watchdog
What does Factory Watchdog do?
Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work. Factory Watchdog is an agent skill from BuilderIO/skills. Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work.
When should I use Factory Watchdog?
Factory Watchdog fits situations like: scheduled ship follow-through.
How do I install Factory Watchdog in Claude Code?
Run `npx skills add BuilderIO/skills --skill factory-watchdog -a claude-code`. Or copy the skill folder (skills/factory-watchdog in BuilderIO/skills) into .claude/skills/factory-watchdog in your project. Claude Code loads it when a task matches its description.
How do I install Factory Watchdog in Codex?
Run `npx skills add BuilderIO/skills --skill factory-watchdog -a codex`. Or copy the skill folder (skills/factory-watchdog in BuilderIO/skills) into .agents/skills/factory-watchdog in your project. Codex loads it when a task matches its description.
Can I use Factory Watchdog in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BuilderIO/skills --skill factory-watchdog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/factory-watchdog, .gemini/skills/factory-watchdog, .github/skills/factory-watchdog and .opencode/skills/factory-watchdog in your project.
What does Factory Watchdog need to run?
SKILL.md names no scripts, command-line tools or credentials: Factory Watchdog is instructions for the agent only.
Does Factory Watchdog access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Factory Watchdog safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Factory Watchdog use?
Factory Watchdog is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Factory Watchdog use?
About 461 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Factory Watchdog?
Skills that share tags, products or a category with Factory Watchdog: Report (microsoft/data-formulator, 18k stars), Report (alirezarezvani/claude-skills, 28k stars), Bugcrowd Reporting (sickn33/agentic-awesome-skills, 47k stars) and Reports (garrytan/gbrain, 31k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Factory Watchdog?
BuilderIO (a GitHub organization) maintains it in BuilderIO/skills, which has 4,541 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 7, 2026.
Source: BuilderIO/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.