Name: nylas
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

nylas

Nylas integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nylas 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/nylas/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 Nylas through the Membrane CLI, with concrete commands and a validated connection workflow. Its main weakness is conciseness, as the intro and a few asides explain context Claude already knows.

Suggestions

Trim the intro paragraph ('Nylas provides APIs for developers...') and the 'so you can focus on the integration logic rather than auth plumbing' aside; keep only what Claude cannot infer.

Resolve the dangling 'skip to Step 2' reference by either labeling the 'Searching for actions' section as Step 2 or removing the cross-reference.

Add one fully-worked end-to-end example with concrete values (connect -> search -> run) so the common case is copy-paste ready without placeholder substitution.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the intro paragraph explaining what Nylas is and phrasing like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanations Claude does not need, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level at 4.	3 / 5
Actionability	Concrete, copy-paste-ready commands are provided throughout (install, login, connection ensure, action list/run, proxy with a flags table), but placeholders (CONNECTION_ID, QUERY, actionId) and the absence of a fully-worked end-to-end example leave minor gaps, matching 'mostly executable guidance; concrete code or commands with minor gaps' rather than fully covering common cases at 5.	4 / 5
Workflow Clarity	The connection flow has an explicit sequence with validation checkpoints (poll to READY, clientAction handling, CONFIGURATION_ERROR/SETUP_FAILED) and a re-poll feedback loop, but the dangling 'skip to Step 2' reference with no labeled Step 2 is a minor sequencing gap, fitting 'clear sequence with most checkpoints present; minor validation gaps' rather than the fully explicit level at 5.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized into clearly headed sections (install, auth, connecting, searching, actions, proxy, best practices), giving good structure with only minor gaps like the bare 'Nylas Overview' bullet list of resources with no detail, matching 'good structure; most content appropriately placed; minor organization gaps' rather than the well-signaled one-level reference level at 5.	4 / 5
	Total	15 / 20 Passed

Description

50%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 names the Nylas niche and includes an explicit 'Use when' trigger, but its capability language is generic and it lacks the natural terms (email, calendar, contacts) users would actually say. Distinctiveness is decent thanks to the named product, though generic verbs create minor overlap risk.

Suggestions

Replace the generic action verbs with concrete Nylas capabilities, e.g. 'Read and sync email, calendar events, and contacts, and automate Nylas workflows.'

Expand the trigger terms to the natural phrases users say, e.g. 'Use when the user wants to interact with Nylas email, calendars, or contacts, or sync Nylas data.'

Keep the description in third person (it already is) and avoid over-claiming 'automate workflows' without naming what can be automated.

Dimension	Reasoning	Score
Specificity	The description names the Nylas domain but the actions are minimal and generic ("Manage data, records, and automate workflows") rather than concrete capabilities, fitting the 'names the domain but actions are minimal or generic' anchor and falling below the 1-2 concrete actions expected at 3.	2 / 5
Completeness	Both a 'what' ("Nylas integration. Manage data, records, and automate workflows.") and an explicit 'when' ("Use when the user wants to interact with Nylas data.") are present, but the trigger could be more specific (e.g. naming email/calendar), matching the 'has both what and when; when could be more explicit' anchor rather than the concrete-trigger-phrases level at 5.	4 / 5
Trigger Term Quality	The only keyword is "Nylas" / "Nylas data"; it omits the natural phrases a user would actually say (email, calendar, contacts, sync), matching 'one or two generic keywords; missing the natural phrases users say' rather than the synonym coverage at 3.	2 / 5
Distinctiveness Conflict Risk	"Nylas" is a named product giving it a clear niche with minimal conflict risk, but the generic verbs (manage data, automate workflows) leave minor overlap risk with other data-integration skills, fitting 'mostly distinct; minor overlap risk' rather than the minimal-risk anchor at 5.	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/nylas/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.