Skills linkerd-patterns
📦

linkerd-patterns

Content revision r1 Critical ⚙️ External commands🌐 Network access

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.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
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.

Markdown detail GET /skills/sickn33-linkerd-patterns.md Signed manifest GET /api/skills/sickn33-linkerd-patterns/manifest Signed lockfile GET /api/skills/sickn33-linkerd-patterns/lockfile

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

Critical
v4 • 7/7/2026 Open versioned report

Most 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.

1
Files scanned
322
Lines analyzed
2
Review items
0
False positives ignored

Confirmed security concerns (2)

Critical
SKILL.md:70
Pipe to shell pattern
curl --proto '=https' --tlsv1.2 -sSfL https://run.linkerd.io/install | sh
The command downloads a script from the internet and pipes it directly into sh. This is a classic pipe-to-shell pattern with remote code execution risk.
High
SKILL.md:200-212
Broad Unauthenticated Mesh Access Example
The ServerAuthorization template permits unauthenticated clients from 10.0.0.0/8. This can weaken zero-trust controls if copied without narrowing the source.
The policy explicitly sets unauthenticated access and pairs it with a broad private CIDR. The surrounding text presents it as an example for ingress without a warning.
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.

High
SKILL.md:70
Hardcoded URL
curl --proto '=https' --tlsv1.2 -sSfL https://run.linkerd.io/install | sh
The URL is used in a command that downloads a remote installer and pipes it to sh. Copying this pattern creates a supply-chain execution risk.
Medium
SKILL.md:212
Hardcoded IP address
- cidr: 10.0.0.0/8
The private CIDR appears inside an unauthenticated ServerAuthorization example. Copying it can allow broad internal network access without mesh identity.

Risk Factors

⚙️ External commands (21)
SKILL.md:20 SKILL.md:35-53 SKILL.md:53-68 SKILL.md:68-86 SKILL.md:86-90 SKILL.md:90-111 SKILL.md:111-115 SKILL.md:115-150 SKILL.md:150-154 SKILL.md:154-167 SKILL.md:167-171 SKILL.md:171-213 SKILL.md:213-217 SKILL.md:217-247 SKILL.md:247-251 SKILL.md:251-266 SKILL.md:266-270 SKILL.md:270-285 SKILL.md:285-289 SKILL.md:289-301 SKILL.md:301-312
🌐 Network access (6)
SKILL.md:70 SKILL.md:257 SKILL.md:319 SKILL.md:320 SKILL.md:321 SKILL.md:212

Detected Patterns

Pipe to shell pattern
Audited by: codex View Audit History →
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-linkerd-patterns/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-linkerd-patterns/security.svg)](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/4

BibTeX 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 variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage
wshobson Recommended

wshobson-linkerd-patterns

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 12
Updated

2026-09-09

sickn33 Current

sickn33-linkerd-patterns

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 9
Updated

2026-09-09

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What 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 
Plan a Linkerd installation for my Kubernetes cluster. Include prerequisites, validation checks, namespace injection, and post-install verification steps.
Add service mesh injection 
Show how to enable Linkerd injection for this namespace or workload. Include rollout checks and a safe rollback path.
Design traffic policy 
Design Linkerd traffic policy for this service. Include route metrics, retry budgets, timeouts, and canary routing guidance.
Review zero-trust mesh policy 
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.

Frequently Asked Questions

What is this skill for?
It helps plan and describe Linkerd service mesh setup, traffic policy, authorization, monitoring, and debugging patterns.
Can it install Linkerd for me?
No. It provides command guidance and templates, but users must review and run commands in their own environment.
Does it cover security policy?
Yes. It includes Linkerd Server and ServerAuthorization examples, with review needed before production use.
Does it support multicluster setups?
Yes. It includes multicluster command patterns and service export checks that must be customized per cluster.
What should I customize before use?
Customize namespaces, service names, hostnames, cluster addresses, CIDRs, retry settings, and authorization identities.
Which tools can use this skill?
The skill declares support for Claude, Codex, and Claude Code.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/linkerd-patterns

Ref

816c62b2546ddb1c6a0453e7c781b5e095117819

Maintenance freshness

7/18/2026

Usage

6 downloads · 145 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all