Name: harperdb
Rating: 60.8 (1 reviews)
Author: membranedev

harperdb

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

Quality

71%

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/harperdb/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 body is highly actionable with executable CLI commands and a solid connection-state feedback loop. Weaknesses are a padded marketing intro and the absence of validation checkpoints for destructive record operations (Update/Delete).

Suggestions

Add a verify-before-mutate checkpoint for destructive actions, e.g. 'Before Delete/Update, confirm the target hash with a SearchByHash read and show the record to the user'.

Trim the opening paragraph and conversational filler ('so you can focus on the integration logic rather than auth plumbing') to improve token efficiency.

Clarify the step numbering (the body references 'Step 2' which is never labeled) so the multi-step workflow is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-focused content, but the marketing-style intro ('distributed database platform designed for ease of use and scalability... used by developers and businesses') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding, matching the 3 anchor; not lean enough for 4.	3 / 5
Actionability	Copy-paste-ready, fully executable commands throughout (npm install, membrane login, connection ensure/get, action list/run, request) with concrete flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	A clear connection-readiness sequence with a polling feedback loop exists, but the core destructive operations (Delete, Update records) lack validation/verification checkpoints; per the destructive-operations cap this cannot exceed 3.	3 / 5
Progressive Disclosure	Well-organized single file with clear section headers covering distinct concerns; no external references are needed and content is appropriately placed, with only minor organization gaps (loose 'Step 2' references), matching the 4 anchor.	4 / 5
	Total	15 / 20 Passed

Description

73%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 concise, third-person, and includes an explicit 'Use when' trigger with a distinctive niche name. Its main weakness is generic action verbs ('manage') that limit specificity and the richness of trigger phrasing.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Query, insert, update, and delete records in HarperDB' to raise specificity.

Expand the when-clause with concrete trigger phrases such as 'Use when the user mentions HarperDB, wants to query or modify HarperDB tables/records, or automate HarperDB workflows'.

Dimension	Reasoning	Score
Specificity	Names the domain (HarperDB) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic ('manage') rather than concrete, matching the 1-2 concrete actions anchor; not comprehensive enough for a 4.	3 / 5
Completeness	Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with HarperDB data'); the when-clause is present and explicit but could be richer with concrete triggers, matching the 4 anchor.	4 / 5
Trigger Term Quality	Good coverage of natural niche terms ('HarperDB', 'data', 'records', 'interact with HarperDB data') that a user would say; a few synonyms/variations are absent, so it stops short of 5.	4 / 5
Distinctiveness Conflict Risk	The proper-noun niche 'HarperDB' gives it a clear, distinct trigger with minimal overlap risk against 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/harperdb/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.