New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Factory

by BuilderIO in BuilderIO/skills

Experimental workflow for configuring an autonomous software delivery factory.

MITAuto-check passedDevelopment

Install Factory

skills CLI
$ npx skills add BuilderIO/skills --skill factory -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install BuilderIO/skills factory --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/factory .claude/skills/factory && rm -rf skills-src

Use ~/.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/

Facts

Skill name
factory
GitHub stars
4.5k
Token cost
~1k tokens
SKILL.md length
493 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

Experimental workflow for configuring an autonomous software delivery factory.

  • Works in 7 steps: Read .agent-factory/config.yaml if it… → Show the read-capable integrations this… → Set each action policy independently:… → …
  • Choosing feedback sources
  • SKILL.md covers Set up, Safe defaults, Modules and Prompt overlays, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Factory is an agent skill from BuilderIO/skills. Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git worktrees. The licence is MIT.

When your agent uses it

  • Choosing feedback sources
  • Worktree behavior
  • Host automations

Example prompts

  • “/factory”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Read .agent-factory/config.yaml if it exists. Preserve explicit choices.
  2. Show the read-capable integrations this host exposes. There is no built-in
  3. Set each action policy independently: implement, reply, close, review,
  4. Add optional per-skill prompts under skill_prompts when you want
  5. Choose schedules, time zone, worktree ownership, runtime, and notifications
  6. Write the agreed config. Never put credentials or tokens in it.
  7. If asked to create automations, create one job per enabled workflow, then

What it can do on your machine

Read from SKILL.md and the folder at commit 530d9ee. 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 loads about 1k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 493 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~1k

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 530d9ee, republished under its MIT licence (© BuilderIO). 493 words, ~1,000 tokens.

Download SKILL.mdSave it as .claude/skills/factory/SKILL.md (or your agent's skills folder).
name
factory
description
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.
installer-group
factory

Factory

Start with the Factory guide for workflow setup and configuration.

Read .agent-factory/config.yaml and apply the optional skill_prompts.factory entry as additional project guidance. Configure the current project to turn selected product or maintenance signals into verified, reviewed changes. Factory coordinates the other modules; it does not assume a provider, repository, schedule, or autonomy level.

Set up

Use the Factory configuration reference for field meanings, examples, and host limitations.

  1. Read .agent-factory/config.yaml if it exists. Preserve explicit choices.
  2. Show the read-capable integrations this host exposes. There is no built-in Factory source catalog. Confirm the source scope; add a custom source only when a connected tool can read it.
  3. Set each action policy independently: implement, reply, close, review, approve, publish, merge, deploy, recover, and notify.
  4. Add optional per-skill prompts under skill_prompts when you want project-specific rules layered onto a module.
  5. Choose schedules, time zone, worktree ownership, runtime, and notifications only where the host supports them.
  6. Write the agreed config. Never put credentials or tokens in it.
  7. If asked to create automations, create one job per enabled workflow, then read back its saved schedule, target, runtime, and notification settings. Report fields the host could not honor.

A config entry or written prompt does not prove a job exists. Treat unavailable or partial reads as unknown, not empty or successful.

Safe defaults

  • Keep replies, issue closure, approvals, merges, production deploys, and recovery disabled unless their own policy is explicit.
  • For criteria-based actions, record both conditions that allow the action and conditions that require a human.
  • Missing or unclear policy means hold. Permission to fix does not authorize publication or another external action.
Show full SKILL.md (219 more words)Show less

Modules

SkillScope
factory-collectCollect and triage configured feedback, telemetry, errors, and issues.
factory-lookbackFind recurring signals and brittle paths that need systemic fixes.
factory-human-digestAggregate work that still needs a human decision.
factory-review-prsReview a filtered PR queue.
factory-babysit-prFollow one explicitly authorized PR.
factory-shipPublish and complete a delivery lifecycle.
factory-watchdogFind stopped, authorized delivery work.
factory-recoverResume valid interrupted runs.

Modules can run independently. Each reads the same project config and must not borrow permissions from another workflow.

Prompt overlays

skill_prompts is an open map from a skill name to a multiline prompt. Each Factory module reads its matching entry, such as skill_prompts.factory-babysit-pr, and treats it as additional project guidance. Editing or removing that value replaces or removes the project overlay; it never replaces the installed skill instructions.

For scheduled runs, include the matching overlay in the saved automation prompt and verify the host retained it. A prompt cannot grant a permission, weaken repository or host safeguards, or override the user's current request. If it conflicts with those rules, follow the more restrictive requirement and surface the conflict.

Report

State which sources and host capabilities were verified, which policies and jobs were configured, what remains manual, and any unavailable evidence. Never claim that a schedule, integration, merge, or deployment exists without reading back its live state.

© 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 of BuilderIO/skills.

Open the folder on GitHubat commit 530d9ee

Compare with similar skills

Factory 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.

Factory compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Factory this skillBuilderIO/skills4.5k—~1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman41k—~2.6kAutomated safety check: PassGPL-3.0
Finishing A Development Branchfarm-fe/farm5.6k33 repos~1.8kAutomated safety check: PassMIT
Git Worktree Cleanuplobehub/lobehub83k—~2.8kAutomated safety check: PassCustom licence
Keep Codex Fastvibeforge1111/keep-codex-fast1.6k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    41k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Finishing A Development Branch

    farm-fe/farm

    A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 33 repos~1.8k tokens
    DevelopmentAuto-check passed

  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Keep Codex Fast

    vibeforge1111/keep-codex-fast

    A skill your agent uses when Codex feels slow or bloated, when local sessions/logs/worktrees/config have grown over time, or when a user wants safe maintenance for Codex Desktop/CLI state.

    1.6k GitHub stars~3.1k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

More from BuilderIO/skills

All 25 skills in this repo

  • 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…

    4.5k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • 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…

    4.5k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • 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"…

    4.5k GitHub stars~973 tokensUpdated today
    Auto-check passed

  • 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…

    4.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • 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…

    4.5k GitHub stars~857 tokensUpdated today
    Auto-check passed

  • Efficient Fable

    BuilderIO/skills

    A skill your agent uses when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy…

    4.5k GitHub stars~996 tokensUpdated today
    Auto-check passed

Categories

Questions about Factory

What does Factory do?

Experimental workflow for configuring an autonomous software delivery factory. Factory is an agent skill from BuilderIO/skills. Experimental workflow for configuring an autonomous software delivery factory.

When should I use Factory?

Factory fits situations like: choosing feedback sources; worktree behavior; host automations.

How do I install Factory in Claude Code?

Run `npx skills add BuilderIO/skills --skill factory -a claude-code`. Or copy the skill folder (skills/factory in BuilderIO/skills) into .claude/skills/factory in your project. Claude Code loads it when a task matches its description.

How do I install Factory in Codex?

Run `npx skills add BuilderIO/skills --skill factory -a codex`. Or copy the skill folder (skills/factory in BuilderIO/skills) into .agents/skills/factory in your project. Codex loads it when a task matches its description.

Can I use Factory 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 -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, .gemini/skills/factory, .github/skills/factory and .opencode/skills/factory in your project.

What does Factory need to run?

SKILL.md names no scripts, command-line tools or credentials: Factory is instructions for the agent only.

Does Factory 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 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 use?

Factory 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 use?

About 1k tokens (SKILL.md is roughly 4k 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?

Skills that share tags, products or a category with Factory: Finishing a Development Branch (obra/superpowers, 296k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars) and Git Worktree Cleanup (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Factory?

BuilderIO (a GitHub organization) maintains it in BuilderIO/skills, which has 4,528 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.