Status
Show the operator the deterministic Main Branch briefing without duplicating
repo-health checks in prose.
CLI facts first: Run mb status --json --peek before answering, then use
that JSON as the source of truth.
Shared source: The portable daily start/status workflow contract lives in
workflows/mb-start-status/workflow.md. This Claude skill is the Claude Code
status shell over that source.
Shared contract markers: Keep these aligned with the shared source.
Required commands:
mb status --json --peek
mb start --json
mb doctor repair --plan
mb doctor repair --plan is read-only. If it exits nonzero while returning plan_interpretation and actions, treat that as findings to review, not as an opaque command failure.
operator_actions (in mb doctor repair and mb update JSON) are steps for the user, such as the plugin-rail switch: show each command and note as theirs to run at a terminal, and never run them yourself.
Required fact paths:
money_path
money_path.policy
money_path.policy.thresholds_declared
money_path.active_bets
money_path.active_bets.unanchored
money_path.active_bets.over_cap
money_path.objects.proof.quality
validation.file_contracts
content_strategy
ranked_actions
relationship_health.gaps
update
readiness
readiness.dimensions.repo_runtime
readiness.dimensions.business_memory
drift.items
runtime.codex_cli
runtime.claude_code
since_last_check
git_activity
journal
checkpoint
onboarding
integrations
github
topology.repo_boundary
brain.bets
brain.bets.active
brain.bets.due_soon
brain.bets.overdue
brain.bets.exit_criteria
brain.bets.exit_criteria.missing
brain.bets.exit_criteria.triggered_failure_signals
brain.bets.exit_criteria.triggered_double_down_signals
vocabulary
Approval gates: updates_repairs_migrations, file_writes, checkpoint,
provider_mutation, publishing_or_spend, customer_contact, private_data,
destructive_operations, and status_marker.
Public/private boundaries: no_secrets, no_raw_provider_exports,
no_customer_member_data, no_private_runtime_settings, and
no_raw_finance_legal_records.
Core route: status facts first, runtime mismatch gates before business routing,
one owner-facing recommendation, business language first, and explicit approval
before mutating the status marker or doing durable writes.
Use recent git_activity and since_last_check from mb status to answer
what changed. Business repos need no separate latest or changelog index.
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, team, bets, journal activity, since-last-check,
readiness,
readiness.dimensions.repo_runtime,
readiness.dimensions.business_memory, vocabulary, content_strategy,
money_path, validation.file_contracts, 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.
Use
money_path when the question is about the path from customer progress
to offer, proof, CTA, channel, push, playbook, page readiness, or outcome
feedback. Keep the language evidence-based: legible, supported, connected,
instrumented. Do not say the offer is good, bad, likely to convert, or ready
to win.
Use validation.file_contracts when the question is about a file that
exists but lacks the business shape needed for the next workflow. Route
offer-shape gaps to /mb-think and ask before editing durable offer files.
Use content_strategy when the question is about content strategy health,
layered channel/account/person files, stale platform rules, or disconnected
content layers. Do not infer that health by parsing markdown yourself unless
status says the section is unavailable.
Use brain.bets.active, brain.bets.due_soon, brain.bets.overdue, and
brain.bets.exit_criteria for active, due-soon, overdue, missing-exit,
triggered kill, triggered double-down, close, update, and narrate moments
before inventing bet state from prose.
For a measurable channel trial with a review or cut point, check brain.bets
and bets/; use a covering bet, or offer /mb-bet before execution.
Use topology.repo_boundary when the operator is deciding whether work
belongs in this business repo, a separate business repo, or a
child repo.
If vocabulary.terms.push defines display words, use them in
operator-facing prose without changing current paths, frontmatter, JSON
keys, validator rules, or command names.
Use team facts and GitHub activity author_display / author_known fields
when naming people; keep unknown contributors as handles.
Do not re-run shell probes that duplicate status facts.
For "what changed?" or "what happened since last time?", answer from
since_last_check.journal first, then top-level journal for recent
context.
- 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.
1---2name: mb-status3description: "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."4loops: [sense]5metadata:6 source: https://skillmd.com/skills/dmthepm/mb-status7---89# Status1011Show the operator the deterministic Main Branch briefing without duplicating12repo-health checks in prose.1314**CLI facts first:** Run `mb status --json --peek` before answering, then use15that JSON as the source of truth.1617**Shared source:** The portable daily start/status workflow contract lives in18`workflows/mb-start-status/workflow.md`. This Claude skill is the Claude Code19status shell over that source.2021**Shared contract markers:** Keep these aligned with the shared source.2223Required commands:2425- `mb status --json --peek`26- `mb start --json`27- `mb doctor repair --plan`2829`mb doctor repair --plan` is read-only. If it exits nonzero while returning `plan_interpretation` and `actions`, treat that as findings to review, not as an opaque command failure.3031`operator_actions` (in `mb doctor repair` and `mb update` JSON) are steps for the user, such as the plugin-rail switch: show each `command` and `note` as theirs to run at a terminal, and never run them yourself.3233Required fact paths:3435- `money_path`36- `money_path.policy`37- `money_path.policy.thresholds_declared`38- `money_path.active_bets`39- `money_path.active_bets.unanchored`40- `money_path.active_bets.over_cap`41- `money_path.objects.proof.quality`42- `validation.file_contracts`43- `content_strategy`44- `ranked_actions`45- `relationship_health.gaps`46- `update`47- `readiness`48- `readiness.dimensions.repo_runtime`49- `readiness.dimensions.business_memory`50- `drift.items`51- `runtime.codex_cli`52- `runtime.claude_code`53- `since_last_check`54- `git_activity`55- `journal`56- `checkpoint`57- `onboarding`58- `integrations`59- `github`60- `topology.repo_boundary`61- `brain.bets`62- `brain.bets.active`63- `brain.bets.due_soon`64- `brain.bets.overdue`65- `brain.bets.exit_criteria`66- `brain.bets.exit_criteria.missing`67- `brain.bets.exit_criteria.triggered_failure_signals`68- `brain.bets.exit_criteria.triggered_double_down_signals`69- `vocabulary`7071Approval gates: `updates_repairs_migrations`, `file_writes`, `checkpoint`,72`provider_mutation`, `publishing_or_spend`, `customer_contact`, `private_data`,73`destructive_operations`, and `status_marker`.7475Public/private boundaries: `no_secrets`, `no_raw_provider_exports`,76`no_customer_member_data`, `no_private_runtime_settings`, and77`no_raw_finance_legal_records`.7879Core route: status facts first, runtime mismatch gates before business routing,80one owner-facing recommendation, business language first, and explicit approval81before mutating the status marker or doing durable writes.8283Use recent `git_activity` and `since_last_check` from `mb status` to answer84what changed. Business repos need no separate latest or changelog index.8586## Workflow87881. Confirm you are in the business repo. If not, ask the operator to `cd` into89 the business repo or pass the repo path.902. Run:9192```bash93mb status --json --peek94```95963. Treat the JSON as the source of truth for setup, update, drift, GitHub,97 onboarding, integrations, team, bets, journal activity, since-last-check,98 readiness, `readiness.dimensions.repo_runtime`,99 `readiness.dimensions.business_memory`, vocabulary, content_strategy,100 money_path, validation.file_contracts, and ranked actions.1014. Summarize the top `ranked_actions` first. For each one, include:102 - title103 - command or slash command104 - reason105 - cited signal summaries1065. Then summarize only the sections that matter for the operator's question.107 Use `money_path` when the question is about the path from customer progress108 to offer, proof, CTA, channel, push, playbook, page readiness, or outcome109 feedback. Keep the language evidence-based: legible, supported, connected,110 instrumented. Do not say the offer is good, bad, likely to convert, or ready111 to win.112 Use `validation.file_contracts` when the question is about a file that113 exists but lacks the business shape needed for the next workflow. Route114 offer-shape gaps to `/mb-think` and ask before editing durable offer files.115 Use `content_strategy` when the question is about content strategy health,116 layered channel/account/person files, stale platform rules, or disconnected117 content layers. Do not infer that health by parsing markdown yourself unless118 status says the section is unavailable.119 Use `brain.bets.active`, `brain.bets.due_soon`, `brain.bets.overdue`, and120 `brain.bets.exit_criteria` for active, due-soon, overdue, missing-exit,121 triggered kill, triggered double-down, close, update, and narrate moments122 before inventing bet state from prose.123 For a measurable channel trial with a review or cut point, check `brain.bets`124 and `bets/`; use a covering bet, or offer `/mb-bet` before execution.125 Use `topology.repo_boundary` when the operator is deciding whether work126 belongs in this business repo, a separate business repo, or a127 child repo.128 If `vocabulary.terms.push` defines display words, use them in129 operator-facing prose without changing current paths, frontmatter, JSON130 keys, validator rules, or command names.131 Use `team` facts and GitHub activity `author_display` / `author_known` fields132 when naming people; keep unknown contributors as handles.133 Do not re-run shell probes that duplicate status facts.134 For "what changed?" or "what happened since last time?", answer from135 `since_last_check.journal` first, then top-level `journal` for recent136 context.1376. If provider readiness is the question, use `integrations.github` and138 `integrations.providers` from status first. If the operator needs choices or139 repair commands, run:140141```bash142mb connect plan143mb connect doctor --json144```145146Summarize GitHub, Cloudflare, Google/Workspace, Meta Ads, and Apify as numbered147business choices. Use the CLI's `next_command` or `repair_command`; do not ask148the operator to paste tokens into files or public issue text.149150## Mutating The Last-Check Marker151152`--peek` is the default inside this skill because a conversation may inspect153status before the operator is ready to record a daily check.154155If the operator explicitly says this is the daily check-in and wants it156recorded, run:157158```bash159mb status --json160```161162Use the new report for the answer.163164## Privacy165166Respect each action and signal's `safe_to_share` field. If `safe_to_share` is167false, keep evidence local to the conversation and do not suggest pasting it168into public GitHub without review.