Appearance
Workflow · Operations

Entity Mission Control Bootstrap

Turn a loose cluster of agents into a repeatable ops surface.

LiveOperationsAdvancedExternal bundlev1.3.2
View source
Overview

What this workflow does

Installs from a real external skill bundle that bootstraps the Entity Mission Control helper runtime for a crew of agents with shared scripts, structured task intake, per-agent manifests, and supervised rollout steps.

Availability

How it ships today

Classification
External bundle
Install mode
Manual install
Review status
Source review
Verification mode
Source review

GitHub source specs are not supported by every OpenClaw CLI build. OpenClaw 2026.5.4 accepts ClawHub slugs for `openclaw skills install`, not `github:owner/repo/path`, so this workflow uses a GitHub clone/copy fallback and then runs `install-auto.sh` to install wrappers, write the Entity MC cron block, and verify the result.

Install source

GitHub skill bundle - auto installer fallback

https://github.com/h-mascot/enterprise-crew-skills/tree/main/entity-mc

git clone https://github.com/h-mascot/enterprise-crew-skills.git /tmp/enterprise-crew-skills && mkdir -p skills && cp -R /tmp/enterprise-crew-skills/entity-mc skills/entity-mc && bash skills/entity-mc/install-auto.sh
Workflow record

Bundle anatomy

Bundle id
superada.workflow.entity-mission-control-bootstrap
Entrypoint
SKILL.md
Bundle root
github:henrino3/enterprise-crew-skills/entity-mc
Artifact count
9 described items

A reusable external ops bundle that keeps the helper runtime canonical, installs portable MC operating memory, applies per-agent manifests, creates tasks from structured intake, and gives operators a safe rollout plus rollback path.

Install contract

Can an agent install it now?

Installability
Truly installable now
Method
Manual operator install
Install source spec
github:henrino3/enterprise-crew-skills/entity-mc
Install command
git clone https://github.com/h-mascot/enterprise-crew-skills.git /tmp/enterprise-crew-skills && mkdir -p skills && cp -R /tmp/enterprise-crew-skills/entity-mc skills/entity-mc && bash skills/entity-mc/install-auto.sh

Canonical source: https://github.com/h-mascot/enterprise-crew-skills/tree/main/entity-mc

Agent steps

  1. Agent step 1

    Review the linked GitHub bundle before install so the runtime, manifests, and helper scripts are understood.

  2. Agent step 2

    If `openclaw skills install --help` only accepts a ClawHub slug, do not use the `github:` source spec. Clone the source repo, copy `entity-mc` into the local `skills/entity-mc` workspace path, and run `bash skills/entity-mc/install-auto.sh`.

  3. Agent step 3

    `install-auto.sh` creates an auto manifest for the current workspace, installs wrappers, installs portable MC/intake setup context, writes the auto-pull and stall-check cron entries, then runs verification.

  4. Agent step 4

    Inspect the installed skill locally and verify the installed cron block before wider rollout.

Verification command
bash skills/entity-mc/verify.sh --manifest skills/entity-mc/manifests/auto.env

Current limits

  • OpenClaw 2026.5.4 rejects `github:owner/repo/path` skill source specs as invalid skill slugs; GitHub-source install requires a newer/compatible CLI or the clone/copy/install-auto fallback above.
  • Auto install writes auto-pull and stall-check crons by default; source-specific intake remains off unless explicitly enabled with `--enable-intake true` because it needs an inbox policy.
  • The runtime artifacts live in the external skills repo, not in this website repo.
  • Auto-pull executes existing tasks; automatic task creation requires explicit structured input or a source-specific watcher feeding mc-intake.sh.
  • Portable context is intentionally small; host-specific secrets, private memory, and local paths belong in manifests or local memory, not the public bundle.
Setup

Install steps

  1. Step 1 Review the external bundle source

    Inspect the linked skill files, runtime layout, and manifests before rollout so the install stays deliberate.

  2. Step 2 Install the bundle

    Pull the Entity Mission Control bootstrap workflow into the local OpenClaw environment and run the auto installer. This writes wrappers, installs portable MC/intake setup context, installs the default cron block, and verifies the install.

    git clone https://github.com/h-mascot/enterprise-crew-skills.git /tmp/enterprise-crew-skills && mkdir -p skills && cp -R /tmp/enterprise-crew-skills/entity-mc skills/entity-mc && bash skills/entity-mc/install-auto.sh
  3. Step 3 Review the canonical runtime and manifests locally

    After install, inspect source-scripts/, context/, the per-agent .env manifests, and the optional intake settings before rollout.

  4. Step 4 Run the install helper for the target machine

    Apply the canonical runtime and the matching per-agent manifest on the chosen host.

    bash skills/entity-mc/install.sh --manifest skills/entity-mc/manifests/<agent>.env
  5. Step 5 Verify and keep rollback ready

    Confirm the helper runtime is active on each target agent before removing the previous version.

    bash skills/entity-mc/verify.sh --manifest skills/entity-mc/manifests/<agent>.env
  6. Step 6 Wire structured intake only when a source policy exists

    Use mc-intake.sh directly or feed .entity-mc/intake/inbox.jsonl from a source-specific watcher. Intake cron is off by default.

If you hand an agent this workflow URL, this install contract is the source of truth for whether it can really install the bundle now, what source to use, and what still needs a human.

What you get

  • Shared helper runtime across agents
  • Structured task intake into Mission Control
  • Safe rollout with verification and rollback
  • Per-agent manifests without duplicating core scripts

Workflow includes

  • Installer workflow
  • Verification pass
  • Rollback path
  • Canonical source bundle
  • Structured intake helper
Files

Described artifacts

  • Skill contract skill
    github:henrino3/enterprise-crew-skills/entity-mc/SKILL.md

    Defines the bootstrap workflow, shared runtime assumptions, and rollout guardrails.

  • Canonical helper runtime bundle
    github:henrino3/enterprise-crew-skills/entity-mc/source-scripts/

    Shared Mission Control helper scripts: mc.sh, mc-auto-pull.sh, mc-assign-model.sh, mc-build-context.sh, mc-stall-check.sh, and mc-intake.sh.

  • Structured intake helper script
    github:henrino3/enterprise-crew-skills/entity-mc/source-scripts/mc-intake.sh

    Conservative JSON/JSONL intake helper that dedupes and creates Mission Control tasks from explicit structured signals.

  • Portable MC operating context doc
    github:henrino3/enterprise-crew-skills/entity-mc/context/

    Public-safe MC operating memory: task lifecycle, review/blocker contract, evidence rules, and Entity MC runtime behavior. Installed into .entity-mc/context/ and injected by mc-build-context.sh.

  • Intake setup memory doc
    github:henrino3/enterprise-crew-skills/entity-mc/context/mc-intake-setup.md

    Portable onboarding memory that tells a newly installed workspace how to define intake source policy, candidate JSON/JSONL shape, dedupe keys, review boundaries, and safe enablement before turning on the intake cron.

  • Onboarding flow document doc
    github:henrino3/enterprise-crew-skills/entity-mc/docs/onboarding-flow.md

    End-to-end explanation of install, default crons, portable context, MC intake policy setup, watcher JSONL flow, intake cron enablement, and verification.

  • Per-agent manifests manifest
    github:henrino3/enterprise-crew-skills/entity-mc/manifests/*.env

    Agent-specific env manifests that map the canonical runtime onto each operator without duplicating scripts.

  • Install helper script
    github:henrino3/enterprise-crew-skills/entity-mc/install.sh

    Idempotent installer that stages the runtime, writes wrappers, and installs the marked cron block.

  • Verify and rollback helpers script
    github:henrino3/enterprise-crew-skills/entity-mc/verify.sh and github:henrino3/enterprise-crew-skills/entity-mc/rollback.sh

    Verification and rollback helpers used during supervised rollout.

Before you start

Requirements

  • OpenClaw runtime with skill install access runtime

    The host needs a functioning OpenClaw environment capable of loading local skills and running shell helpers.

  • Mission Control connectivity access

    Target agents must be able to reach the Mission Control system they are being configured to support.

  • Operator review of host mappings review

    A human should validate hostnames, agent ids, and manifest selection before rollout.

Layout

Declared structure

  • github:henrino3/enterprise-crew-skills/entity-mc/
  • github:henrino3/enterprise-crew-skills/entity-mc/SKILL.md
  • github:henrino3/enterprise-crew-skills/entity-mc/source-scripts/
  • github:henrino3/enterprise-crew-skills/entity-mc/source-scripts/mc-intake.sh
  • github:henrino3/enterprise-crew-skills/entity-mc/context/
  • github:henrino3/enterprise-crew-skills/entity-mc/context/mc-intake-setup.md
  • github:henrino3/enterprise-crew-skills/entity-mc/docs/onboarding-flow.md
  • github:henrino3/enterprise-crew-skills/entity-mc/manifests/*.env
  • github:henrino3/enterprise-crew-skills/entity-mc/install.sh
  • github:henrino3/enterprise-crew-skills/entity-mc/verify.sh
  • github:henrino3/enterprise-crew-skills/entity-mc/rollback.sh
Proof

Verification

Verification language now matches reality. Installable bundles can be tested after install, external bundles should be source-reviewed first, and conceptual entries are reviewed as designs until real artifacts exist.

  1. Source bundle review

    Confirm the linked GitHub bundle exposes SKILL.md, source-scripts/, context/, manifests/*.env, install.sh, verify.sh, rollback.sh, and VERSION.

    Expected: The source repository contains the referenced files and directories described by this listing.

  2. Bundle install present

    Confirm the copied skill exists in the local OpenClaw workspace after installation.

    test -f skills/entity-mc/SKILL.md && ls skills/entity-mc

    Expected: The installed workspace path contains SKILL.md, source-scripts/, context/mc-intake-setup.md, manifests/auto.env, install-auto.sh, install.sh, verify.sh, rollback.sh, and VERSION, and the crontab contains exactly one ENTITY_MC block for the agent.

  3. Manifest applied

    Check that the target machine received the intended per-agent manifest and helper runtime files.

    Expected: The target host shows the expected manifest-backed runtime files without duplication drift.

  4. Runtime scripts present

    Confirm the installed scripts directory includes mc.sh, mc-auto-pull.sh, mc-assign-model.sh, mc-build-context.sh, mc-stall-check.sh, and mc-intake.sh.

    ls scripts/mc*.sh

    Expected: All six runtime scripts are present and executable.

  5. Portable context present

    Confirm the installed context pack exists and will be injected into pulled tasks.

    ls .entity-mc/context/*.md && bash scripts/mc-build-context.sh '{"task_id":"0","task_name":"context smoke","task_description":"smoke","skill":"none","context":""}' | grep "Entity MC Operating Context"

    Expected: Context files exist and the generated prompt includes Entity MC Operating Context.

  6. Intake dry run

    Confirm structured intake can build a task payload without mutating Mission Control.

    bash scripts/mc-intake.sh create --title "Entity MC intake smoke" --description "Dry run" --assignee Ada --dry-run

    Expected: JSON output with action=dry_run and a payload containing metadata.intake=true.

  • Verify the linked source layout before install and verify one host first before rolling the bundle out everywhere.
  • Keep the previous helper runtime accessible until the new manifest proves healthy.
  • Compare generated agent state against the canonical runtime to catch drift.

Best used for

  • Standardize agent helper scripts across multiple machines
  • Roll out Mission Control updates without hand-editing every node
  • Reduce drift between operator environments
From the operators

Operator notes

  • This listing describes an externally hosted skill bundle. It does not imply those runtime files are checked into this website repo.