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

Blog Docs Log in Get started

ragic

Ragic integration. Manage Organizations. Use when the user wants to interact with Ragic 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/ragic/SKILL.md

Quality

Content

82%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.

A well-structured, highly actionable Membrane-CLI integration guide whose concrete commands and state-machine handling are its main strengths. Its weaknesses are minor verbosity in the intro and inconsistent step labeling with some section redundancy.

Suggestions

Trim the marketing-flavored intro ('online database and application builder... flexible data management') to a one-line factual description, and drop 'so you can focus on the integration logic rather than auth plumbing'.

Fix the broken cross-references: label an explicit 'Step 1'/'Step 2' (or remove the 'skip to Step 2' / '1b' labels) so the connection flow is unambiguous.

Merge 'Searching for actions' and 'Popular actions' into a single section to remove the duplicated `membrane action list` coverage.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, executable CLI commands, but the intro paragraph ('Ragic is an online database and application builder... flexible data management and workflow solutions') and lines like 'so you can focus on the integration logic rather than auth plumbing' are minor padding that could be trimmed.	4 / 5
Actionability	Fully copy-paste-ready commands cover the common workflow end-to-end (`npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action run`, `membrane request`), plus a thorough flags table — specific examples cover the common cases.	5 / 5
Workflow Clarity	A clear connection state-machine with polling and a CLIENT_ACTION_REQUIRED feedback loop provides real checkpoints, but 'skip to Step 2' references an unlabeled step, '1b' has no '1a', and 'Searching for actions'/'Popular actions' redundantly re-show `membrane action list`.	4 / 5
Progressive Disclosure	Good section structure with clear headers and no nested file references (none needed for this single-file CLI guide), but it is a >50-line monolith with minor organization gaps (the broken step cross-references) rather than an overview pointing to one-level-deep materials.	4 / 5
	Total	17 / 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.

A concise description with an explicit 'Use when' trigger and a distinct named-app niche. It is held back by thin capability specificity and limited trigger-term variation rather than broad coverage of natural phrasings.

Suggestions

Expand 'Manage Organizations' into a few concrete capabilities (e.g., 'Manage Organizations, query and update records, run Ragic reports') to lift specificity.

Add natural trigger variations — e.g., 'Use when the user wants to query, create, or update records in Ragic, or work with Ragic sheets and reports' — to broaden trigger-term coverage.

Tighten the generic 'Ragic integration' opener into a capability statement so the 'what' is as concrete as the 'when'.

Dimension	Reasoning	Score
Specificity	Names the Ragic domain plus one concrete action ('Manage Organizations'), but 'Ragic integration' and 'interact with Ragic data' are generic rather than enumerating concrete capabilities — not comprehensive, fitting the '1-2 concrete actions' anchor.	3 / 5
Completeness	It answers both what ('Ragic integration. Manage Organizations.') and when with an explicit 'Use when the user wants to interact with Ragic data' clause, but the 'when' trigger is broad and the 'what' is thin, so it stops short of the fully concrete-trigger anchor.	4 / 5
Trigger Term Quality	The relevant keywords ('Ragic', 'Ragic data', 'Organizations') are present but limited to essentially the one product name with no synonyms, task variations, or natural phrasings beyond 'interact with Ragic data'.	3 / 5
Distinctiveness Conflict Risk	'Ragic' is a named SaaS app giving it a clear niche and low conflict risk, but the generic phrasing 'interact with Ragic data' leaves minor overlap risk with general data/database 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/ragic/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.