Chf3198@Megingjord Harness

Operate and maintain the LLM Wiki knowledge system in the Megingjord source workspace.

Operate and tune Crostini Mem Watchdog for low-memory development sessions. Use for status triage, log interpretation, and safe threshold tuning.

Execute IT operations: fleet hardware, service management, and environment provisioning.

Classify tasks into free, fleet, or premium lanes and persist an escalation rationale for the active session.

Dispatch an adversarial cross-family review to a non-Anthropic fleet model. Enforces the cross-family independence contract (Epic #2511) at L1-L5 lifecycle points. Returns ACCEPT/PARTIAL/REJECT verdict + rationale.

Execute operational tasks after validated implementation: runtime controls, git/PR/release flow, and governance checks.

Run a bounded self-annealing review of operating instructions and workflow outcomes. Use this after failures, after long sessions, before merge, or when repeated mismatches appear between intended process and observed execution.

Analyze fleet overlay inventory and recommend optimal Ollama models per device based on hardware constraints, inference tier, and current LLM landscape. Generates pull/delete commands and a safe transition plan.

Adapt the Megingjord harness to a new operator's fleet topology without hand-editing inventory files. Use when first activating the harness on a new host or onboarding a new fleet.

Define and apply expert GitHub policy profiles and control catalogs used by specialized execution skills across ticketing, review/merge, governance, and release flows.

Operate an LLM Wiki knowledge system in any workspace using the Karpathy pattern

Classify a repository by app type and route it to the correct standards branch, policy profile, and verification gates.

Web-augmented cross-family consensus gate: produce/refresh research → fleet/free-cloud red-team rating /100 → Manager reworks on fail → repeat until > gate or cap exhausted. G3-first: fleet → free-cloud; no paid path.

Detect and remediate documentation drift after code, config, workflow, or UX changes. Use after implementation, before merge, and before release.

Route GitHub workflow requests through a capability-first GitHub skill tree with explicit ownership boundaries and minimal overlap.

Define scope, constraints, acceptance criteria, and verification gates before implementation begins.

Adversarial cross-family review of baton artifacts, PRs, and governance docs. Dispatches a non-Anthropic fleet model (cross-family invariant) and returns structured findings with ACCEPT/REJECT/PARTIAL verdicts and hallucination-risk classifications. Operates as a bounded, non-blocking advisory layer.

Initialize a repository so global skills are always loaded first through repository instructions, local hooks, and governance presence checks.

Audit and harden repository profile, community health, discoverability metadata, and contribution surfaces across repos using bounded, evidence-based checks.

Orchestrate single-thread baton handoff across Manager -> Collaborator -> Admin -> Consultant with explicit entry/exit contracts.

Execute the six-phase breaking-change recovery workflow. Invoked from workflow-resilience Tier-3 escalation or manually when a merged commit breaks the runtime, schema, or governance pipeline.

The GitHub issue IS the baton. Manager creates tickets, pre-assigns roles, enforces status transitions through the Agile workflow.

Configure and maintain optimal OpenRouter free model failover for OpenClaw. Prioritized cascade of free models ranked by coding capability, with automatic failover on rate limits, downtime, and errors. Load this skill when configuring models, troubleshooting model availability, or refreshing the free model inventory.

Perform independent post-execution critique, risk scoring, and recommendation synthesis without changing implementation scope.

Make OpenClaw a reusable machine-global execution system for all VS Code Copilot agent chats, regardless of repository, by standardizing routing, observability, and decision checkpoints.

Validate and enforce release version integrity across tags, manifests, changelogs, and publish workflows. Use before tagging, publishing, or when release metadata drift is suspected.

Onboard any repository into a standardized Copilot + CI governance baseline. Use for new repos and first-time sessions to ensure immediate standards adoption.

Apply non-bypass visual/DOM/runtime regression governance for website-static and web-app repositories that use HTML/CSS/JS runtime behavior.

Resolve GitHub feature availability and policy constraints by plan, repo visibility, account type, and enabled settings before recommending governance actions.

Inventory of all network-accessible compute platforms, connection methods, credentials, and specs. Load this skill when a task could benefit from remote execution, offloading, or cross-platform deployment.

Enforce file organization, naming conventions, and app-type-specific project layouts. Use when creating, restructuring, or onboarding a repository.

Prevent secret leakage across git history, package artifacts, logs, and docs. Use when editing workflows, packaging configuration, environment files, or release automation.

Design and audit repository and organization ruleset architecture, including layering, bypass controls, enforcement modes, and merge queue compatibility.

Implement scoped changes and produce validation evidence matching manager-defined gates.

Govern release readiness and incident response flow in GitHub with rollback evidence, hotfix linkage, and follow-up controls.

Apply Agile linkage controls in GitHub using issue types, sub-issues, dependencies, issue-branch/PR linkage, project fields, and built-in automations.

Apply a low-resource operating profile for Playwright MCP + Claude Vision on constrained machines. Use this at session start, before visual QA, or after browser-context/OOM failures. Establishes bounded retries, local-vs-remote execution split, and optimized screenshot/vision practices.

Keep OpenClaw gateway highly available and actively used through mandatory preflight checks, execution routing, and failover controls.

Naming conventions and phase protocol for GitHub ticket lifecycle. Baton workflow in manager-ticket-lifecycle.