Name: whereby
Rating: 52 (1 reviews)
Author: membranedev

whereby

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

Quality

58%

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/whereby/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 is a well-structured, actionable CLI integration guide with strong connection-state validation and feedback loops, slightly held back by minor explanatory padding and the absence of verification guidance for potentially destructive action/proxy calls.

Suggestions

Trim soft prose such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" to improve token efficiency.

Add a verification/check step after running actions and a caution + verify guidance for destructive proxy methods (e.g. DELETE) to strengthen workflow clarity.

Clarify the "Step 2" references by labeling the downstream section or rewording to remove the dangling cross-reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands, but includes some unnecessary explanatory prose ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") and a brief over-explanation of what Whereby is, matching the score-3 anchor of mostly efficient with some tightening possible.	3 / 5
Actionability	Concrete, copy-pasteable commands appear throughout (npm install, membrane login, connection ensure, action run, request) plus a flags table, reaching mostly-executable guidance with only minor gaps such as the referenced but unlabeled "Step 2" and prose-described polling rather than a complete script.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit validation checkpoints and a feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED states plus re-poll after user action), but the action-execution and proxy (DELETE-capable) sections lack post-run verification, leaving minor validation gaps at the score-4 level.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but it is well organized under clear section headers (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, fitting the score-4 anchor of good structure with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

48%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 correctly pairs a what/when structure and leverages a distinct brand name, but its capability verbs are generic and its trigger phrasing omits the natural meeting/video-conferencing terms users would actually say.

Suggestions

Replace generic verbs with concrete Whereby actions, e.g. "Create and manage video meeting rooms, recordings, and participants" instead of "Manage data, records, and automate workflows".

Add natural trigger terms users say, such as "Use when the user wants to create or join Whereby video meetings, manage meeting rooms, or access recordings".

Tighten the "what" clause so it explicitly reflects Whereby's video-conferencing domain rather than read like any CRM/data integration.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the Whereby domain but the actions are generic verbs on generic nouns (data, records) rather than concrete Whereby-specific operations, matching the score-2 anchor.	2 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and a "when" (Use when the user wants to interact with Whereby data) are present, but the "what" is too vague to clearly answer what the skill concretely does, so it does not reach the score-4 bar of both being adequately explicit.	3 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Whereby data" includes the brand keyword but misses natural domain terms users would say (video meetings, video conferencing, meeting rooms), fitting the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The explicit "Whereby integration" brand framing and "interact with Whereby data" trigger give it a mostly-distinct niche with only minor overlap risk against other generic integration skills, matching the score-4 anchor.	4 / 5
	Total	12 / 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/whereby/SKILL.md
Commit: f484c82

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