Name: yonder
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

yonder

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

Quality

72%

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

Quality

Content

78%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 executable commands and good validation/feedback loops for connection state, but loses points on progressive disclosure (no external references, inlined reference material) and minor conciseness and workflow-numbering issues.

Suggestions

Move the connection-state reference and the proxy flag table into separate reference files (e.g., references/connection-states.md, references/proxy.md) and link to them from the body to improve progressive disclosure.

Fix the inconsistent step numbering: either number the main workflow steps 1-2-3 consistently or remove the stray 'Step 2' / '1b' labels so the sequence is unambiguous.

Dedupe 'Popular actions' with 'Searching for actions' and trim the marketing-style intro paragraph to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and little explanation of concepts Claude already knows, though the marketing-flavored intro paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (npm install, membrane connection ensure, action run, request) plus a flag table and JSON examples covering the common cases.	5 / 5
Workflow Clarity	There is a clear install-auth-connect-search-run sequence with polling and explicit handling of READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR states, but section numbering is inconsistent (a 'Step 2' reference with only a '1b' label) and 'Popular actions' duplicates 'Searching for actions'.	4 / 5
Progressive Disclosure	The file has reasonable section headers but no bundle references and inlines content that could be split (full connection-state reference, proxy flag table); at ~155 lines it does not qualify for the simple-skill exception, matching the 'some structure, content that should be separate is inline' anchor.	3 / 5
	Total	16 / 20 Passed

Description

66%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 product-specific and answers both what and when, which keeps distinctiveness high and completeness solid. Weaknesses are generic action verbs and narrow trigger terms that limit specificity and trigger-term quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Yonder-specific actions a user would request (e.g., 'create and search Spaces, manage Documents and Collections, list and update Members').

Expand the 'Use when...' clause with natural trigger phrases and synonyms a user might actually say (e.g., 'Use when the user wants to query Yonder Spaces, search Documents, or automate Yonder workflows').

Dimension	Reasoning	Score
Specificity	Names the Yonder domain and a couple of actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') and coverage is not comprehensive, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	Provides both a clear 'what' (Yonder integration; manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Yonder data'), though the 'when' could be more specific; not a 5 because trigger phrases are not comprehensive.	4 / 5
Trigger Term Quality	Contains relevant keywords ('Yonder data', 'interact with Yonder data') but misses common variations or synonyms a user might naturally say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named product (Yonder) with a distinct trigger, giving it a clear niche and minimal conflict risk with other skills.	5 / 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/yonder/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.