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 Ship

by BuilderIO in BuilderIO/skills

Experimental workflow for publishing and completing configured software delivery work.

MITAuto-check passed

Install Factory Ship

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

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

GitHub CLI
$ gh skill install BuilderIO/skills factory-ship --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-ship .claude/skills/factory-ship && 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-ship
GitHub stars
4.5k
Token cost
~539 tokens
SKILL.md length
260 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

Experimental workflow for publishing and completing configured software delivery work.

  • Works in 6 steps: Confirm ownership. Identify the target… → Verify changes. Run the configured… → Publish when enabled. Open or update a… → …
  • An enabled factory policy asks to ship
  • SKILL.md covers Delivery steps and Stop conditions
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Factory Ship is an agent skill from BuilderIO/skills. Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.

Its SKILL.md is about 540 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

  • An enabled factory policy asks to ship

Example prompts

  • “/factory-ship”

Workflow steps

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

  1. Confirm ownership. Identify the target repository, task-owned worktree,
  2. Verify changes. Run the configured formatter, tests, and release checks.
  3. Publish when enabled. Open or update a PR only when authorized. Apply
  4. Resolve feedback. Compare comments with the code and current human
  5. Apply merge gates. Merge only under its own enabled policy and while all
  6. Verify and close out. Confirm the merge in the current base branch.

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 Ship loads about 539 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 260 words of instructions outside code blocks.

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

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). 260 words, ~539 tokens.

Download SKILL.mdSave it as .claude/skills/factory-ship/SKILL.md (or your agent's skills folder).
name
factory-ship
description
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
installer-group
factory

Factory Ship

Start with the Factory guide for workflow setup and configuration.

Read .agent-factory/config.yaml, the optional skill_prompts.factory-ship entry, and the repository's instructions before publishing. See the Factory configuration reference. The prompt adds project guidance; editing code does not by itself authorize a PR update, approval, merge, or deployment.

Delivery steps

  1. Confirm ownership. Identify the target repository, task-owned worktree, branch, and complete task-related change set. Preserve unrelated changes. Use a clean automation-owned worktree when the scheduler provides one; never take over a peer's checkout.
  2. Verify changes. Run the configured formatter, tests, and release checks. Report checks that were skipped or unavailable.
  3. Publish when enabled. Open or update a PR only when authorized. Apply configured title, body, draft status, labels, and communication rules. Do not tag or message people unless enabled.
  4. Resolve feedback. Compare comments with the code and current human direction. Make one coherent update, then rerun affected checks.
  5. Apply merge gates. Merge only under its own enabled policy and while all criteria hold on the unchanged live head. Use a head-match guard when the host supports it. A head change invalidates tied evidence and resets the soak.
  6. Verify and close out. Confirm the merge in the current base branch. Verify deployment only when configured; a merge is not live proof. Close issues, rotate worktrees, and notify only at their configured proof points.

Stop conditions

Hold the work when ownership, authorization, a required check, or live host state is missing or unclear. State the exact next step; do not turn an inconclusive result into success.

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

Open the folder on GitHubat commit 530d9ee

Compare with similar skills

Factory Ship 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 Ship compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Factory Ship this skillBuilderIO/skills4.5k—~539Automated safety check: PassMIT
Configure Factory Rulesmastra-ai/mastra29k—~3.4kAutomated safety check: PassCustom licence
Publishcode-yeongyu/oh-my-openagent70k—~5.5kAutomated safety check: WarnCustom licence
Factory Complete Issuemastra-ai/mastra29k—~485Automated safety check: PassCustom licence
Social Publisheraffaan-m/ECC274k1 repos~1.1kAutomated safety check: PassMIT
Publishyc-software/qm15k—~2.2kAutomated safety check: WarnMIT

Similar skills

  • Configure Factory Rules

    mastra-ai/mastra

    Configure board-owned lifecycle, policy, phase-semantics, and tool-result rules, plus integration event rules

    29k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Publish

    code-yeongyu/oh-my-openagent

    Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts.

    70k GitHub stars~5.5k tokensUpdated today
    DevOps & CloudAuto-check: warnings

  • Factory Complete Issue

    mastra-ai/mastra

    Mark a GitHub issue as done and update its status labels. An agent skill from mastra-ai/mastra.

    29k GitHub stars~485 tokensUpdated today
    DevelopmentAuto-check passed

  • Social Publisher

    affaan-m/ECC

    Agent-driven scheduling and publishing of social media posts across 13 platforms via SocialClaw.

    274k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed

  • Publish

    yc-software/qm

    Publish a long-lived internal web app, site, or dashboard from the agent computer.

    15k GitHub stars~2.2k tokensUpdated today
    DevOps & CloudAuto-check: warnings

  • Factory Review

    mastra-ai/mastra

    Review a pull request for a Factory work item — history and context first, then a verdict published on the PR — and mark the review complete

    29k GitHub stars~10k tokensUpdated today
    DevelopmentAuto-check: warnings

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

Questions about Factory Ship

What does Factory Ship do?

Experimental workflow for publishing and completing configured software delivery work. Factory Ship is an agent skill from BuilderIO/skills. Experimental workflow for publishing and completing configured software delivery work.

When should I use Factory Ship?

Factory Ship fits situations like: an enabled factory policy asks to ship.

How do I install Factory Ship in Claude Code?

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

How do I install Factory Ship in Codex?

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

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

What does Factory Ship need to run?

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

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

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

About 539 tokens (SKILL.md is roughly 2.2k 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 Ship?

Skills that share tags, products or a category with Factory Ship: Configure Factory Rules (mastra-ai/mastra, 29k stars), Publish (code-yeongyu/oh-my-openagent, 70k stars), Factory Complete Issue (mastra-ai/mastra, 29k stars) and Social Publisher (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Factory Ship?

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.