CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

linkerd-patterns

Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable pattern catalog with excellent copy-paste-ready templates and embedded validation for the install and multicluster workflows. Its weaknesses are padding (generic Instructions / Do-not-use sections, an ASCII diagram of known concepts, a pinned version string) and a fully monolithic single-file structure with no progressive disclosure despite being well over 50 lines.

Suggestions

Delete the content-free 'Do not use this skill when' and 'Instructions' sections, which contain no Linkerd-specific information, and remove or shrink the ASCII architecture diagram of concepts Claude already knows.

Split the longer deep-dive material (AuthorizationPolicy block, multi-cluster setup) into files under references/ and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Add inline post-apply verification to the YAML templates (e.g., 'linkerd viz routes deploy/my-app' after a traffic split, 'linkerd check --proxy' after injection) so each template has a validation checkpoint, and move the pinned version/SHA-256 into a clearly dated or version-agnostic form.

DimensionReasoningScore

Conciseness

The templates and command sections are lean and code-dense, but the document carries pure padding: the "Do not use this skill when" bullets ("The task is unrelated to linkerd patterns") and the generic "Instructions" section ("Clarify goals, constraints, and required inputs") say nothing domain-specific, the ASCII architecture diagram re-explains concepts Claude already knows, and a pinned version "edge-26.11.1" plus full inline SHA-256 is time-sensitive content not placed in a deprecated section. It is not anchor 2 because the padding is a small fraction of the ~355 lines and the core content is highly efficient.

3 / 5

Actionability

Every section provides copy-paste-ready material: a complete checksum-verified install script, seven concrete YAML/bash templates (injection, ServiceProfile with retry budgets, canary HTTPRoute, AuthorizationPolicy, multi-cluster), plus monitoring and debugging command lists. Specific examples cover the common cases end to end, matching the anchor-5 example.

5 / 5

Workflow Clarity

The major workflows embed explicit checkpoints — "linkerd check --pre", "sha256sum --strict -c -", "linkerd check" after install, and "linkerd multicluster check" / "gateways" for verification — with a clear implicit sequence within each template. It is not anchor 5 because the YAML config templates lack inline post-apply validation (e.g., verify a traffic split with `linkerd viz routes`) and there are no error-recovery feedback loops; it is above anchor 3 because key sequences do include explicit validation steps rather than leaving them implicit.

4 / 5

Progressive Disclosure

No bundle files exist and no internal references are used — all ~355 lines live inline in a single file, including self-contained deep dives (the five-resource AuthorizationPolicy block, multi-cluster setup) that could be split into reference files with the SKILL.md as an overview. Section headers are clear and navigation is adequate, which keeps it above anchor 2's "no section headers" case, but the total inlining of content that belongs in separate files matches anchor 3.

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and when to use it, with a named product that makes it highly distinctive. The trigger coverage is good but could add common synonyms like mTLS, canary, or traffic splitting for comprehensiveness.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "setting up Linkerd, configuring traffic policies, or implementing zero-trust networking" — beyond just naming the domain. It falls short of anchor 5 because the lead phrase "Implement Linkerd service mesh patterns" is somewhat abstract and the action list is not fully comprehensive (e.g., no mention of traffic splits, retries, or multi-cluster).

4 / 5

Completeness

Explicitly answers both questions: the "what" ("Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments") and the "when" ("Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead") with concrete trigger phrases, closely matching the anchor-5 example structure. It is not anchor 4 because the 'when' clause is explicit and specific rather than generic.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "Linkerd", "service mesh", "traffic policies", "zero-trust networking", "minimal overhead" — terms a user with this need would plausibly say. Not anchor 5 because common synonyms users actually say are missing, such as "mTLS", "canary", "traffic splitting", or "Kubernetes".

4 / 5

Distinctiveness Conflict Risk

Naming the specific product (Linkerd) carves out a clear niche with distinct triggers; only Linkerd-related requests would match, giving minimal conflict risk with other meshing/proxy skills. It is not anchor 4 because the product name makes it more distinguishable than the 'PDF and Word document files' overlap example.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/linkerd-patterns/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.