Name: envoy
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

envoy

Envoy integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Envoy data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/envoy/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete, executable Membrane commands and a useful action table, organized into clear sections. Its main weaknesses are an inaccurate verbose intro, and missing validation guidance for the destructive operations the proxy and create actions enable.

Suggestions

Remove or correct the opening 'Envoy is a service mesh' paragraph — it explains a concept Claude already knows and mischaracterizes the visitor-management product this skill integrates.

Add a verification step after running create actions or proxy requests (e.g., re-fetch the created resource or check the response status) to satisfy validation for destructive operations.

Tighten the Best practices bullets by dropping rhetorical padding like 'so you can focus on the integration logic rather than auth plumbing'.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient commands and tables, but the opening 'Envoy is a service mesh...' paragraph is unnecessary concept explanation (and inaccurate for this integration), and best-practices prose contains padding such as 'so you can focus on the integration logic rather than auth plumbing'.	3 / 5
Actionability	Provides copy-paste-ready CLI commands for install, auth, connection, action search/run, and proxy requests plus a concrete popular-actions table, with only minor gaps (the input example uses a generic '{"key": "value"}' rather than a real action payload).	4 / 5
Workflow Clarity	The connection flow is well sequenced with a state machine and polling feedback loop, but the action-runner and proxy sections support destructive operations (create actions, -X DELETE) with no verification step, capping workflow clarity per the destructive-operations rule.	3 / 5
Progressive Disclosure	Single self-contained SKILL.md with clear, well-organized section headers and no nested references; no bundle files are needed for a CLI integration guide, though the file is somewhat long and monolithic.	4 / 5
	Total	14 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description answers both what and when with an explicit 'Use when' clause and a named product, placing it solidly above average. It is held back by a single generic action verb and trigger terms that don't align with Envoy's real visitor-management capabilities.

Suggestions

Replace the generic 'Manage ... and more' with several distinct concrete verbs (e.g., 'List, create, and retrieve reservations, invites, and entries') drawn from the actual action set.

Align the trigger terms with Envoy's real domain (visitors, deliveries, desks, reservations, sign-in flows) instead of CRM entities like Deals and Leads.

Expand the 'Use when' clause to list concrete trigger phrases (e.g., 'when the user mentions visitor sign-ins, desk reservations, or employee check-ins').

Dimension	Reasoning	Score
Specificity	Names the Envoy domain and lists several concrete entities (Persons, Organizations, Deals, Leads, Projects, Activities) but relies on a single generic verb ('Manage ... and more') rather than multiple distinct concrete actions.	3 / 5
Completeness	Provides a clear 'what' (Envoy integration, manage entities) and an explicit 'when' ('Use when the user wants to interact with Envoy data'), though the trigger could name concrete entity-level phrases to be more specific.	4 / 5
Trigger Term Quality	Includes the natural brand keyword 'Envoy' and several entity names, but the listed entities (Deals, Leads) do not match Envoy's actual visitor-management domain and common synonyms/variations are missing.	3 / 5
Distinctiveness Conflict Risk	The named product 'Envoy' gives it a distinct niche with minimal skill overlap, though the CRM-style entity list creates some confusion with the service-mesh meaning of Envoy.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/envoy/SKILL.md
Commit: f484c82

Reviewed: ~19 hours ago

Table of Contents

Discovery Implementation Validation

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.