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

hiphops

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

Quality

63%

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/hiphops/SKILL.md

Quality

Content

63%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 actionable and reasonably well-sequenced with genuine validation via connection-state polling, but its quality is dragged down by an embedded leaked-LLM refusal line, marketing padding, duplicated sections, and inline reference material that belongs in separate files. It is a competent integration guide that needs a cleanup pass.

Suggestions

Delete the leaked model-refusal line at the top of the body ('I don't have enough information to do that...'); it is irrelevant noise that wastes tokens.

Fix the workflow numbering — relabel '1b' and add the missing 'Step 2' header so cross-references like 'skip to Step 2' resolve.

Move the proxy flag reference table and action inputSchema/outputSchema details into a references/ file and link to it, and merge the duplicated 'Searching for actions' and 'Popular actions' sections.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient command-based guidance, but it carries irrelevant noise — the leaked LLM refusal line 'I don't have enough information to do that...' — plus marketing padding like 'so you can focus on the integration logic rather than auth plumbing', fitting the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxy with a flag table, but placeholders (CONNECTION_ID, <actionId>) and an unexplained entity-name bulleted list leave minor gaps versus the fully-covered 5 anchor.	4 / 5
Workflow Clarity	The install → auth → connect → search → run/proxy sequence is clear with a real validation checkpoint via connection-state polling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but inconsistent numbering ('1b', a referenced 'Step 2' with no matching header) keeps it just below the explicit-checklist 5 anchor.	4 / 5
Progressive Disclosure	The body is a single ~140-line file with reasonable headers but no bundle files; reference-style material (the proxy flag table, action schema fields) is inlined and the 'Searching for actions' and 'Popular actions' sections duplicate each other, matching the 'some structure, could be better organized' anchor.	3 / 5
	Total	14 / 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 is well-formed: third-person voice, a clear niche tied to the Hiphops app, and an explicit 'Use when' trigger. Its main weakness is generic action language ('Manage data, records, automate workflows') and limited trigger-term variation, which keep specificity and trigger quality at mid-range.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Search, run, and proxy Hiphops API actions via Membrane' to lift specificity.

Expand the trigger with natural phrasings users would say, e.g. 'Use when the user wants to query Hiphops datasets, run model actions, or call the Hiphops API'.

Mirror the body's actual capabilities (connection setup, action discovery, proxy requests) so the 'what' matches what the skill does.

Dimension	Reasoning	Score
Specificity	Names the domain (Hiphops) plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the '1-2 concrete actions, not comprehensive' anchor rather than the specific-actions anchor at 4.	3 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' with an explicit 'Use when the user wants to interact with Hiphops data' clause, but the 'what' is vague and the 'when' is general rather than listing concrete trigger phrases, so it falls short of the 5 anchor.	4 / 5
Trigger Term Quality	The natural keyword is essentially the app name ('Hiphops', 'Hiphops data'); relevant but lacking common variations or synonyms, fitting the 'some relevant keywords but missing variations' anchor rather than the good-coverage anchor at 4.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to a specific named app ('Hiphops integration', 'interact with Hiphops data') gives a clear niche with minimal conflict risk, but the broad 'interact with data' phrasing leaves minor overlap risk versus a fully distinct trigger, so it sits at 4 rather than 5.	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/hiphops/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.