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

hyscoreio

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/hyscoreio/SKILL.md

Quality

Content

68%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 executable CLI commands throughout and is well-organized into clear sections. Its main weaknesses are some over-explanation of auth concepts Claude already knows and the absence of validation checkpoints or feedback loops for destructive/batch actions (action runs, proxy writes), which caps workflow clarity.

Suggestions

Add explicit validation/verification after destructive or batch operations — e.g. after a proxy POST/DELETE or action run, verify the result before declaring success, and on CONFIGURATION_ERROR show how to read the error and retry.

Trim redundant or obvious prose such as 'so you can focus on the integration logic rather than auth plumbing' and the near-duplicate discovery guidance in both 'Searching for actions' and 'Best practices'.

Tighten the connection state handling into a compact checklist (READY → Step 2; BUILDING → poll; CLIENT_ACTION_REQUIRED → show uiUrl, poll; CONFIGURATION_ERROR/SETUP_FAILED → read error) so the feedback loop is explicit.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable CLI commands, but it includes unnecessary explanation Claude already knows ('Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing') and a redundant restatement of 'Discover before you build' guidance, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the level-4 'efficient; minor instances of over-explanation.'	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection ensure, polling, action search/run, and proxy requests, plus a concrete options table — covering the common cases with specific flags and JSON examples, matching the level-5 anchor exactly.	5 / 5
Workflow Clarity	The connection flow has a rough sequence (ensure → poll BUILDING → handle READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive/batch operations like 'membrane action run' and proxy POST/DELETE requests lack explicit validation checkpoints or feedback loops to verify results before proceeding, hitting the rubric cap that 'missing validation/verification steps in workflows involving destructive or batch operations should cap workflow clarity at 3.'	3 / 5
Progressive Disclosure	The body is well-sectioned (Overview, Working with, Install, Auth, Connecting, Searching, Popular actions, Best practices) at roughly the right overview length with no bundle files present to externalize, matching 'good structure; most content appropriately placed; minor organization gaps' rather than level-5 which expects clearly signaled one-level-deep external references that this skill doesn't use.	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 has a clear third-person voice and includes both a 'what' and a 'Use when' trigger, satisfying the basic completeness bar. Its weaknesses are generic action verbs ('data', 'records') that don't reflect the platform's real entities and a single, non-varied trigger phrase rather than concrete natural-language triggers.

Suggestions

Replace the generic actions with the platform's real entities, e.g. 'Manage scorecards, key results, users, organizations, and comments' instead of 'Manage data, records, and automate workflows.'

Expand the trigger clause with concrete natural phrases a user would say, e.g. 'Use when the user wants to query or update Hyscore.io scorecards, key results, or user engagement data.'

Add natural synonyms/variations (e.g. 'user engagement analytics', 'key-result tracking') so the skill surfaces for the varied ways users phrase the intent.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the domain and a few concrete-sounding actions, but 'data' and 'records' are generic abstractions rather than the platform's real entities (Scorecard, Key Result, User), so coverage is comprehensive in count but not in concrete specificity — matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor better than the level-4 'several specific actions with minor gaps' anchor.	3 / 5
Completeness	'Hyscore.io integration. Manage data, records, and automate workflows' answers what, and 'Use when the user wants to interact with Hyscore.io data' answers when, but the 'when' clause is a single generic trigger rather than concrete trigger phrases, matching the level-4 'has both what and when; when could be more explicit or specific' rather than the level-5 anchor requiring concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural trigger phrase is 'interact with Hyscore.io data'; the repeated proper noun 'Hyscore.io' is technical jargon rather than the varied natural synonyms a user would say, fitting 'some relevant keywords but missing common variations or synonyms' and falling short of the level-4 'good keyword coverage' anchor which expects multiple natural terms.	3 / 5
Distinctiveness Conflict Risk	The proper-noun scope ('Hyscore.io') gives it a clear niche with minimal conflict risk, but the generic actions ('Manage data, records, and automate workflows') could overlap with other data-management skills, matching 'mostly distinct; minor overlap risk with closely related skills' rather than the level-5 'clear niche with distinct triggers.'	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/hyscoreio/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.