envoy-proxy-config
Envoy Proxy Config - Auto-activating skill for DevOps Advanced. Triggers on: envoy proxy config, envoy proxy config Part of the DevOps Advanced skill category.
36
3%
Does it follow best practices?
Impact
96%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/02-devops-advanced/envoy-proxy-config/SKILL.mdQuality
Discovery
7%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 description is extremely minimal and essentially just restates the skill name without providing any useful information about capabilities, use cases, or trigger scenarios. It reads like auto-generated boilerplate rather than a thoughtful description designed to help Claude select the right skill. The repeated trigger term and lack of concrete actions make it nearly useless for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates and validates Envoy proxy configurations including listeners, clusters, routes, and filters. Troubleshoots Envoy config errors and optimizes load balancing settings.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Envoy proxy setup, envoy.yaml configuration, service mesh routing, load balancer configuration, or Envoy xDS APIs.'
Remove the duplicate trigger term 'envoy proxy config' and replace with diverse natural language variations users might actually use, such as 'Envoy YAML', 'proxy configuration', 'service mesh config', 'Envoy listeners/clusters'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only names 'Envoy Proxy Config' without describing what it actually does — no mention of generating configs, validating routes, setting up listeners, clusters, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just restating the skill name as a trigger. There is no explicit 'Use when...' guidance with meaningful context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'envoy proxy config' repeated twice. It misses natural variations users might say like 'envoy configuration', 'envoy yaml', 'load balancer config', 'envoy listeners', 'envoy clusters', 'service mesh', or 'envoy.yaml'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Envoy Proxy' is fairly specific to a particular technology, which provides some distinctiveness. However, the lack of detail about what aspects of Envoy config it handles means it could overlap with general DevOps or proxy configuration skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content about Envoy proxy configuration. It contains only auto-generated boilerplate describing what the skill would do without providing any real guidance, code, configuration examples, or workflows. It adds no value beyond what Claude already knows.
Suggestions
Add concrete Envoy configuration examples (e.g., a complete envoy.yaml with listeners, clusters, and routes) that are copy-paste ready.
Include a step-by-step workflow for common tasks like setting up an Envoy sidecar proxy, configuring TLS termination, or setting up rate limiting, with validation steps (e.g., `envoy --mode validate -c envoy.yaml`).
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content covering specific Envoy patterns like front proxy, service mesh sidecar, and external authorization.
Add references to detailed sub-files for advanced topics (e.g., xDS configuration, Lua filters, WASM extensions) rather than keeping everything abstract.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information about Envoy proxy configuration. It explains what the skill does in abstract terms without providing any actual guidance, wasting tokens on meta-descriptions Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific Envoy concepts. Every section describes rather than instructs, offering nothing executable or actionable. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints—just vague claims like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of boilerplate with no references to detailed materials, no links to configuration examples, and no structured navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.