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 essentially a placeholder that repeats the skill name without providing any meaningful information about capabilities or usage triggers. It fails to describe what actions the skill performs (e.g., generating Envoy configurations, validating routes, configuring listeners/clusters) and lacks any explicit guidance on when Claude should select it. The duplicate trigger term suggests auto-generation without human review.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates and validates Envoy proxy configurations including listeners, clusters, routes, and filters.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks about Envoy proxy setup, envoy.yaml configuration, load balancer routing, service mesh config, or Envoy xDS resources.'
Remove the duplicate trigger term and expand with natural keyword variations users would actually say, such as 'envoy yaml', 'envoy listener', 'envoy cluster', 'service mesh', 'L7 proxy config'.
| 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 | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the skill name itself. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'envoy proxy config' repeated twice. Missing natural variations users would 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' does narrow the domain to a specific technology, which provides some distinctiveness. However, the lack of specific actions 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 shell with no actual technical content about Envoy proxy configuration. It consists entirely of auto-generated boilerplate that describes what the skill would do without providing any actionable guidance, code examples, configuration snippets, or workflows. It adds zero value beyond what Claude already knows about Envoy.
Suggestions
Add concrete Envoy configuration examples (e.g., a complete static bootstrap config YAML with listeners, clusters, and routes) that are copy-paste ready.
Include a clear multi-step workflow for common Envoy tasks such as setting up a front proxy, configuring TLS termination, or adding rate limiting, with validation steps (e.g., `envoy --mode validate -c envoy.yaml`).
Remove all boilerplate meta-sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content covering key Envoy concepts like xDS, filter chains, and health checking.
Add references to advanced topics in separate files (e.g., ADVANCED_ROUTING.md, TLS_CONFIG.md, OBSERVABILITY.md) to provide progressive disclosure for complex Envoy configurations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'envoy proxy config' numerous times without adding any actual technical content, and wastes tokens on meta-descriptions of what the skill does rather than providing actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance—no Envoy configuration examples, no YAML snippets, no specific commands, no listener/cluster/route definitions. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. For a topic like Envoy proxy configuration—which involves multi-step processes (listeners, clusters, routes, TLS setup)—the complete absence of any workflow is a critical gap. | 1 / 3 |
Progressive Disclosure | The content is a flat, shallow document with no meaningful structure. There are no references to detailed configuration guides, no links to examples or advanced topics, and the sections that exist contain only generic placeholder text rather than organized technical 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
3e83543
- 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.