Wrap Linkerd

Problem

If a script, CI job, or agent workflow needs to interact with Linkerd, scattering service mesh operations across ad hoc commands can make execution order, context, and ownership hard to track. Wrap Linkerd is positioned as a reusable tool for Linkerd-related work in GitHub or automation pipelines.

How It Works

The metadata describes this skill as a Wrapper around Linkerd, a service mesh, rather than as an independent mesh implementation. Its role is to provide a single skill entry point for Linkerd-related steps:
- It wraps Linkerd;
- It is tagged as tool, github, and automation;
- It is listed at version 1.0.0.
In practice, confirm the target Linkerd deployment, namespace, and permission boundary before delegating calls to the wrapper.

Boundaries

The provided material does not specify subcommands, parameters, or telemetry features, so do not assume it covers service discovery, mTLS, routing policy, or observability configuration by itself. For simple Linkerd-adjacent automation, it can act as an entry point; for production traffic policy, rely on Linkerd's official configuration and cluster permissions.