Name: rydoo
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

rydoo

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

Quality

65%

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/rydoo/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-structured, actionable guide to the Membrane CLI workflow for Rydoo, with clear sequencing and feedback loops for connection setup. Its main weaknesses are minor redundancy between action-list sections, a couple of padded sentences, and unresolved placeholders with no end-to-end worked example.

Suggestions

De-duplicate the action-list command: keep it in one section and have 'Popular actions' reference it rather than repeating the full command.

Tighten or remove padded lines such as the 'Agent Types' trailing sentence about adjusting tooling for the harness.

Add one fully resolved end-to-end example (real connection id, a concrete action, and a sample proxy request) so the placeholders are demonstrated with real values.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with useful operational detail, but it repeats the action-list command between 'Searching for actions' and 'Popular actions' and includes padded lines ('Those will be used to adjust tooling to be used best with your harness'), matching 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the trim 4.	3 / 5
Actionability	It provides concrete, executable CLI commands (login, connection ensure, action list/run, request) plus a flags table, but leaves placeholders unresolved (<agentType>, CONNECTION_ID, /path/to/endpoint) with no fully worked example, fitting 'mostly executable guidance; minor gaps' below copy-paste-ready 5.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit polling checkpoints and state-branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) plus a 'poll again after the user completes the action' feedback loop, but lacks a final verify step for actions run via proxy, matching 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist and the body is well-organized into Overview, Working with Rydoo, Connecting, Searching, Popular actions, Proxy, and Best practices sections with no nested references, fitting 'good structure; most content appropriately placed; minor organization gaps' rather than the optimally-split 5.	4 / 5
	Total	15 / 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 correctly pairs a what and a when clause and leans on a distinct named app, but its actions and triggers are generic ('manage data', 'interact with Rydoo data') rather than concrete Rydoo-specific capabilities. Tightening the wording to name expense/report/travel actions and trigger phrases would lift the middling dimensions.

Suggestions

Replace generic verbs with concrete Rydoo capabilities, e.g. 'Manage expenses, reports, mileage, and reimbursements' instead of 'Manage data, records, and automate workflows'.

Expand the trigger clause with natural user phrases, e.g. 'Use when the user wants to submit or review expenses, manage travel, or interact with Rydoo data'.

Mention key Rydoo entities (reports, reimbursements, mileage, policies) to sharpen distinctiveness and reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	Names the Rydoo domain plus a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic abstractions rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor and falling below the multi-action specificity of a 4.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and 'when' (use when the user wants to interact with Rydoo data) are present and explicit, but the trigger clause is generic rather than specific, fitting 'has both what and when; when could be more explicit' rather than the fully concrete 5.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Rydoo data' surfaces relevant keywords but lacks common synonyms or variations (e.g. expenses, reports, travel), matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Rydoo is a named app giving a clear niche and low conflict risk, but the limited, generic trigger terms ('interact with Rydoo data') leave minor overlap risk versus a broader data-management skill, matching 'mostly distinct; minor overlap risk'.	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/rydoo/SKILL.md
Commit: f484c82

Reviewed: 4 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.