Run any Skill in Manus with one click

estatewise-ops

Stars36

Forks21

UpdatedFebruary 28, 2026 at 02:15

Manual playbook for deployment-control, Docker, Kubernetes, Helm, Terraform, Jenkins, and cloud deployment assets in EstateWise.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hoangsonww

hoangsonww/EstateWise-Chapel-Hill-Chatbot

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	estatewise-ops
description	Manual playbook for deployment-control, Docker, Kubernetes, Helm, Terraform, Jenkins, and cloud deployment assets in EstateWise.
argument-hint	["ops-scope"]
disable-model-invocation	true

EstateWise Ops

Invoke this skill manually for infrastructure, deployment-control, or operational workflow changes.

Scope

deployment-control/
docker/
kubernetes/
helm/
terraform/
aws/, azure/, gcp/, oracle-cloud/, hashicorp/
jenkins/, gitlab/
root docs: DEPLOYMENTS.md, DEVOPS.md

Guardrails

Do not run destructive deployment or cluster commands unless the task explicitly requires it.
Preserve rollout semantics for blue-green, canary, and rolling paths.
Keep environment-specific defaults backward compatible unless explicitly asked to change them.
Treat deployment-control as trusted-environment software unless the task adds auth/RBAC deliberately.

Important EstateWise Details

deployment-control/src/server.ts builds shell commands for rollout and scale actions.
Job lifecycle semantics matter: queued, running, succeeded, failed.
UI is served separately via Nuxt on port 3000; API defaults to 4100.
MCP and agentic-ai deployments are often sidecar or bundled runtime patterns, not generic stateless web apps.
MCP is stdio-oriented; deployment docs must preserve that mental model.

Validation

Deployment Control

cd deployment-control
npm run build:api
npm run build:ui

Docker / Compose docs or manifests

Validate referenced image names, env vars, and sidecar assumptions against existing files.

Kubernetes / Helm / Terraform

Prefer static validation and focused manifest inspection unless the task explicitly requests live cluster actions.
Confirm values stay aligned with service ports, env vars, and container entrypoints used elsewhere in the repo.

Documentation To Update

deployment-control/README.md
docker/README.md
kubernetes/README.md
helm/estatewise/README.md
DEPLOYMENTS.md
DEVOPS.md
cloud-specific READMEs when their deployment path changes

Review Questions

Does the change increase operational blast radius?
Does it change the contract between deployment-control API and UI?
Does it change how MCP or agentic-ai is launched or wired?
Are auth/security assumptions still explicitly documented?
Are rollback and status-observability paths still intact?

More from this repository

same repository

estatewise-ai-runtime

hoangsonww/EstateWise-Chapel-Hill-Chatbot

Work on EstateWise MCP, agentic-ai, web-grounding, token flows, and A2A integrations. Use when changing tool behavior, orchestration, runtime flags, MCP wrappers, HTTP/A2A endpoints, or AI integration paths.

2026-02-2836

estatewise-codex-support

hoangsonww/EstateWise-Chapel-Hill-Chatbot

Extend or audit Codex support in the EstateWise repository. Use when changing .codex config, .codex/rules, .agents/skills, AGENTS.md layering, multi-agent roles, project guidance discovery, or Codex-specific documentation and workflows.

2026-02-2836

estatewise-contracts

hoangsonww/EstateWise-Chapel-Hill-Chatbot

Audit producer-consumer alignment in EstateWise when REST, tRPC, MCP, gRPC, A2A, or shared payloads may have changed. Use when one package's change could silently break another package, tool, or doc set.

2026-02-2836

estatewise-engineering

hoangsonww/EstateWise-Chapel-Hill-Chatbot

Execute production-safe code changes in the EstateWise monorepo. Use when implementing or fixing behavior in backend, frontend, MCP, agentic-ai, gRPC, deployment-control, tests, or repo docs. Do not use for pure brainstorming, skill installation, or work outside this repository.

2026-02-2836

estatewise-local-stack

hoangsonww/EstateWise-Chapel-Hill-Chatbot

Run or debug the EstateWise local environment. Use when setting up services, choosing the smallest service combination, checking local endpoints, or troubleshooting environment/config issues. Do not use for routine code implementation unless local run/debugging is the main task.

2026-02-2836

estatewise-ops

hoangsonww/EstateWise-Chapel-Hill-Chatbot

Work on EstateWise deployment-control, Docker, Kubernetes, Helm, Terraform, Jenkins, and cloud deployment assets. Use for infrastructure and operational workflow changes, not ordinary application feature work.

2026-02-2836

EstateWise Ops

Invoke this skill manually for infrastructure, deployment-control, or operational workflow changes.

Scope

deployment-control/

docker/

kubernetes/

helm/

terraform/

aws/, azure/, gcp/, oracle-cloud/, hashicorp/

jenkins/, gitlab/

root docs: DEPLOYMENTS.md, DEVOPS.md

Guardrails

Do not run destructive deployment or cluster commands unless the task explicitly requires it.

Preserve rollout semantics for blue-green, canary, and rolling paths.

Keep environment-specific defaults backward compatible unless explicitly asked to change them.

Treat deployment-control as trusted-environment software unless the task adds auth/RBAC deliberately.

Important EstateWise Details

deployment-control/src/server.ts builds shell commands for rollout and scale actions.

Job lifecycle semantics matter: queued, running, succeeded, failed.

UI is served separately via Nuxt on port 3000; API defaults to 4100.

MCP and agentic-ai deployments are often sidecar or bundled runtime patterns, not generic stateless web apps.

MCP is stdio-oriented; deployment docs must preserve that mental model.

Validation

Deployment Control

cd deployment-control npm run build:api npm run build:ui

Docker / Compose docs or manifests

Validate referenced image names, env vars, and sidecar assumptions against existing files.

Kubernetes / Helm / Terraform

Prefer static validation and focused manifest inspection unless the task explicitly requests live cluster actions.

Confirm values stay aligned with service ports, env vars, and container entrypoints used elsewhere in the repo.

Documentation To Update

deployment-control/README.md

docker/README.md

kubernetes/README.md

helm/estatewise/README.md

DEPLOYMENTS.md

DEVOPS.md

cloud-specific READMEs when their deployment path changes

Review Questions

Does the change increase operational blast radius?

Does it change the contract between deployment-control API and UI?

Does it change how MCP or agentic-ai is launched or wired?

Are auth/security assumptions still explicitly documented?

Are rollback and status-observability paths still intact?