Name: twingate
Rating: 65.60000000000001 (1 reviews)
Author: membranedev

twingate

Twingate integration. Manage data, records, and automate workflows. Use when the user wants to interact with Twingate data.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

88%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 content is highly actionable with fully executable commands, a clear validated workflow, and good section organization; minor conciseness padding and slightly dense inline sections are the only gaps.

Suggestions

Trim the introductory 'what is Twingate / ZTNA' explanation since Claude already knows this concept.

Consider splitting the dense 'Popular actions' / proxy flag table into a referenced REFERENCE.md once the skill grows, to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands and minimal padding, but the opening line explaining what Twingate/ZTNA is and 'replacing traditional VPNs' restates a concept Claude already knows, fitting the 'efficient; minor instances of over-explanation that could be trimmed' anchor.	4 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, action run, and proxy requests, plus a concrete flag-options table, matching the 'fully executable; copy-paste ready code or commands; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The flow is clearly sequenced (install -> authenticate -> connect -> search actions -> run/proxy) with explicit state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-and-retry feedback loop, matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.	5 / 5
Progressive Disclosure	As a single-file skill with no bundle files, it is well-organized into clear sections with no nested references, but the 'Popular actions' and 'Best practices' content is somewhat dense inline rather than split into signaled deeper files, matching the 'good structure; most content appropriately placed; minor organization gaps' anchor.	4 / 5
	Total	18 / 20 Passed

Description

70%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 is concise and includes an explicit 'Use when' trigger with a distinctive domain keyword, but the capability list is generic rather than Twingate-specific, which limits specificity and completeness.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with Twingate-specific capabilities such as 'manage Connectors, Resources, Groups, Users, and Security Policies'.

Broaden trigger phrasing to include natural synonyms users might say, e.g. 'Use when the user wants to manage Twingate network access, connectors, resources, or security policies'.

Add a concrete file/extension or product trigger where applicable to strengthen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the Twingate domain and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than Twingate-specific concrete capabilities, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	It states the 'what' ('Manage data, records, and automate workflows') and includes an explicit 'Use when the user wants to interact with Twingate data' trigger, but the 'what' is somewhat high-level, matching the 'has both what and when; when could be more explicit or specific' anchor.	4 / 5
Trigger Term Quality	'Twingate' is a strong domain keyword and 'interact with Twingate data' reflects natural user phrasing, though common synonyms or variations are limited, fitting the 'good keyword coverage; a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	'Twingate' is a distinct niche keyword minimizing conflict risk, though the generic action phrasing ('Manage data, records, and automate workflows') could overlap with other integration skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	15 / 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/twingate/SKILL.md
Commit: f484c82

Reviewed: ~3 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.