Name: revel-systems
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

revel-systems

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

Quality

66%

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

Quality

Content

76%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 highly actionable with concrete executable commands and a solid connection workflow, but it lacks verification steps around destructive create/update operations and carries minor verbosity. Structure is good for a single-file skill with no bundle references.

Suggestions

Add a verification step after create/update operations, e.g. re-fetch the resource with get-order to confirm the change applied.

Fix the dangling "skip to Step 2" reference by labeling the action-search/run sections as numbered steps.

Trim the introductory "so you can focus on the integration logic rather than auth plumbing" filler to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and a tabular action reference, though phrases like "so you can focus on the integration logic rather than auth plumbing" and the introductory POS explanation are minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection, action listing/running, and proxying, plus a concrete popular-actions table with keys — covering the common cases directly.	5 / 5
Workflow Clarity	The connection flow is well sequenced with an explicit state-polling feedback loop, but the create/update order and payment operations are destructive/batch-like with no validation or verification steps, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The single file is well organized into clear sections (Overview, Working with Revel, Popular actions, Best practices) with no nested references, though the 20-row action table is borderline reference material that could live in a separate file.	4 / 5
	Total	16 / 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 has a clear trigger and answers both what and when, but its capability list is generic rather than naming concrete Revel operations. Tightening the verbs to actual entities (orders, products, payments) would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Revel actions, e.g. "List and create orders, products, customers, and payments in Revel Systems."

Add natural trigger synonyms users say, such as POS, point of sale, orders, or payments, not just "Revel Systems data".

Keep the explicit "Use when..." clause but tie the when to concrete intents like managing POS orders or inventory.

Dimension	Reasoning	Score
Specificity	It names the domain (Revel Systems) but the actions are generic verbs — "Manage data, records, and automate workflows" — rather than concrete operations like list orders or create payments, so it sits below the 1-2 concrete actions anchor.	2 / 5
Completeness	It states both what ("Revel Systems integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Revel Systems data"), but the what is vague enough that it does not reach the fully concrete trigger-phrase anchor.	4 / 5
Trigger Term Quality	It includes the natural term "Revel Systems" and "data"/"records", but misses common synonyms a user might say such as POS, point of sale, orders, or payments, leaving keyword coverage incomplete.	3 / 5
Distinctiveness Conflict Risk	The named "Revel Systems" trigger gives it a clear niche with low conflict risk, though the generic action phrasing leaves minor overlap with other data-management 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/revel-systems/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.