Name: realm
Rating: 49.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

realm

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

Quality

54%

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

Quality

Content

58%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 skill body is well-structured and action-oriented with concrete, executable Membrane CLI commands. Its main weaknesses are an unnecessary introductory concept explanation, redundant action-discovery sections, and missing explicit validation checkpoints for run/proxy operations.

Suggestions

Trim the opening paragraph explaining what Realm is; Claude already knows this and it does not earn its tokens.

Add explicit validation/verification steps after 'action run' and 'membrane request' operations so Claude confirms the result before proceeding.

Consolidate the overlapping 'Searching for actions' and 'Popular actions' sections to remove the redundant action-list command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some unnecessary explanation Claude already knows (e.g. 'Realm is a mobile database solution... offline-first applications... fast, easy to use') and some redundancy between the 'Searching for actions' and 'Popular actions' sections.	3 / 5
Actionability	It provides mostly executable, copy-paste-ready membrane CLI commands with concrete flags and examples covering the common connection/action/request cases, with only minor gaps such as placeholder CONNECTION_ID handling.	4 / 5
Workflow Clarity	There is a rough sequence (install -> auth -> connect -> wait -> search -> run) with state polling, but it is not consistently numbered and the destructive/batch 'action run' and proxy operations lack explicit validation or verification checkpoints, capping it at 3 per rubric guidance.	3 / 5
Progressive Disclosure	Content is well organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to reference; structure is appropriate with only minor organization gaps around the slightly redundant action-listing sections.	4 / 5
	Total	14 / 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 identifies the Realm domain and a few capabilities but relies on generic action verbs and a weak trigger clause. It meets the minimum bar but lacks the concrete, comprehensive, natural-language triggers of a strong description.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Realm-specific actions users would request.

Strengthen the 'Use when' clause with natural trigger phrases users actually say, e.g. 'Use when the user wants to query, create, or update Realm objects or sync local mobile data.'

Add common synonyms or the product's recognizable name variations to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('Realm integration') and a few concrete actions ('Manage data, records, and automate workflows') but these remain generic and not comprehensive, matching the '1-2 concrete actions' anchor.	3 / 5
Completeness	It states a clear 'what' ('Manage data, records, and automate workflows') and has a 'Use when' clause, but the trigger ('when the user wants to interact with Realm data') is generic and weak, capping completeness at 3 per the rubric guidance.	3 / 5
Trigger Term Quality	It includes some relevant keywords ('Realm', 'data', 'records', 'workflows') but misses natural user variations and the literal product name users might say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Realm product name gives it a niche, but the generic 'Manage data, records' framing could overlap with other data/database skills, fitting 'somewhat specific but could still overlap'.	3 / 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/realm/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.