Agent skill

Ship And Monitor

by BuilderIO in BuilderIO/agent-native

Run the normal guarded ship flow, then do requested post-merge checks.

No licenceAuto-check passedDevOps & Cloud

Install Ship And Monitor

skills CLI
$ npx skills add BuilderIO/agent-native --skill ship-and-monitor -a claude-code

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

GitHub CLI
$ gh skill install BuilderIO/agent-native ship-and-monitor --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/agent-native.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ship-and-monitor .claude/skills/ship-and-monitor && 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
ship-and-monitor
GitHub stars
7.1k
Token cost
~1.3k tokens
SKILL.md length
633 words
Files
2
Skills in repo
108
Repo updated
First seen
Licence
None found

At a glance

Run the normal guarded ship flow, then do requested post-merge checks.

  • Works in 4 steps: Confirm the merged PR and merge commit… → Check applicable workflows and package… → If the task changed docs, verify the… → …
  • Standard /ship needs post-merge beta/live
  • SKILL.md covers Deployment split, Host-dependent auth gate, Post-merge monitoring and Related skills
  • Calls gh

What it does

Ship And Monitor is an agent skill from BuilderIO/agent-native. Run the normal guarded ship flow, then do requested post-merge checks. Add independent beta behavior checks only when requested or a concrete deployment-specific risk makes local proof insufficient. Use when standard /ship needs post-merge beta/live, docs, release, or production verification.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in DevOps & Cloud, covering Deployment. It works with GitHub Actions and Netlify. The repository describes itself as: A framework for building agentic apps.

When your agent uses it

  • Standard /ship needs post-merge beta/live
  • Production verification

Example prompts

  • “/ship-and-monitor”

Workflow steps

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

  1. Confirm the merged PR and merge commit are present in origin/main.
  2. Check applicable workflows and package publication. Wait for the affected
  3. If the task changed docs, verify the docs production workflow and
  4. Re-read the merged PR for new review or bot feedback. If actionable

What it can do on your machine

Read from SKILL.md and the folder at commit 1c2de07. 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

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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

Ship And Monitor loads about 1.3k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 633 words of instructions outside code blocks.

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

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 633 words (~1,288 tokens).

“Use the normal /ship workflow, then add the post-merge monitoring described below. Read .agents/skills/ship/SKILL.md and follow every step through /new-branch; /ship intentionally ends after merge and branch rotation. A merge-triggered beta publish alone is not a reason for an independent…”

— opening of SKILL.md by BuilderIO
name
ship-and-monitor
user-invocable
true
scope
dev
metadata.internal
true

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in .agents/skills/ship-and-monitor of BuilderIO/agent-native.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 1c2de07

Compare with similar skills

Ship And Monitor 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.

Ship And Monitor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ship And Monitor this skillBuilderIO/agent-native7.1k—~1.3kAutomated safety check: PassNone
Deploy Setupgarrytan/gstack136k—~11kAutomated safety check: NotesMIT
Memstack Deployment CI CD Pipelinecwinvestments/memstack423—~3.9kAutomated safety check: NotesProprietary
Setup Deployno-session/pstack136—~5.5kAutomated safety check: NotesMIT
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
AI News RadarLearnPrompt/ai-news-radar1.8k—~2.5kAutomated safety check: NotesMIT

Similar skills

  • Deploy Setup

    garrytan/gstack

    Detects where an app deploys, its production URL and health checks, then saves the deploy configuration in CLAUDE.md for /land-and-deploy.

    136k GitHub stars~11k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • A skill your agent uses when the user says 'CI/CD', 'GitHub Actions', 'pipeline', 'continuous integration', 'continuous deployment', 'ci-cd-pipeline', 'automate deploys', or needs to set up…

    423 GitHub stars~3.9k tokensUpdated 15 days ago
    DevOps & CloudAuto-check: notes
  • Setup Deploy

    no-session/pstack

    Configure deployment settings for /land-and-deploy. An agent skill from no-session/pstack.

    136 GitHub stars~5.5k tokensUpdated 6 mo ago
    DevOps & CloudAuto-check: notes
  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes
  • AI News Radar

    LearnPrompt/ai-news-radar

    A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…

    1.8k GitHub stars~2.5k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Use Vercel Action

    amondnet/vercel-action

    Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.

    764 GitHub stars~2.7k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

More from BuilderIO/agent-native

All 108 skills in this repo
  • Bug Trace

    BuilderIO/agent-native

    Find the root cause of a reported bug: take in the report (GitHub issue, Jira ticket, file, or pasted text), trace the failing path hop by hop with each hop's runtime precondition, find the recent…

    7.1k GitHub stars~555 tokensUpdated today
    Auto-check passed
  • Identify Fragile Systems

    BuilderIO/agent-native

    Nightly refactor review: find the systems the last day's commits hit hardest, use three weeks of history to tell fragile from fast-moving, write a plan per systemic fix, and file deduplicated Jira…

    7.1k GitHub stars~957 tokensUpdated today
    Auto-check passed
  • Jira Refactor Findings

    BuilderIO/agent-native

    File and track refactor findings in Jira without duplicates: match a run against existing refactor-findings tickets, create tickets from plan files (Pod, label, attached plan, run link), record…

    7.1k GitHub stars~779 tokensUpdated today
    Auto-check passed
  • System History

    BuilderIO/agent-native

    Blobless-safe git and PR history for this repo. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~727 tokensUpdated today
    Auto-check passed
  • Actions

    BuilderIO/agent-native

    How to create and run agent actions. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~4.5k tokensUpdated today
    Auto-check passed
  • Client Methods

    BuilderIO/agent-native

    Client method surface rules. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Ship And Monitor

What does Ship And Monitor do?

Run the normal guarded ship flow, then do requested post-merge checks. Ship And Monitor is an agent skill from BuilderIO/agent-native. Run the normal guarded ship flow, then do requested post-merge checks.

When should I use Ship And Monitor?

Ship And Monitor fits situations like: standard /ship needs post-merge beta/live; production verification.

How do I install Ship And Monitor in Claude Code?

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

How do I install Ship And Monitor in Codex?

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

Can I use Ship And Monitor 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/agent-native --skill ship-and-monitor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ship-and-monitor, .gemini/skills/ship-and-monitor, .github/skills/ship-and-monitor and .opencode/skills/ship-and-monitor in your project.

What does Ship And Monitor need to run?

Going by SKILL.md and its folder, Ship And Monitor needs the command-line tools its instructions call (gh).

Does Ship And Monitor access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Ship And Monitor 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 Ship And Monitor use?

No licence was found for Ship And Monitor or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Ship And Monitor use?

About 1.3k tokens (SKILL.md is roughly 5.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 Ship And Monitor?

Skills that share tags, products or a category with Ship And Monitor: Deploy Setup (garrytan/gstack, 136k stars), Memstack Deployment CI CD Pipeline (cwinvestments/memstack, 423 stars), Setup Deploy (no-session/pstack, 136 stars) and Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ship And Monitor?

BuilderIO (a GitHub organization) maintains it in BuilderIO/agent-native, which has 7,113 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 10, 2026.

Source: BuilderIO/agent-native on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.