Skill Detail
Swap a local service into a live Kubernetes environment to debug real cluster traffic before rollout with Telepresence
Intercept a Kubernetes service and route live cluster traffic into a local process so debugging happens against real dependencies before release.
Runbooks & DiagnosticsMulti-Framework
Runbooks & Diagnostics
Multi-Framework
Security Reviewed
⭐ 7.2k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill swap-a-local-service-into-a-live-kubernetes-environment-to-debug-real-cluster-traffic-before-rollout-with-telepresence
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Telepresence CLI, kubectl access, kubeconfig for the target cluster, a locally runnable service, and permission to create intercepts in the namespace
Install & setup
Install the Telepresence CLI from the upstream packages or release binaries, connect it to the target Kubernetes cluster with working kubectl credentials, then run the documented intercept workflow against the service you want to replace locally.
Author
telepresenceio
Publisher
Organization
Last updated
Apr 17, 2026
Quick brief
Use Telepresence when an agent needs to replace or intercept one service inside a running Kubernetes environment so local code can handle real in-cluster requests. A user should invoke this instead of using Kubernetes normally when the task is live dependency-aware debugging or pre-rollout verification, not ordinary deployment or cluster administration. The scope boundary is tight and skill-shaped: intercepting a workload and bridging local execution into cluster traffic, not listing a general Kubernetes platform or networking product.