configuring-service-meshes
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill configuring-service-meshesConfigure this skill configures service meshes like istio and linkerd for microservices. it generates production-ready configurations, implements best practices, and ensures a security-first approach. use this skill when the user asks to "configure service ... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill is essentially a placeholder that describes what a service mesh configurator should do without providing any actual implementation guidance. It lacks executable code, concrete YAML examples, specific commands, or any actionable content that would help Claude configure Istio or Linkerd. The content is padded with meta-descriptions and generic boilerplate that waste tokens.
Suggestions
Replace the abstract 'Examples' section with actual, executable YAML configurations for Istio and Linkerd (e.g., complete mTLS PeerAuthentication manifest, Linkerd TrafficSplit resource)
Add concrete kubectl/istioctl/linkerd CLI commands for installation, verification, and troubleshooting (e.g., 'istioctl analyze' for validation)
Remove meta-sections like 'How It Works', 'When to Use This Skill', 'Integration', and 'Instructions' that explain the skill rather than provide actionable guidance
Add a validation workflow with explicit checkpoints (e.g., 'After applying config, verify with: kubectl get peerauthentication -A')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding explaining what the skill does rather than how to do it. Sections like 'How It Works', 'When to Use This Skill', and 'Integration' explain concepts Claude already knows and add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples provided. The 'Examples' section describes what the skill 'will do' but never shows actual YAML configurations, kubectl commands, or any copy-paste ready content for Istio or Linkerd setup. | 1 / 3 |
Workflow Clarity | The workflow described is abstract ('Requirement Gathering', 'Configuration Generation', 'Code Delivery') with no actual steps, validation checkpoints, or error recovery guidance. The 'Instructions' section is generic boilerplate with no service mesh-specific workflow. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to external files for detailed configurations, API references, or examples. The structure exists but content that should be detailed (actual configs) is missing entirely. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
33%This description has a truncated capability statement and uses placeholder boilerplate for the trigger guidance, making it largely ineffective for skill selection. While it names specific technologies (istio, linkerd), the incomplete text and generic 'Use when appropriate context detected' provides no actionable selection criteria for Claude.
Suggestions
Complete the truncated description and replace the placeholder 'Use when appropriate context detected' with specific triggers like 'Use when user mentions service mesh, istio, linkerd, sidecar proxy, traffic management, or mTLS configuration'
Add concrete actions such as 'configure traffic routing policies, set up mutual TLS, define circuit breakers, implement canary deployments'
Include file type triggers like '.yaml service mesh configs' or scenario triggers like 'setting up microservice communication security'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (service meshes, istio, linkerd, microservices) and some actions (generates configurations, implements best practices, security-first approach), but lacks comprehensive specific actions like 'configure traffic routing, set up mTLS, define retry policies'. | 2 / 3 |
Completeness | The 'what' is partially present but truncated. The 'when' section is entirely placeholder boilerplate ('Use when appropriate context detected. Trigger with relevant phrases based on skill purpose') providing no actual guidance on when to use this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'istio', 'linkerd', 'service mesh', 'microservices', but the description is truncated ('configure service ...') and the trigger section is generic placeholder text rather than actual natural user phrases. | 2 / 3 |
Distinctiveness Conflict Risk | Mentions specific technologies (istio, linkerd) which helps distinguish it, but the truncated description and generic trigger text could cause overlap with other Kubernetes or infrastructure configuration skills. | 2 / 3 |
Total | 7 / 12 Passed |
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.