Name: hypeauditor
Rating: 55.2 (1 reviews)
Author: membranedev

hypeauditor

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

Quality

62%

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/hypeauditor/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, largely executable guide to the Membrane/HypeAuditor workflow with strong connection-state feedback loops, held back by scattered verbosity, a duplicated command section, and broken step numbering.

Suggestions

Trim filler ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and merge the redundant 'Popular actions' section into 'Searching for actions'.

Fix the step numbering: label the missing '1a'/'Step 2' anchors or replace 'skip to Step 2' with a concrete section name like 'Searching for actions'.

Add at least one concrete, fully-substituted action-run example (e.g. a real HypeAuditor action id with sample --input) so the running-actions guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but includes padded phrases ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection'), a product-intro paragraph, and a 'Popular actions' section that repeats the already-shown action-list command, fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened.'	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxy requests plus a complete flag table, but uses generic placeholders like <actionId> and CONNECTION_ID without a concrete real-action example, matching 'Mostly executable guidance; concrete code or commands with minor gaps.'	4 / 5
Workflow Clarity	The Install→Auth→Connect→Poll→Search→Run sequence includes explicit state feedback loops (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but step numbering is broken — it references an unlabeled 'Step 2' and a '1b' with no '1a' — fitting 'Clear sequence with most checkpoints present; minor validation gaps.'	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in one well-organized SKILL.md with clear section headers and a category overview; structure and navigation are good, with minor gaps such as the full proxy flag table and schema details kept inline, matching 'Good structure; most content is appropriately placed; minor organization gaps.'	4 / 5
	Total	15 / 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 establishes a clear niche via the HypeAuditor brand and provides an explicit 'Use when' trigger, but its capability wording ('Manage data, records, and automate workflows') is generic and lacks concrete actions or richer trigger synonyms.

Suggestions

Replace generic actions with concrete operations, e.g. 'Pull influencer reports, query account and brand metrics, and automate HypeAuditor workflows.'

Add natural trigger synonyms users would actually say, such as 'influencer', 'influencer marketing', 'analytics', or 'HypeAuditor reports'.

Sharpen the 'when' clause to reference specific intents like 'when the user wants influencer analytics or HypeAuditor report data'.

Dimension	Reasoning	Score
Specificity	It names the domain (HypeAuditor) but the actions 'Manage data, records, and automate workflows' are generic abstractions rather than concrete operations, matching the anchor 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	Both a 'what' (HypeAuditor integration, manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with HypeAuditor data') are present, so it is not capped at 3; the 'when' is explicit but could be more specific.	4 / 5
Trigger Term Quality	It includes the core keyword 'HypeAuditor' plus 'data, records, workflows' but misses natural synonyms a user might say (influencer, analytics, influencer marketing), fitting 'Some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the specific brand 'HypeAuditor' gives it a distinct niche with minimal conflict risk, though the generic action phrasing and possible sibling Membrane skills leave minor overlap, matching 'Mostly distinct; minor overlap risk.'	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/hypeauditor/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.