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 --peekmb start --jsonmb 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.
Required fact paths:
money_pathmoney_path.policymoney_path.policy.thresholds_declaredmoney_path.active_betsmoney_path.active_bets.unanchoredmoney_path.active_bets.over_capmoney_path.objects.proof.qualityvalidation.file_contractscontent_strategyranked_actionsupdatereadinessreadiness.dimensions.repo_runtimereadiness.dimensions.business_memorydrift.itemsruntime.codex_cliruntime.claude_codesince_last_checkjournalcheckpointonboardingintegrationsgithubtopology.repo_boundarybrain.betsbrain.bets.activebrain.bets.due_soonbrain.bets.overduebrain.bets.exit_criteriabrain.bets.exit_criteria.missingbrain.bets.exit_criteria.triggered_failure_signalsbrain.bets.exit_criteria.triggered_double_down_signalsvocabulary
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.
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.
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.4---56# Status78Show the operator the deterministic Main Branch briefing without duplicating9repo-health checks in prose.1011**CLI facts first:** Run `mb status --json --peek` before answering, then use12that JSON as the source of truth.1314**Shared source:** The portable daily start/status workflow contract lives in15`workflows/mb-start-status/workflow.md`. This Claude skill is the Claude Code16status shell over that source.1718**Shared contract markers:** Keep these aligned with the shared source.1920Required commands:2122- `mb status --json --peek`23- `mb start --json`24- `mb doctor repair --plan`2526`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.2728Required fact paths:2930- `money_path`31- `money_path.policy`32- `money_path.policy.thresholds_declared`33- `money_path.active_bets`34- `money_path.active_bets.unanchored`35- `money_path.active_bets.over_cap`36- `money_path.objects.proof.quality`37- `validation.file_contracts`38- `content_strategy`39- `ranked_actions`40- `update`41- `readiness`42- `readiness.dimensions.repo_runtime`43- `readiness.dimensions.business_memory`44- `drift.items`45- `runtime.codex_cli`46- `runtime.claude_code`47- `since_last_check`48- `journal`49- `checkpoint`50- `onboarding`51- `integrations`52- `github`53- `topology.repo_boundary`54- `brain.bets`55- `brain.bets.active`56- `brain.bets.due_soon`57- `brain.bets.overdue`58- `brain.bets.exit_criteria`59- `brain.bets.exit_criteria.missing`60- `brain.bets.exit_criteria.triggered_failure_signals`61- `brain.bets.exit_criteria.triggered_double_down_signals`62- `vocabulary`6364Approval gates: `updates_repairs_migrations`, `file_writes`, `checkpoint`,65`provider_mutation`, `publishing_or_spend`, `customer_contact`, `private_data`,66`destructive_operations`, and `status_marker`.6768Public/private boundaries: `no_secrets`, `no_raw_provider_exports`,69`no_customer_member_data`, `no_private_runtime_settings`, and70`no_raw_finance_legal_records`.7172Core route: status facts first, runtime mismatch gates before business routing,73one owner-facing recommendation, business language first, and explicit approval74before mutating the status marker or doing durable writes.7576## Workflow77781. Confirm you are in the business repo. If not, ask the operator to `cd` into79 the business repo or pass the repo path.802. Run:8182```bash83mb status --json --peek84```85863. Treat the JSON as the source of truth for setup, update, drift, GitHub,87 onboarding, integrations, team, bets, journal activity, since-last-check,88 readiness, `readiness.dimensions.repo_runtime`,89 `readiness.dimensions.business_memory`, vocabulary, content_strategy,90 money_path, validation.file_contracts, and ranked actions.914. Summarize the top `ranked_actions` first. For each one, include:92 - title93 - command or slash command94 - reason95 - cited signal summaries965. Then summarize only the sections that matter for the operator's question.97 Use `money_path` when the question is about the path from customer progress98 to offer, proof, CTA, channel, push, playbook, page readiness, or outcome99 feedback. Keep the language evidence-based: legible, supported, connected,100 instrumented. Do not say the offer is good, bad, likely to convert, or ready101 to win.102 Use `validation.file_contracts` when the question is about a file that103 exists but lacks the business shape needed for the next workflow. Route104 offer-shape gaps to `/mb-think` and ask before editing durable offer files.105 Use `content_strategy` when the question is about content strategy health,106 layered channel/account/person files, stale platform rules, or disconnected107 content layers. Do not infer that health by parsing markdown yourself unless108 status says the section is unavailable.109 Use `brain.bets.active`, `brain.bets.due_soon`, `brain.bets.overdue`, and110 `brain.bets.exit_criteria` for active, due-soon, overdue, missing-exit,111 triggered kill, triggered double-down, close, update, and narrate moments112 before inventing bet state from prose.113 Use `topology.repo_boundary` when the operator is deciding whether work114 belongs in this business repo, a separate business repo, or a115 child repo.116 If `vocabulary.terms.push` defines display words, use them in117 operator-facing prose without changing current paths, frontmatter, JSON118 keys, validator rules, or command names.119 Use `team` facts and GitHub activity `author_display` / `author_known` fields120 when naming people; keep unknown contributors as handles.121 Do not re-run shell probes that duplicate status facts.122 For "what changed?" or "what happened since last time?", answer from123 `since_last_check.journal` first, then top-level `journal` for recent124 context.1256. If provider readiness is the question, use `integrations.github` and126 `integrations.providers` from status first. If the operator needs choices or127 repair commands, run:128129```bash130mb connect plan131mb connect doctor --json132```133134Summarize GitHub, Cloudflare, Google/Workspace, Meta Ads, and Apify as numbered135business choices. Use the CLI's `next_command` or `repair_command`; do not ask136the operator to paste tokens into files or public issue text.137138## Mutating The Last-Check Marker139140`--peek` is the default inside this skill because a conversation may inspect141status before the operator is ready to record a daily check.142143If the operator explicitly says this is the daily check-in and wants it144recorded, run:145146```bash147mb status --json148```149150Use the new report for the answer.151152## Privacy153154Respect each action and signal's `safe_to_share` field. If `safe_to_share` is155false, keep evidence local to the conversation and do not suggest pasting it156into public GitHub without review.
noontide-co