Name: raet
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

raet

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

Quality

64%

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

Quality

Content

67%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-sequenced, largely executable integration guide with sensible state-handling checkpoints. Its main weaknesses are a stray junk line, a vague overview section, and a redundant 'Popular actions' block that adds length without new guidance.

Suggestions

Remove the stray line 'I don't have enough information about Raet to do that. I'm sorry.' and the empty 'Raet Overview' bullet list, or replace them with concrete entity/action examples.

Make 'Popular actions' actually enumerate 2-3 representative actionIds with example parameters and outputs, or drop the section if it only restates the list command.

Call out an explicit validation step after running actions (e.g. check the `output`/`error` fields before proceeding) to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with little padding, but it carries unnecessary noise such as the stray line 'I don't have enough information about Raet to do that. I'm sorry.' and a vague 'Raet Overview' bullet list with 'Use action names and parameters as needed', placing it at 'mostly efficient but includes some unnecessary content that could be tightened'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, auth, connection, action search/run, and proxy with a flags table, but 'Popular actions' only repeats the list command without showing a real actionId and parameters, leaving a minor gap versus fully-covered common cases.	4 / 5
Workflow Clarity	The install → login → connection ensure → poll-state → search → run sequence is clear and branches on connection state (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with a polling feedback loop, though some validation guidance for action outputs is implicit rather than called out.	4 / 5
Progressive Disclosure	The content is organized into clear headed sections with no nested or broken references and no bundle files to defer to, but inlined reference-like blocks (the proxy flags table, verbose connection-state detail) and the redundant 'Popular actions' section leave minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

61%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 and a when and is clearly scoped to Raet, but its capability verbs are generic ('manage data', 'manage records') and its keyword coverage beyond the product name is thin. Tightening the actions into concrete operations would lift specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete Raet operations (e.g. 'list meetings, fetch participants, query accounts and workspaces') so the 'what' reads as specific actions.

Broaden trigger keywords with natural synonyms and entity names users would actually say (e.g. 'Raet meetings, participants, accounts, workspaces, Raet API').

Make the 'Use when' clause enumerate the concrete Raet tasks (meetings, records, automation) rather than only 'interact with Raet data'.

Dimension	Reasoning	Score
Specificity	Names the Raet domain plus a few actions, but 'Manage data, records, and automate workflows' uses near-synonymous generic verbs rather than concrete operations, so it is noticeably below the midpoint toward the 'names domain but actions minimal/generic' anchor.	2 / 5
Completeness	It states both the 'what' ('Raet integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Raet data'), but the 'what' is generic and the 'when' is narrow, fitting 'has both but could be more explicit or specific' rather than the fully concrete anchor 5.	4 / 5
Trigger Term Quality	'Raet', 'data', 'records', and 'Use when the user wants to interact with Raet data' surface some relevant keywords, but coverage is thin on natural synonyms or variations beyond the product name, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tied explicitly to the specific Raet product with a dedicated trigger ('interact with Raet data'), giving it a clear niche with minimal overlap risk, matching the top anchor.	5 / 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/raet/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.