Name: simplehash
Rating: 59.2 (1 reviews)
Author: membranedev

simplehash

SimpleHash integration. Manage Deals, Persons, Organizations, Leads, Projects, Activities and more. Use when the user wants to interact with SimpleHash data.

Quality

69%

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

Quality

Content

76%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, copy-paste-ready CLI documentation with a mostly clear workflow and good section structure. Its main weaknesses are a dangling "Step 2" reference and the absence of validation/verification for the action-run and proxy (destructive HTTP) operations.

Suggestions

Add an explicit validation step after running actions and proxy requests (e.g., check the response for an error/status field before treating the output as success), since proxy supports destructive DELETE/PUT with no verification guidance.

Fix the broken step navigation: either label the sections "Step 1 / Step 2" or change "skip to Step 2" to a concrete section anchor like "skip to Searching for actions".

Either populate "Popular actions" with actual example actions or remove the section, since it currently duplicates the "Searching for actions" guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean concrete CLI documentation; above a 3 because the bulk is efficient executable guidance, but below a 5 because of minor trim opportunities — the opening NFT-platform explainer is mild over-explanation and the "Popular actions" section merely restates the discovery command already given under "Searching for actions".	4 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, login, connection ensure/get, action list/run, proxy) plus a complete proxy options table, with the common cases explicitly covered.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists and the connection-readiness block has a real poll/client-action feedback loop, but the "skip to Step 2" reference dangles (no Step 1/2 labels) and the action-run and proxy steps (proxy supports destructive DELETE/PUT) have no output validation or verification checkpoint, capping this at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections and is appropriately self-contained with no bundle files to reference, but the bare entity-list overview, the redundant "Popular actions" section, and the broken "Step 2" navigation reference are minor organization gaps that keep it below a 5.	4 / 5
	Total	16 / 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 answers both what and when and targets a distinct app niche, but its action verb is generic ("Manage ... and more") and its trigger phrasing is circular rather than rich with natural keywords. It is solid but leaves room for more concrete actions and natural trigger terms.

Suggestions

Replace the generic "Manage ... and more" with 2-3 concrete actions (e.g., "Look up NFT collection/wallet risk scores, fetch asset metadata, trace attribution").

Expand the when-clause with concrete natural triggers users would actually say (e.g., "Use when the user asks about NFT risk/safety scores, collection or wallet safety, or fraud signals for an NFT").

Reconcile the entity list with the tool's real domain — the description names Deals/Persons/Organizations/Leads/Projects/Activities while the body describes Collections, Assets, Wallets, Attribution, Transactions, and Users, which makes the trigger terms misleading.

Dimension	Reasoning	Score
Specificity	It names the SimpleHash domain and lists six concrete resource types ("Deals, Persons, Organizations, Leads, Projects, Activities"), but the only action verb is the generic "Manage ... and more", with no specific concrete actions, so it sits at the domain+entities-but-generic-action band rather than listing several specific actions.	3 / 5
Completeness	It states a clear "what" ("Manage Deals, Persons, Organizations, Leads, Projects, Activities") and an explicit "Use when the user wants to interact with SimpleHash data" trigger, but the when-clause is generic and somewhat circular rather than concrete trigger phrases, so it falls short of a 5.	4 / 5
Trigger Term Quality	Relevant keywords are present (the entity names plus "SimpleHash"), but there are no common synonyms, file extensions, or varied natural phrasings a user might say, leaving keyword coverage partial rather than good.	3 / 5
Distinctiveness Conflict Risk	"SimpleHash integration" plus a SimpleHash-scoped trigger carves out a clear niche with only minor overlap risk against other app-integration skills, though the somewhat circular when-clause keeps it from minimal-conflict territory.	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/simplehash/SKILL.md
Commit: f484c82

Reviewed: 4 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.