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

datawrapper

Datawrapper integration. Manage data, records, and automate workflows. Use when the user wants to interact with Datawrapper 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/datawrapper/SKILL.md

Quality

Content

67%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 a well-structured, actionable guide with executable commands, a flags table, and explicit connection-state checkpoints. Its main weakness is mild verbosity from background explanation and minor gaps in placeholders and file-splitting.

Suggestions

Trim background prose ('Datawrapper is an online platform...') and motivational phrases that Claude can infer, to improve token efficiency.

Make placeholder substitution explicit (e.g. show how to capture a CONNECTION_ID from the ensure step and reuse it in subsequent commands).

Consider splitting the proxy-request reference into a separate ADVANCED.md or REFERENCE.md and linking to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The bulk is lean executable commands, but background prose like 'Datawrapper is an online platform... used by journalists' and 'so you can focus on the integration logic rather than auth plumbing' explains concepts Claude already knows, fitting 'mostly efficient but includes some unnecessary explanation'; it does not reach the trim level of score 4.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list, action run) plus a full proxy flags table, covering common cases copy-paste ready; minor gaps like unresolved CONNECTION_ID placeholders keep it just below 5.	4 / 5
Workflow Clarity	The install → auth → connect → search → run sequence is clear, and connection-state polling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) includes explicit checkpoints and a poll-again feedback loop; it falls short of 5 only because some retry/error-recovery detail is implicit.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear sections (Overview, Working with Datawrapper, Popular actions, Best practices) with good navigation; minor organization gaps (e.g. the proxy reference could be a separate advanced file) keep it at 4 rather than 5.	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 cleanly identifies a distinct niche (Datawrapper) and includes an explicit 'Use when' clause, but its action verbs are generic and its trigger phrases lack concrete synonyms or file extensions. It is solid but not comprehensive.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Datawrapper actions such as creating/editing charts, uploading data, and managing folders or teams.

Expand the 'Use when' clause with concrete trigger phrases and synonyms users would actually say, e.g. 'Use when creating Datawrapper charts, uploading datasets, or managing chart folders and teams.'

Add Datawrapper-specific trigger terms (charts, maps, visualization) and the datawrapper.de / .csv references to reduce generic overlap with other data skills.

Dimension	Reasoning	Score
Specificity	It names the Datawrapper domain and a few actions ('Manage data, records, and automate workflows'), but those verbs are generic rather than concrete operations, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor and falling short of score 4's specific action list.	3 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' via an explicit 'Use when the user wants to interact with Datawrapper data' clause, but the trigger is generic rather than concrete phrases, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	'Datawrapper' and 'data' are relevant natural keywords, but common variations or synonyms a user might say are absent, matching 'some relevant keywords but missing common variations'; it does not reach the broad coverage of score 4.	3 / 5
Distinctiveness Conflict Risk	The named app 'Datawrapper' gives a clear niche with distinct triggers and low conflict risk, though the generic 'manage data/records' verbs leave minor overlap risk, keeping it just below the 5 anchor.	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/datawrapper/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.