Name: gatekeeper
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

gatekeeper

Gatekeeper integration. Manage Users, Organizations. Use when the user wants to interact with Gatekeeper data.

Quality

69%

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/gatekeeper/SKILL.md

Quality

Content

76%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 a strong, executable CLI integration guide with a well-structured connection workflow, but it lacks validation/verification checkpoints for its batch and destructive create/update actions, capping workflow clarity. Trimming minor padding would further improve token efficiency.

Suggestions

Add a validation/verification step after create/update/delete actions (e.g., re-run the corresponding get/list action to confirm the change took effect) to satisfy the feedback-loop requirement for batch/destructive operations.

Trim non-essential padding such as the introductory "Gatekeeper is a SaaS application..." paragraph and phrases like "This is the fastest way to get a connection" to improve conciseness.

Consider moving the large popular-actions table into a separate reference file (e.g., ACTIONS.md) and linking it from the body to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-ready CLI commands, but contains minor over-explanation such as the intro paragraph on what Gatekeeper is and phrases like "so you can focus on the integration logic rather than auth plumbing".	4 / 5
Actionability	Provides fully executable, copy-paste ready commands throughout (install, login, connection ensure/get, action list/run, request proxy) with concrete parameter examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear state-machine sequence with explicit polling and branch handling, but batch/destructive operations (create/update/delete contracts, vendors, requests) lack any validation or verification step, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (install, auth, connecting, searching, popular actions, running, proxy, best practices); the large inlined actions table could arguably live in a separate reference file, but navigation is otherwise easy.	4 / 5
	Total	16 / 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 is adequate, stating both the domain and an explicit use-when trigger, but it is generic about capabilities ("Manage Users, Organizations") and lacks specific natural trigger phrases. Tightening the action list and adding concrete trigger terms would lift it.

Suggestions

Replace the generic "Manage Users, Organizations" with several concrete actions (e.g., create/update contracts, vendors, requests, tasks) to match the popular-actions table in the body.

Add natural trigger phrases users would actually say, such as "Gatekeeper contracts, vendors, or access requests", to improve trigger term quality.

Make the use-when clause more specific by naming the entities and tasks (e.g., "Use when managing Gatekeeper contracts, vendors, requests, or tasks") instead of the generic "interact with Gatekeeper data".

Dimension	Reasoning	Score
Specificity	Names the Gatekeeper domain and two concrete actions ("Manage Users, Organizations") but offers only minimal, generic actions rather than comprehensive coverage.	3 / 5
Completeness	Explicitly answers both what ("Manage Users, Organizations") and when ("Use when the user wants to interact with Gatekeeper data"), though the when clause is generic rather than trigger-specific.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Gatekeeper data", "Users", "Organizations") but misses the common natural variations or synonyms a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	"Gatekeeper integration" carves a clear, distinct niche with minimal overlap risk, though "Manage Users, Organizations" is broad enough to risk minor overlap with generic admin skills.	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/gatekeeper/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.