Name: ravelin
Rating: 53.6 (1 reviews)
Author: membranedev

ravelin

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

Quality

60%

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

Quality

Content

63%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 body is a well-structured, actionable integration guide with concrete commands and a validated connection workflow, but it carries some promotional padding and inlines detail that, with no references present, keeps progressive disclosure from scoring higher.

Suggestions

Trim the marketing-style intro paragraph ("Ravelin helps online businesses prevent fraud...") and the "so you can focus on the integration logic rather than auth plumbing" aside to improve token efficiency.

Label the referenced "Step 2" (e.g. add a "## Step 2: Search for actions" heading) so the skip-ahead links resolve to an actual section.

Move the detailed clientAction state-machine and proxy flag table into a references file and link to it from SKILL.md to improve progressive disclosure now that the skill exceeds ~50 lines.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste command blocks, but it includes some unnecessary explanation such as the marketing-style Ravelin intro ("Ravelin helps online businesses prevent fraud...uses machine learning...") and "so you can focus on the integration logic rather than auth plumbing", fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	It provides concrete, executable membrane commands for install, login, connection ensure, action list/run, and proxy with a clear flag table, but placeholders like CONNECTION_ID and --intent "QUERY" leave minor gaps versus fully resolved copy-paste examples.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit validation checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED, check CONFIGURATION_ERROR/SETUP_FAILED) and a feedback loop (re-poll after user action), though the "skip to Step 2" reference points at an unlabeled step, a minor gap.	4 / 5
Progressive Disclosure	There are no bundle files and the content is organized into clear sections, but everything (the detailed clientAction state machine, proxy flag table, best practices) is inlined in a single ~145-line file that could be split, fitting the 'some structure but content that could be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

57%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 pairs a what-statement with an explicit Use-when trigger and leverages a distinct brand name, but its action list is generic and the trigger phrasing could name more concrete Ravelin-specific scenarios.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Ravelin actions such as retrieving customer profiles, searching events, or raising labels/decisions.

Broaden the trigger clause with natural synonyms users would say, e.g. "Use when the user wants to query Ravelin fraud events, manage customer profiles, or handle chargebacks and decisions."

Add file/extension or object keywords (e.g. events, chargebacks, labels, decisions) to improve trigger term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain ("Ravelin integration") but the actions are generic and minimal ("Manage data, records, and automate workflows"), matching the anchor that names a domain with minimal/generic actions rather than concrete capabilities.	2 / 5
Completeness	Both what ("Ravelin integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Ravelin data") are present, but the when-clause could be more explicit about specific trigger scenarios, matching the anchor with both what and when where when is less specific.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Ravelin data" surfaces the natural brand keyword "Ravelin", but it lacks common variations or synonyms beyond the single brand term, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Ravelin brand name gives it a clear, distinct niche with minimal conflict risk, though the generic "manage data, records, and automate workflows" phrasing carries minor overlap with other data-integration skills.	4 / 5
	Total	13 / 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/ravelin/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.