How do I install the Estatewise Local Stack skill?

Run npx skillmds@latest add hoangsonww/estatewise-local-stack 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 Local Stack 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 Local Stack?

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 Local Stack free to use?

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

Who published Estatewise Local Stack?

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

Estatewise Local Stack by hoangsonww

Name: Estatewise Local Stack
Author: hoangsonww

Estatewise Local Stack

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.

hoangsonww a4d8d9f 2 files · 2.4 KB Updated Sep 17, 2026

File contents

EstateWise Local Stack

Use this skill when the task is about running or debugging the local environment.

Smallest Useful Service Combinations

Frontend + backend

npm run dev

Or separately:

cd backend && npm start
cd frontend && npm run dev

Backend only

cd backend
npm start

Useful local endpoints:

http://localhost:3001/api-docs
http://localhost:3001/swagger.json
http://localhost:3001/metrics
http://localhost:3001/status

Frontend only

cd frontend
npm run dev

Note: local frontend tRPC endpoints live inside Next.js and do not require the Express backend.

MCP only

cd mcp
npm install
npm run build
npm run client:dev

npm run dev waits for a stdio client and looks idle by design.

Agentic AI + MCP

cd mcp && npm install && npm run build
cd ../agentic-ai && npm install && npm run build
npm run dev "Find 3-bed homes in Chapel Hill and estimate mortgage"

gRPC

cd grpc
npm install
npm run dev

Deployment Control

cd deployment-control
npm run install:all
npm run dev
npm run dev:ui

Frequent Local Failure Modes

Frontend hits the deployed backend unexpectedly because URLs are duplicated across multiple files.
MCP appears hung because it is waiting for a stdio client.
Graph endpoints fail because Neo4j is disabled or not ingested.
Agentic AI fails because MCP was not built or a tool contract drifted.
Deployment-control works locally but is still unsafe by default because it has no built-in auth/RBAC.

Helpful Searches

rg -n "estatewise-backend\\.vercel\\.app|API_BASE_URL" frontend
rg -n "A2A_BASE_URL|API_BASE_URL|FRONTEND_BASE_URL" mcp agentic-ai
rg -n "NEO4J_|PINECONE_|GOOGLE_AI_API_KEY|MONGO_URI|JWT_SECRET" backend mcp agentic-ai

---name: estatewise-local-stackdescription: 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.---# EstateWise Local StackUse this skill when the task is about running or debugging the local environment.## Smallest Useful Service Combinations### Frontend + backend```bashnpm run dev```Or separately:```bashcd backend && npm startcd frontend && npm run dev```### Backend only```bashcd backendnpm start```Useful local endpoints:- `http://localhost:3001/api-docs`- `http://localhost:3001/swagger.json`- `http://localhost:3001/metrics`- `http://localhost:3001/status`### Frontend only```bashcd frontendnpm run dev```Note: local frontend tRPC endpoints live inside Next.js and do not require the Express backend.### MCP only```bashcd mcpnpm installnpm run buildnpm run client:dev````npm run dev` waits for a stdio client and looks idle by design.### Agentic AI + MCP```bashcd mcp && npm install && npm run buildcd ../agentic-ai && npm install && npm run buildnpm run dev "Find 3-bed homes in Chapel Hill and estimate mortgage"```### gRPC```bashcd grpcnpm installnpm run dev```### Deployment Control```bashcd deployment-controlnpm run install:allnpm run devnpm run dev:ui```## Frequent Local Failure Modes- Frontend hits the deployed backend unexpectedly because URLs are duplicated across multiple files.- MCP appears hung because it is waiting for a stdio client.- Graph endpoints fail because Neo4j is disabled or not ingested.- Agentic AI fails because MCP was not built or a tool contract drifted.- Deployment-control works locally but is still unsafe by default because it has no built-in auth/RBAC.## Helpful Searches- `rg -n "estatewise-backend\\.vercel\\.app|API_BASE_URL" frontend`- `rg -n "A2A_BASE_URL|API_BASE_URL|FRONTEND_BASE_URL" mcp agentic-ai`- `rg -n "NEO4J_|PINECONE_|GOOGLE_AI_API_KEY|MONGO_URI|JWT_SECRET" backend mcp agentic-ai`

Frequently asked questions