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

dimdata

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

Quality

68%

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

Quality

Content

75%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 tightly written, executable integration guide with clear state-driven workflows and feedback loops for the connection lifecycle. Its main weaknesses are minor: placeholder-laden commands, a dangling "Step 2" reference, and light conceptual padding.

Suggestions

Fix the dangling "skip to Step 2" / "Skip to Step 2" references by labeling the actual downstream step or rewording to a concrete section name.

Add one fully-resolved worked example (real connection id, a sample action run with concrete input) so a command can be copy-pasted verbatim.

Trim the DIMDATA marketing intro ("helps businesses organize, clean, and analyze... used by data analysts, scientists, and engineers") to a one-line purpose statement.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with only minor padding (the DIMDATA marketing intro and "so you can focus on the integration logic rather than auth plumbing"), fitting efficient with minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides concrete, runnable commands for install, login, connection, action search/run, and proxying with a flag table, but most commands require substituting placeholders (CONNECTION_ID, <actionId>, <code>), which is a minor gap from fully copy-paste ready.	4 / 5
Workflow Clarity	The connect-to-poll-to-act lifecycle is sequenced with explicit state checks and a feedback loop (poll again after the user completes the action), but the document references a "Step 2" that is never labeled as a step, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	Content is well organized under clear section headers in a single file with no bundle files to split, but the dangling "Step 2" reference and all-inline reference/action content keep it from the cleanest navigation, fitting good structure with minor organization gaps.	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 in third person with a clear platform-specific niche, but its action verbs are somewhat generic and it lacks trigger-term synonyms. It sits solidly above average without being exemplary.

Suggestions

Replace generic verbs like "Manage data" with more concrete actions (e.g., query records, update fields, list invoices) to lift specificity.

Add natural trigger synonyms users might say (records, invoices, DIMDATA API) rather than relying solely on "DIMDATA data".

Tighten the when-clause with concrete triggers, e.g. "Use when the user wants to query, create, or update DIMDATA records or automate DIMDATA workflows."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the DIMDATA domain plus 2-3 actions, but "manage data" is generic and the coverage is not comprehensive, fitting the anchor that names the domain and 1-2 concrete actions.	3 / 5
Completeness	It states a clear what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with DIMDATA data"), matching the anchor where both are present but the when could be more specific.	4 / 5
Trigger Term Quality	The trigger "interact with DIMDATA data" centers on a single keyword (DIMDATA) with no synonyms or common variations, matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a named platform (DIMDATA) gives it a clear niche with low conflict risk, though the trigger phrasing is broad enough to leave minor overlap with generic data skills, fitting mostly distinct with minor overlap.	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/dimdata/SKILL.md
Commit: f484c82

Reviewed: ~17 hours 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.