Name: hyperise
Rating: 64 (1 reviews)
Author: membranedev

hyperise

Hyperise integration. Manage Organizations, Leads, Projects, Users, Goals, Filters. Use when the user wants to interact with Hyperise data.

Quality

76%

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/hyperise/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 a well-structured, highly actionable CLI integration guide with executable commands and a strong connection-state feedback loop. Its main weaknesses are minor marketing prose that could be trimmed and the lack of verification guidance before destructive actions.

Suggestions

Add a brief verification checkpoint before destructive actions (e.g. for delete-business, confirm the business ID via get-business first) to close the workflow_clarity gap.

Trim the marketing-flavored explanations ('so you can focus on the integration logic', 'burn less tokens') to keep the body lean.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and structured state handling with only minor marketing-flavored prose ("so you can focus on the integration logic rather than auth plumbing", "burn less tokens"), fitting the 'efficient; minor instances of over-explanation' anchor rather than the noticeably-verbose anchor-2 or the fully-lean anchor-5.	4 / 5
Actionability	It provides copy-paste-ready commands across the full lifecycle (install, login, connection ensure, action list, action run, request) with flag tables and a popular-actions table, covering the common cases the anchor-5 example rewards.	5 / 5
Workflow Clarity	The connection-readiness flow is a clear sequence with an explicit feedback loop (poll --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after the user acts); the one gap is the absence of any validation/verification before destructive actions such as delete-business, which keeps it just below anchor 5.	4 / 5
Progressive Disclosure	No bundle files exist and the SKILL.md is a single, well-sectioned file (Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no broken or deeply nested references; the inline popular-actions and proxy-flag tables could be externalized but are reasonably placed, matching anchor 4 rather than the one-level-deep-reference anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

71%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 cleanly names the product and the six resource types it manages and includes an explicit 'Use when' trigger, but the trigger phrasing is generic and could name concrete user intents. It is distinct and low-conflict but not maximally specific on actions.

Suggestions

Replace the generic 'Use when the user wants to interact with Hyperise data' with concrete trigger phrases a user would say, e.g. 'Use when the user asks to manage Hyperise leads, organizations, projects, or goals.'

Pair each managed resource with a concrete verb (create, list, update, delete) rather than the single generic 'Manage' so the capabilities read as distinct actions.

Dimension	Reasoning	Score
Specificity	Lists several concrete managed resources ("Organizations, Leads, Projects, Users, Goals, Filters") under a single "Manage" verb; covers the domain comprehensively but does not enumerate distinct per-resource actions, so it sits below the anchor-5 example rather than at it.	4 / 5
Completeness	It states a clear "what" ("Hyperise integration. Manage Organizations, Leads, Projects...") and an explicit "when" clause ("Use when the user wants to interact with Hyperise data"), but the trigger is generic rather than concrete phrases, matching the anchor-4 example.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Hyperise data" surfaces the brand plus the resource names as keywords, but the phrase is generic and lacks the natural variations a user would actually say (e.g. "my Hyperise leads", "Hyperise campaigns").	3 / 5
Distinctiveness Conflict Risk	"Hyperise integration" names a distinct third-party product with brand-specific triggers, giving it a clear niche and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/hyperise/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.