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

embrace

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

Quality

68%

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

Quality

Content

75%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 an efficient, actionable guide built around concrete Membrane CLI commands with a clear connection-state workflow. It is held back from excellence by minor structural gaps (broken step references, an empty Popular actions section) and slight over-explanation in the intro.

Suggestions

Fix the broken "skip to Step 2" reference by labeling the searching/running sections as Step 2, and rename "1b" to a consistent numbering scheme (e.g. add a "1a" or use plain subheadings).

Populate "Popular actions" with 3-5 actual frequently-used Embrace action names and example invocations, or remove the section if discovery is the intended path.

Trim the introductory product paragraph to one line so the body assumes Claude's competence and earns full conciseness credit.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with light, relevant explanation; minor over-explanation (the introductory product paragraph and "This is the fastest way to get a connection...") could be trimmed, keeping it just below a 5.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases (login, connection ensure, action list/run, request with a full options table), but "Popular actions" only repeats the discovery command without listing actual popular actions, a minor gap.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→search→run sequence is present with state-polling checkpoints and a re-poll feedback loop, but the "skip to Step 2" reference points to no labeled Step 2 and "1b" has no "1a", which are minor structural gaps.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but it is organized into well-separated sections; at ~140 lines it slightly exceeds the simple-skill threshold, and the thin "Popular actions" section is a minor organization gap.	4 / 5
	Total	16 / 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 a product-specific trigger, but relies on generic capability verbs and limited trigger-term variation. It is functional but lacks the concrete, comprehensive specificity of a top-tier description.

Suggestions

Replace generic verbs with concrete Embrace capabilities, e.g. "Query sessions, moments, and crashes; manage user timelines and notes; automate workflows."

Expand trigger terms to include natural user phrases like "Embrace sessions", "mobile crashes", or "Embrace moments" so the skill matches how users actually ask.

Tighten the "what" to list 3-4 specific actions so completeness can reach a 5 alongside the existing "Use when" clause.

Dimension	Reasoning	Score
Specificity	Names the Embrace domain and a couple of actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete like extract/fill/merge, so it is not comprehensive enough for a 4.	3 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and an explicit "when" clause are present; the "when" is reasonably clear but the "what" is vague, so it does not reach the concrete-trigger-phrase level of a 5.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with Embrace data" supplies one relevant keyword pair, but it omits common variations or synonyms (e.g. sessions, moments, crashes, logs) that users would naturally say.	3 / 5
Distinctiveness Conflict Risk	The named brand "Embrace" gives a clear niche with low conflict risk, but the generic action verbs ("manage data, records") leave minor overlap with adjacent data-management skills.	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/embrace/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.