Name: charthop
Rating: 53.6 (1 reviews)
Author: membranedev

charthop

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

Quality

60%

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

Quality

Content

57%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 gives real executable commands, but it spends tokens explaining ChartHop itself and inlines reference-style content without progressive disclosure. Workflow sequencing also lacks the validation checkpoints expected for data-mutating operations.

Suggestions

Cut the introductory 'what is ChartHop' paragraph and the bare Overview entity list; assume Claude knows the product and lead with the integration workflow.

Add explicit validation/verification after data-mutating actions (e.g. re-fetch a record to confirm a write, or check action output for errors before proceeding) and label the referenced 'Step 2'.

Move the proxy flag reference table and the action-discovery catalog into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The opening paragraph and 'Overview' list re-explain what ChartHop is and enumerate entities without actionable value, which is padding Claude does not need; the rest is reasonably efficient.	3 / 5
Actionability	Concrete, copy-pasteable commands are provided throughout (login, connection ensure, action list/run, request) with a flag table, leaving only minor gaps such as unfilled CONNECTION_ID/QUERY placeholders.	4 / 5
Workflow Clarity	A connection lifecycle sequence with state handling and polling is present, but 'Step 2' is referenced without being labeled, and destructive/batch data operations lack any validation or verification checkpoint.	3 / 5
Progressive Disclosure	The single SKILL.md is sectioned with headers, but there are no bundle files and the proxy flag table plus popular-actions catalog are inlined reference material that is not split out or signaled.	3 / 5
	Total	13 / 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 third-person and correctly pairs a 'what' with an explicit 'Use when...' trigger, landing in the mid-range. It is held back by generic action verbs and thin trigger-term variety rather than any over-claiming.

Suggestions

Replace generic verbs with concrete operations, e.g. 'Manage data, records, and automate workflows' -> 'Query and update employee records, sync compensation data, and trigger workflow automations'.

Broaden trigger terms beyond the product name, e.g. 'Use when the user wants to interact with ChartHop data, manage org-chart or workforce data, or automate ChartHop workflows'.

Dimension	Reasoning	Score
Specificity	Names the ChartHop domain and lists a few actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete operations, so coverage is not comprehensive.	3 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with ChartHop data' clause, though the 'when' could name more specific trigger scenarios.	4 / 5
Trigger Term Quality	The phrase 'interact with ChartHop data' is a natural trigger, but only the bare product name is offered with no synonyms, feature names, or variations a user might actually say.	3 / 5
Distinctiveness Conflict Risk	The proper noun 'ChartHop' carves out a clear niche with minimal overlap risk; only the generic trailing phrasing keeps it from a 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/charthop/SKILL.md
Commit: f484c82

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