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.
85
77%
Does it follow best practices?
Impact
100%
1.35xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/linkerd-patterns/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Linkerd service mesh) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the 'what' portion could be more specific about concrete actions beyond the general 'implement patterns' and 'deployments'. The description effectively distinguishes itself from other service mesh tools.
Suggestions
Add more specific concrete actions to the capabilities portion, e.g., 'inject sidecar proxies, configure mTLS, create service profiles, set up traffic splits and retries' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Linkerd service mesh) and some actions ('setting up Linkerd', 'configuring traffic policies', 'implementing zero-trust networking'), but the 'what' portion is somewhat vague with 'implement patterns' and 'deployments' rather than listing multiple concrete specific actions like injecting sidecars, configuring mTLS, creating service profiles, or setting up retries/timeouts. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement Linkerd service mesh patterns for lightweight, security-focused deployments) and 'when' (explicit 'Use when' clause covering setting up Linkerd, configuring traffic policies, or implementing zero-trust networking). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Linkerd', 'service mesh', 'traffic policies', 'zero-trust networking', 'minimal overhead', 'lightweight', 'security-focused'. These cover the main terms a user working with Linkerd would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by specifying 'Linkerd' explicitly, which clearly differentiates it from other service mesh skills (e.g., Istio, Consul Connect). The mention of 'lightweight' and 'security-focused' further narrows the niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, copy-paste ready templates for Linkerd service mesh patterns with good coverage of common use cases. Its main weaknesses are verbosity (architecture diagrams, concept explanations Claude doesn't need) and missing validation/feedback loops for complex multi-step operations like canary deployments and multi-cluster setup. The monolithic structure would benefit from splitting advanced topics into separate referenced files.
Suggestions
Remove the architecture diagram and 'Core Concepts' section - Claude already understands service mesh architecture. Keep only the resource table if it adds value as a quick reference.
Add validation checkpoints to the canary deployment workflow (e.g., 'verify traffic split with `linkerd viz stat`') and multi-cluster setup (e.g., verify service mirroring is working).
Split advanced templates (multi-cluster, HTTPRoute, authorization policies) into separate referenced files to improve progressive disclosure for this lengthy skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The architecture diagram and key resources table add some value but the 'When to Use This Skill' section and 'Core Concepts' header are unnecessary padding. The Do's/Don'ts section restates things Claude would already know (e.g., 'Linkerd defaults are sensible'). The overall content is moderately efficient but could be tightened significantly. | 2 / 3 |
Actionability | Templates are fully executable with real YAML manifests and bash commands that are copy-paste ready. The installation steps, service profiles, traffic splits, authorization policies, and monitoring commands are all concrete and specific with realistic values. | 3 / 3 |
Workflow Clarity | The installation template has a clear sequence with validation (`linkerd check --pre`, `linkerd check`), but other workflows like canary deployments and multi-cluster setup lack validation checkpoints or error recovery steps. There's no feedback loop for verifying that traffic splits are working correctly or that authorization policies are properly applied. | 2 / 3 |
Progressive Disclosure | The content is a monolithic file with all templates inline. For a skill this long (~200+ lines), the advanced templates (multi-cluster, HTTPRoute, authorization policies) could be split into referenced files. The external resource links at the bottom are helpful but the internal organization could benefit from splitting. | 2 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- 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.