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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill envoy-proxy-configActivation
22%This description is severely underdeveloped - it names the technology (Envoy Proxy) but provides no information about what actions the skill performs or when it should be used. The duplicate trigger term and boilerplate 'auto-activating skill' language add no value. Without concrete capabilities listed, Claude cannot make informed decisions about when to select this skill.
Suggestions
Add specific actions the skill performs, e.g., 'Generate Envoy proxy configurations, validate listener/cluster settings, debug routing rules, configure load balancing policies'
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user needs help with Envoy configuration files, service mesh routing, or load balancer setup'
Expand trigger terms to include natural variations: 'envoy.yaml', 'envoy configuration', 'service mesh config', 'Envoy listeners', 'Envoy clusters', 'xDS configuration'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only states it's an 'auto-activating skill' without describing what it actually does with Envoy proxy configurations (e.g., generate, validate, debug, optimize). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains 'envoy proxy config' as a trigger term (duplicated), which is relevant but misses common variations users might say like 'envoy.yaml', 'envoy configuration', 'service mesh', 'load balancer config', or 'envoy listeners/clusters'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'Envoy Proxy' is fairly specific technology, the lack of concrete actions means it could overlap with general DevOps, Kubernetes, or service mesh skills without clear differentiation. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill is an empty template with no actual Envoy proxy configuration content. It contains only generic boilerplate describing what a skill should do without providing any actionable guidance, code examples, configuration snippets, or workflows for Envoy proxy configuration.
Suggestions
Add concrete Envoy configuration examples (e.g., listener, cluster, route configurations in YAML format)
Include a clear workflow for common tasks like setting up a basic proxy, configuring TLS, or implementing rate limiting with validation steps
Provide executable commands for testing and validating Envoy configurations (e.g., envoy --mode validate -c config.yaml)
Add references to detailed documentation for advanced topics like xDS, filters, and observability configuration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual Envoy-specific information. It explains what the skill does in abstract terms without providing any concrete configuration examples or commands that Claude doesn't already know. | 1 / 3 |
Actionability | No concrete code, commands, or Envoy configuration examples are provided. The content only describes capabilities in vague terms like 'provides step-by-step guidance' without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, sequences, or validation checkpoints for Envoy proxy configuration tasks. The skill claims to provide 'step-by-step guidance' but includes none. | 1 / 3 |
Progressive Disclosure | No structure for progressive disclosure exists. There are no references to detailed documentation, examples, or related files. The content is a shallow placeholder with no depth or navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.