Loading...
Loading...
Support local workflow platform development in the DAP workspace across frontend, backend, and infra teams. Provides access to Kubernetes (Kind), Tilt service management, database queries, and troubleshooting. Use when building backend/API features, adjusting infra configurations, checking logs, running tests, or debugging issues against locally deployed workflow engine components.
npx skill4agent add lgariv-dn/frontend-skills workflow-local-dev| Task | Command |
|---|---|
| Check pods | |
| Restart component | |
| View component logs | |
workflow-catalogworkflow-executions-apiworkflow-engine-workerworkflow-consumerworkflow-validatorworkflows-workerstandalone-tasks-workerbash .cursor/skills/workflow-local-dev/scripts/check-pods.shbash .cursor/skills/workflow-local-dev/scripts/restart-service.sh <service-name>
# Example: bash .cursor/skills/workflow-local-dev/scripts/restart-service.sh catalogbash .cursor/skills/workflow-local-dev/scripts/tail-logs.sh <service-name>
# Example: bash .cursor/skills/workflow-local-dev/scripts/tail-logs.sh executions-apibash .cursor/skills/workflow-local-dev/scripts/db-query.sh "<SQL query>"
# Example: bash .cursor/skills/workflow-local-dev/scripts/db-query.sh "SELECT * FROM workflow_engine.workflows ORDER BY created_at DESC LIMIT 5"kubectl get pods --context kind-kindtilt trigger workflow-<service>kubectl logs -f <pod> --context kind-kindbash .cursor/skills/workflow-local-dev/scripts/db-query.sh "<SQL query>"kubectl get pods --context kind-kind
kubectl describe pod <pod-name> --context kind-kind
kubectl logs -f <pod-name> --context kind-kind# Use the db-query script (runs psql inside the postgres pod)
bash .cursor/skills/workflow-local-dev/scripts/db-query.sh "SELECT * FROM workflow_engine.workflows ORDER BY created_at DESC LIMIT 5"pulsar-admin topics stats persistent://public/dap/<topic>
pulsar-client consume persistent://public/dap/<topic> -s test-sub -n 10kind-kindTool: pods_list
Arguments: { "labelSelector": "app=workflow-catalog" }Tool: pods_list
Arguments: {}Tool: pods_log
Arguments: {
"name": "workflow-catalog-xxxxx",
"namespace": "default",
"tail": 100
}Tool: pods_log
Arguments: {
"name": "workflow-catalog-xxxxx",
"namespace": "default",
"previous": true
}Tool: pods_exec
Arguments: {
"name": "postgres-xxxxx",
"namespace": "default",
"command": ["psql", "-U", "postgres", "-d", "temporal", "-c", "SELECT * FROM workflow_engine.workflows ORDER BY created_at DESC LIMIT 5"]
}Tool: pods_delete
Arguments: {
"name": "workflow-catalog-xxxxx",
"namespace": "default"
}Tool: pods_get
Arguments: {
"name": "workflow-catalog-xxxxx",
"namespace": "default"
}Tool: events_list
Arguments: { "namespace": "default" }Note: When using MCP tools, you don't need to specifyas it defaults tocontext. The MCP approach is useful when you want the agent to directly interact with the cluster without spawning shell processes.kind-kind