Skip to content
TrustedSkillsbeta
Back to all skills

Linkerd Patterns

Checked
wshobson·vlatest·cloud·MIT

Analyzes Linkerd service mesh configurations to suggest improvements based on established best practices and common patterns.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add wshobson/agents --skill linkerd-patterns -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wshobson

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned wshobson/agents at 46891e7e60.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 290 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The linkerd-patterns skill provides a set of predefined patterns and configurations related to Linkerd, a service mesh designed for cloud-native applications. It enables users to implement best practices for service discovery, traffic management, observability, and security within their Kubernetes environments.

When to use it

  • When setting up a new service mesh in a Kubernetes cluster using Linkerd.
  • When looking to optimize existing microservices communication with advanced routing rules.
  • When needing to enforce consistent observability across services for debugging and monitoring purposes.
  • When implementing zero-trust security policies between services.

Key capabilities

  • Predefined configurations for service discovery and load balancing
  • Traffic control patterns such as retries, timeouts, and circuit breakers
  • Integration with observability tools like Prometheus and Grafana
  • Security patterns including mutual TLS and access control

Example prompts

  • "Implement a Linkerd pattern for automatic retries on failed requests."
  • "Set up service mesh observability using the linkerd-patterns configuration."
  • "Apply zero-trust security policies between microservices with Linkerd."

Tips & gotchas

  • Ensure your Kubernetes cluster is properly configured and compatible with Linkerd before applying these patterns.
  • Review each pattern's documentation to understand its impact on existing service behavior.