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

slottable

Slottable integration. Manage Users, Organizations, Files, Notes, Activities. Use when the user wants to interact with Slottable 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/slottable/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 body delivers strong, executable Membrane CLI guidance with a clear connection workflow and validation checkpoints. It is held back by minor filler, placeholder gaps, and confusing step numbering rather than any structural failure.

Suggestions

Remove marketing filler (e.g., "so you can focus on the integration logic rather than auth plumbing") and the vague "Use action names and parameters as needed" line to improve token efficiency.

Fix the workflow numbering: label the connect steps explicitly (Step 1: ensure connection, Step 2: search actions, Step 3: run) instead of an orphaned "1b" and an unlabeled "Step 2".

Give the CLIENT_ACTION_REQUIRED branch a small executable script/checklist rather than only a narrative description of the clientAction fields.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary filler such as the marketing line "so you can focus on the integration logic rather than auth plumbing" and the vague "Use action names and parameters as needed", which could be tightened.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action run, and proxy requests, with a clear options table; minor gaps remain (CONNECTION_ID placeholders and the narrative clientAction-state handling rather than scripted steps).	4 / 5
Workflow Clarity	The connect-to-ready flow has a clear sequence with explicit state-check validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but the confusing numbering ("1b" with no "1a", an unlabeled "Step 2") is a minor structural gap keeping it from a 5.	4 / 5
Progressive Disclosure	With no bundle files present, all content lives in one SKILL.md organized under clear, well-ordered sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); structure is good but the single file is somewhat long without splitting deeper reference material out.	4 / 5
	Total	15 / 20 Passed

Description

71%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 clearly names the platform and lists the resource types it manages, with an explicit 'Use when' trigger and low conflict risk. Its main weakness is a generic trigger clause and a single generic verb that under-specify the concrete actions and natural user phrases.

Suggestions

Replace the generic verb 'Manage' with specific actions per resource (e.g., 'Create, update, and list users, organizations, files, notes, and activities').

Expand the 'Use when' clause with concrete natural-language triggers users actually say, such as 'when the user wants to manage bookings, appointments, schedules, or availability in Slottable'.

Add common synonyms (scheduling, booking, appointments) so the description surfaces for those phrasings.

Dimension	Reasoning	Score
Specificity	Lists several concrete resources to manage ("Manage Users, Organizations, Files, Notes, Activities"), giving broad coverage, but the single generic verb "Manage" leaves minor gaps versus a fuller action vocabulary.	4 / 5
Completeness	It answers both 'what' (Slottable integration managing five resource types) and 'when' ("Use when the user wants to interact with Slottable data"), but the 'when' clause is generic rather than listing concrete triggers, so it is not a 5.	4 / 5
Trigger Term Quality	"Slottable" and "Slottable data" are relevant keywords, but the description omits natural synonyms users would say (scheduling, booking, appointments, calendars), matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Slottable is a specific named platform with a distinct trigger ("interact with Slottable data"), giving it a clear niche with minimal risk of matching the wrong skill.	5 / 5
	Total	16 / 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/slottable/SKILL.md
Commit: f484c82

Reviewed: 4 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.