linkerd-patterns
Implement Linkerd Service Mesh Patterns
Kubernetes teams need repeatable Linkerd patterns for secure service communication and traffic management. This skill provides templates, commands, and checks for Linkerd setup, policy, routing, and observability.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "linkerd-patterns" from https://skillstore.io/skills/sickn33-linkerd-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-linkerd-patterns/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "linkerd-patterns". Plan Linkerd for a new payments namespace.
Expected outcome:
- Prerequisites and cluster checks are listed first.
- Namespace injection is planned with rollout verification.
- Post-install checks cover proxy health, mTLS status, and metrics visibility.
Using "linkerd-patterns". Create a canary rollout approach for an API service.
Expected outcome:
- The response separates stable and canary backends.
- It recommends gradual traffic weights and rollback thresholds.
- It includes monitoring points for success rate, latency, and retries.
Using "linkerd-patterns". Review a Linkerd authorization policy for ingress traffic.
Expected outcome:
- The response flags broad unauthenticated access.
- It suggests meshTLS identities where possible.
- It recommends narrow network sources when unauthenticated ingress is unavoidable.
Security Audit
CriticalMost static shell execution alerts are Markdown formatting false positives. The audit confirms a critical curl-to-sh installer pattern and a broad unauthenticated authorization example that need remediation.
Confirmed security concerns (2)
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (21)
🌐 Network access (6)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-linkerd-patterns/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-linkerd-patterns?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-linkerd-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-linkerd-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-linkerd-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). linkerd-patterns security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-linkerd-patterns/audits/4BibTeX citation
@techreport{sickn33-sickn33-linkerd-patterns-2026,
author = {sickn33},
title = {linkerd-patterns security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-linkerd-patterns/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "linkerd-patterns security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-linkerd-patterns/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-linkerd-patterns:audit:4"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
wshobson-linkerd-patterns
2026-08-21
sickn33-linkerd-patterns
2026-08-21
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Deploy a Linkerd baseline
Plan installation, namespace injection, and validation steps for a Kubernetes service mesh rollout.
Tune service traffic behavior
Design retries, timeouts, canary traffic splits, and route-level metrics for application services.
Review mesh access controls
Draft Server and ServerAuthorization policies that align with service identity and ingress requirements.
Try These Prompts
Plan a Linkerd installation for my Kubernetes cluster. Include prerequisites, validation checks, namespace injection, and post-install verification steps.
Show how to enable Linkerd injection for this namespace or workload. Include rollout checks and a safe rollback path.
Design Linkerd traffic policy for this service. Include route metrics, retry budgets, timeouts, and canary routing guidance.
Review this Linkerd authorization plan for zero-trust risk. Identify overly broad access, missing service identities, and safer policy alternatives.
Best Practices
- Run Linkerd pre-checks and post-install checks before changing production workloads.
- Replace every placeholder namespace, service name, URL, and CIDR before applying examples.
- Review generated manifests and security policies before applying them to a cluster.
Avoid
- Do not pipe remote installers directly into a shell.
- Do not allow unauthenticated access from broad network ranges.
- Do not copy example traffic policies without service-specific retry and timeout limits.