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.

66

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, code-rich skill body with strong executable templates and built-in validation checks. Its main weaknesses are generic boilerplate sections that dilute conciseness and a monolithic single-file structure that underuses progressive disclosure.

Suggestions

Remove or replace the generic 'Instructions' and 'Do not use this skill when' boilerplate with Linkerd-specific guidance, since those sections state things Claude already knows.

Split the longer templates (e.g., ServiceProfile, ServerAuthorization, multi-cluster setup) into reference files under ./references/ and link to them one level deep from SKILL.md to improve progressive disclosure.

Add explicit error-recovery feedback loops to the installation and traffic-split workflows (e.g., 'if linkerd check fails, inspect the reported component and re-run before proceeding') to push workflow clarity toward a 5.

DimensionReasoningScore

Conciseness

The body is mostly lean code and tables, but the generic 'Instructions' ('Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.') and 'Do not use this skill when' sections are boilerplate Claude already knows and could be trimmed; not a 4 because that padding is noticeable.

3 / 5

Actionability

Seven templates plus monitoring and debugging sections provide fully executable, copy-paste-ready bash and YAML covering the common Linkerd cases, matching the top anchor.

5 / 5

Workflow Clarity

Installation is sequenced with explicit validation ('linkerd check --pre' then 'linkerd check') and multi-cluster has a 'check' step; not a 5 because most templates are standalone snippets without explicit feedback loops for error recovery.

4 / 5

Progressive Disclosure

Sections are clearly headed and well ordered, but ~320 lines of detailed manifests are all inlined in SKILL.md with no bundle files or one-level-deep references to split out deeper material; not a 4 because content that belongs in separate files stays inline.

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, third-person description that clearly states the skill's purpose and explicit trigger conditions with concrete Linkerd-specific terms. Minor room to add a few more natural synonyms, but it cleanly answers both what and when.

DimensionReasoningScore

Specificity

Lists several concrete actions ('setting up Linkerd, configuring traffic policies, or implementing zero-trust networking') beyond naming the domain, with only minor coverage gaps; not a 5 because 'patterns' and 'deployments' stay somewhat generic.

4 / 5

Completeness

Explicitly answers both what ('Implement Linkerd service mesh patterns...') and when ('Use when setting up Linkerd, configuring traffic policies...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural terms a user would say ('Linkerd', 'service mesh', 'traffic policies', 'zero-trust networking') are well covered; a few synonyms (e.g., 'mTLS', 'canary', 'retry') are absent, keeping it just below 5.

4 / 5

Distinctiveness Conflict Risk

Names a specific product (Linkerd) with a clear niche and distinct triggers, giving minimal conflict risk with other skills.

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.