How do I install the Estatewise Ops skill?

Run npx skillmds@latest add hoangsonww/estatewise-ops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Estatewise Ops safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Estatewise Ops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Estatewise Ops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Estatewise Ops?

hoangsonww (@hoangsonww) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Estatewise Ops by hoangsonww — Agent Skill

Name: Estatewise Ops
Author: hoangsonww

Estatewise Ops

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.

hoangsonww 079890e 2 files · 2.2 KB Updated Sep 17, 2026

File contents

EstateWise Ops

Use this skill 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 such as DEPLOYMENTS.md and DEVOPS.md

Guardrails

Do not run destructive deployment or cluster commands unless explicitly requested.
Preserve rollout semantics for blue-green, canary, and rolling paths.
Keep environment defaults backward compatible unless asked to change them.
Remember deployment-control has no built-in auth/RBAC.

EstateWise-Specific Notes

deployment-control/src/server.ts builds shell commands for rollout and scale actions.
Job lifecycle semantics matter: queued, running, succeeded, failed.
UI is separate from the API and typically runs on port 3000; API defaults to 4100.
MCP and agentic-ai deployments often use sidecar or bundled-runtime patterns rather than generic web deployment patterns.
MCP is stdio-oriented; deployment docs and manifests should preserve that model.

Validation

Deployment Control

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

Infra Changes

Prefer focused static validation and manifest inspection unless the task explicitly asks for live environment changes.
Confirm service ports, env vars, and container entrypoints remain aligned with the rest of 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 workflows changed

---name: estatewise-opsdescription: 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.---# EstateWise OpsUse this skill 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 such as `DEPLOYMENTS.md` and `DEVOPS.md`## Guardrails1. Do not run destructive deployment or cluster commands unless explicitly requested.2. Preserve rollout semantics for blue-green, canary, and rolling paths.3. Keep environment defaults backward compatible unless asked to change them.4. Remember `deployment-control` has no built-in auth/RBAC.## EstateWise-Specific Notes- `deployment-control/src/server.ts` builds shell commands for rollout and scale actions.- Job lifecycle semantics matter: `queued`, `running`, `succeeded`, `failed`.- UI is separate from the API and typically runs on port `3000`; API defaults to `4100`.- MCP and agentic-ai deployments often use sidecar or bundled-runtime patterns rather than generic web deployment patterns.- MCP is stdio-oriented; deployment docs and manifests should preserve that model.## Validation### Deployment Control```bashcd deployment-controlnpm run build:apinpm run build:ui```### Infra Changes- Prefer focused static validation and manifest inspection unless the task explicitly asks for live environment changes.- Confirm service ports, env vars, and container entrypoints remain aligned with the rest of 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 workflows changed

Frequently asked questions