Name: dolthub
Rating: 56.8 (1 reviews)
Author: membranedev

dolthub

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/dolthub/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 content is highly actionable with copy-paste CLI commands and a clear connection workflow, but it loses points for some redundant conceptual explanation and a missing validation checkpoint on database action execution.

Suggestions

Trim the conceptual intro and 'DoltHub Overview' glossary that restate what Claude already knows about DoltHub to improve token efficiency.

Add an explicit validation/verification step (e.g., checking action output or a dry-run/--dryRun before destructive SQL actions) to the 'Running actions' workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, but the 'DoltHub Overview' bullet glossary and the opening 'DoltHub is a data version control system...' sentence re-explain concepts Claude already knows.	3 / 5
Actionability	Commands are fully executable and copy-paste ready throughout (install, login, connection ensure, action run with --input JSON, proxy with a flag table), with parameterized placeholders rather than pseudocode.	5 / 5
Workflow Clarity	The connect-to-ready flow has explicit polling and state checkpoints, but the destructive/batch database 'action run' step has no validation or verification checkpoint, capping this dimension per the database-operations feedback-loop rule.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references, though ~141 lines of inlined proxy flags and clientAction detail could be split into separate reference files.	4 / 5
	Total	15 / 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 covers both what the skill does and when to use it with an explicit trigger clause, landing above average. It is held back by somewhat abstract action verbs ('manage') and limited natural-language keyword coverage.

Suggestions

Replace generic verbs ('Manage data, records') with concrete DoltHub-specific actions such as 'query, branch, and commit SQL data' to raise specificity.

Expand the 'Use when' clause with natural user phrasings like 'DoltHub databases, SQL data versioning, or dolthub.com repos' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the DoltHub domain and lists 2-3 actions ('Manage data, records, and automate workflows'), but 'manage data' and 'records' are generic rather than concretely specified actions.	3 / 5
Completeness	Both a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' clause are present, though the 'when' trigger is somewhat generic.	4 / 5
Trigger Term Quality	Includes relevant keywords ('DoltHub', 'data', 'records', 'workflows') but misses common natural synonyms or file/extension variations a user would say.	3 / 5
Distinctiveness Conflict Risk	'DoltHub integration' is a clear niche with a distinct trigger, though the broad 'manage data, records, workflows' phrasing carries minor overlap risk with general data skills.	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/dolthub/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.