Skill

mb-status

Thin Main Branch status wrapper. Use when the operator asks what changed, what is healthy, what is stale, what to do next, or wants a daily briefing inside Claude Code.

npx claudepluginhub noontide-co/mainbranch

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Show the operator the deterministic Main Branch briefing without duplicating

SKILL.md

Similar Skills

status

Provides briefing on current tasks, emails, handovers, priorities from GitHub issues, git log, and vault files via bash-regenerated cache. Invoke /status anytime.

2 files

brain-os

status

332

Renders AgentOps workflow dashboard via /status, showing ratchet/task status, epics, learnings count, git state, recent activity, inbox, and session signals. Use for quick project overviews.

1 file4 tools

agentops

apex-status

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

11 tools

tonone

Stats

Stars10

Forks1

Last CommitMay 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Status

Show the operator the deterministic Main Branch briefing without duplicating repo-health checks in prose.

Workflow

Confirm you are in the business repo. If not, ask the operator to cd into the business repo or pass the repo path.

Run:

mb status --json --peek

Treat the JSON as the source of truth for setup, update, drift, GitHub, onboarding, integrations, bets, since-last-check, readiness, and ranked actions.

Summarize the top ranked_actions first. For each one, include:

title
command or slash command
reason
cited signal summaries

Then summarize only the sections that matter for the operator's question. Do not re-run shell probes that duplicate status facts.

If provider readiness is the question, use integrations.github and integrations.providers from status first. If the operator needs choices or repair commands, run:

mb connect plan mb connect doctor --json

Summarize GitHub, Cloudflare, Google/Workspace, Meta Ads, and Apify as numbered business choices. Use the CLI's next_command or repair_command; do not ask the operator to paste tokens into files or public issue text.

Mutating The Last-Check Marker

--peek is the default inside this skill because a conversation may inspect status before the operator is ready to record a daily check.

If the operator explicitly says this is the daily check-in and wants it recorded, run:

mb status --json

Use the new report for the answer.

Privacy

Respect each action and signal's safe_to_share field. If safe_to_share is false, keep evidence local to the conversation and do not suggest pasting it into public GitHub without review.