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

reamaze

Reamaze integration. Manage data, records, and automate workflows. Use when the user wants to interact with Reamaze 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/reamaze/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.

The body is highly actionable with comprehensive, executable CLI commands and a clear connection workflow including error-recovery branching. Its main weaknesses are minor prose padding and inconsistent step numbering rather than structural problems.

Suggestions

Trim the intro paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" to tighten conciseness.

Fix step numbering so referenced steps ("Step 2", "1b") have matching labeled anchors, or relabel as a continuous numbered sequence.

Consider moving the proxy flags table and connection-state reference into a separate REFERENCE.md to improve progressive disclosure and reduce SKILL.md length.

Dimension	Reasoning	Score
Conciseness	The body is command-dense and mostly efficient, but the opening paragraph explaining what Reamaze is and prose like "so you can focus on the integration logic rather than auth plumbing" and "This will burn less tokens" are minor instances of over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands across install, login, connection ensure/get with polling, action list/run with JSON input, and proxy requests with a full flags table, covering the common cases fully and executably.	5 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear with a real state-based feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR polling), but step numbering is inconsistent ("skip to Step 2" with no labeled Step 2, a "1b" with no "1a") and output verification is implicit.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections with good navigation, but reference-style material (the proxy flags table, the connection-state breakdown) is inlined rather than split into a separate reference file, leaving minor organization gaps.	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.

The description covers the required what and when with a clear brand trigger, but its action language is generic and the trigger terms lack synonyms for the platform's entities. Strengthening it with concrete Reamaze capabilities and broader natural triggers would raise specificity and trigger quality.

Suggestions

Replace generic actions with concrete Reamaze capabilities, e.g. "Manage conversations, contacts, messages, articles, and workflows" to improve specificity.

Broaden the trigger clause to include natural synonyms, e.g. "Use when the user wants to work with Reamaze conversations, support tickets, contacts, or knowledge base articles."

Keep the concise third-person voice but ensure the when clause references the entity types users actually name rather than only "Reamaze data".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Reamaze domain plus three actions, but the actions are generic rather than concrete capabilities, matching the anchor that lists 1-2 generic actions without comprehensive coverage.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Reamaze data"), but the when clause is narrow and could be more specific about which Reamaze entities trigger the skill.	4 / 5
Trigger Term Quality	The "Reamaze" brand keyword and "interact with Reamaze data" provide some relevant natural terms, but common variations and synonyms a user might say (support, conversations, tickets, contacts) are missing, fitting the anchor with partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	"Reamaze integration" names a specific platform with a distinct brand trigger, but the generic "Manage data, records, automate workflows" phrasing leaves minor overlap risk with general data/CRM skills, placing it mostly-distinct rather than fully niche.	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/reamaze/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.