Name: hyros
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

hyros

Hyros integration. Manage Organizations. Use when the user wants to interact with Hyros data.

Quality

70%

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/hyros/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 copy-paste commands and a sensible connection workflow including polling and error-state feedback. The main gaps are an undefined "Step 2" reference and a slightly long single-file layout.

Suggestions

Define or relabel "Step 2": the body says "skip to Step 2" but no Step 2 header exists — either add a numbered "Step 2: Search and run actions" heading or change the wording to point at the actual section.

Consider moving the 15-row Popular actions table and the proxy options table into a references/ file (e.g., ACTIONS.md) referenced from the body, to tighten the main file and improve progressive disclosure.

Trim the Hyros marketing-analytics intro paragraph and the "focus on integration logic" aside to reduce token cost without losing actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and tables, with only minor over-explanation (the Hyros marketing-analytics intro and the "focus on integration logic rather than auth plumbing" aside) that could be trimmed, fitting anchor 4.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) with flags and a concrete popular-actions table covering common cases, matching anchor 5.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints and feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED, error states), but "skip to Step 2" references an undefined step, leaving a minor validation/labeling gap at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no external references needed (no bundle files exist), but at ~160 lines in a single file it is slightly long for a monolithic layout, placing it at anchor 4 rather than the well-split anchor 5.	4 / 5
	Total	17 / 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 includes a Use-when trigger and anchors on a distinct product name, but its capability statement is thin and generic. Expanding the concrete actions and trigger specificity would raise completeness and specificity.

Suggestions

Replace the generic "Manage Organizations" with 2-3 concrete actions the skill actually supports (e.g., refund sales, retrieve lead journeys, pull attribution data) to improve specificity and accuracy.

Broaden the trigger clause beyond "interact with Hyros data" to name concrete scenarios (e.g., "Use when the user wants to refund a Hyros sale, look up a lead's attribution journey, or analyze ad ROI").

Drop the inaccurate "Manage Organizations" framing since it does not match the skill's real analytics/attribution focus, reducing overlap risk with unrelated org-management skills.

Dimension	Reasoning	Score
Specificity	The description names the domain (Hyros) but offers only one minimal, generic action ("Manage Organizations"), which does not reflect the actual breadth of capabilities shown in the body (refunds, leads, calls, attribution). It sits closer to anchor 2 ("names the domain but actions are minimal or generic") than anchor 3, which expects 1-2 concrete actions.	2 / 5
Completeness	Both a "what" ("Hyros integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Hyros data.") are present, but the trigger clause is generic rather than concrete, fitting anchor 4 rather than 5.	4 / 5
Trigger Term Quality	"Hyros" is a relevant natural keyword a user would say, and "interact with Hyros data" echoes it, but there is only a single term with no synonyms or variations, matching anchor 3 ("some relevant keywords but missing common variations or synonyms").	3 / 5
Distinctiveness Conflict Risk	The proper noun "Hyros" gives a clear niche with minimal conflict risk, but the generic "Manage Organizations" action creates minor overlap with general org-management skills, placing it at anchor 4 rather than 5.	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/hyros/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.