Name: passslot
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

passslot

PassSlot integration. Manage Organizations. Use when the user wants to interact with PassSlot data.

Quality

65%

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

Quality

Content

67%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 well-structured, actionable guide to driving PassSlot through the Membrane CLI, with executable commands and a clear state-driven connection workflow. Its main weaknesses are a fluffy introductory paragraph and the reliance on action discovery rather than enumerating concrete PassSlot operations.

Suggestions

Trim the opening PassSlot definition and the "so you can focus on the integration logic" commentary; assume Claude knows what a password manager is.

Add at least one concrete PassSlot action example with real input/output (e.g. listing passes or retrieving slot details) instead of relying solely on `action list` discovery.

Clarify the "Step 2" reference by labeling the workflow steps (Step 1 connect, Step 2 search/run) so the skip-ahead instruction is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening PassSlot definition ("a password management application that allows users to securely store and manage their passwords...") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for install, login, connection, action discovery, action runs, and proxy requests with a full flags table, but never shows an actual PassSlot-specific action invocation with real data, leaving a minor gap.	4 / 5
Workflow Clarity	The connect-to-run flow is clearly sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and error handling for CONFIGURATION_ERROR/SETUP_FAILED, but the undefined "Step 2" reference and missing explicit re-validation loop keep it just below a 5.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly headed sections (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references, and the content is appropriately kept inline for a CLI-usage skill; minor gaps only because some detail (the clientAction state machine) could live in a reference.	4 / 5
	Total	15 / 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 covers both what and when with an explicit "Use when" trigger and is anchored to a distinct product niche. Its weaknesses are generic phrasing ("PassSlot integration", "interact with PassSlot data") and a "Manage Organizations" action that is thin and arguably misaligned with the body's Slots/Passes focus.

Suggestions

Replace the generic "PassSlot integration" opener with concrete PassSlot actions that match the body, e.g. "Manage Slots and Passes in PassSlot — list, retrieve details, and create passes."

Strengthen the trigger clause with natural user phrasing, e.g. "Use when the user wants to manage PassSlot passes, slots, or pass data."

Add synonyms or common variations (e.g. "PassSlot passes", "pass details") so the trigger matches how users actually refer to the data.

Dimension	Reasoning	Score
Specificity	It names the PassSlot domain and one concrete action ("Manage Organizations"), matching the anchor for naming a domain plus 1-2 concrete actions, but coverage is not comprehensive and "PassSlot integration" is generic.	3 / 5
Completeness	It answers both "what" ("PassSlot integration. Manage Organizations.") and "when" ("Use when the user wants to interact with PassSlot data."), but the trigger clause is somewhat generic rather than concrete, matching the both-present-but-could-be-more-specific anchor.	4 / 5
Trigger Term Quality	It surfaces the "PassSlot" keyword and the phrase "interact with PassSlot data", but lacks synonyms, file extensions, or common variations a user might naturally say, fitting the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The named PassSlot product gives it a clear, distinct niche with minimal conflict risk, but the generic "Manage Organizations" phrasing introduces minor overlap with org-management skills, fitting the mostly-distinct anchor rather than the fully-distinct 5.	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/passslot/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.