Name: dashbotio
Rating: 60 (1 reviews)
Author: membranedev

dashbotio

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

Quality

70%

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/dashbotio/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 solid, command-driven integration guide with a clear workflow and explicit state-validation checkpoints. It loses points mainly to padding (intro/Overview/filler) and a lack of concrete Dashbot.io-specific action examples.

Suggestions

Trim the marketing-style intro paragraph and the "Use action names and parameters as needed." filler; let the Overview list either carry substance or be removed.

Consolidate the duplicated action-discovery command (it appears in both "Searching for actions" and "Popular actions") into one place.

Fix the dangling "skip to Step 2" and "1b" references by adding matching labeled step headers, or replace them with concrete section links.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands, but it carries several padded spots — a marketing-style intro ("helps developers and product managers understand user behavior..."), the filler line "Use action names and parameters as needed.", a sparse Overview list, and a duplicated action-list command between "Searching for actions" and "Popular actions".	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (install, login, connection ensure/get, action run, request) plus a flags table, but the running-actions examples use generic placeholders (<actionId>, {"key": "value"}) with no real Dashbot.io action example, leaving a minor gap.	4 / 5
Workflow Clarity	There is a clear sequenced setup (install → authenticate → connect → search → run) with state-polling checkpoints and error feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the text references a "Step 2" and "1b" that have no matching labeled headers, a minor structural gap.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested or buried references (and no bundle files exist to reference), but everything is inlined into a single ~140-line file where some material (the proxy flags table, clientAction details) could plausibly live in a separate reference.	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 clearly answers what the skill does and when to use it, anchored to a distinct product name that doubles as a natural trigger. Its main weakness is generic action phrasing ("Manage data, records, and automate workflows") rather than concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain (Dashbot.io) and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, so it sits at the anchor for domain + 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Both a "what" ("Dashbot.io integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Dashbot.io data.") are present, but the "what" is generic enough that it falls short of the concrete-trigger anchor at 5.	4 / 5
Trigger Term Quality	"Dashbot.io" is repeated as the natural trigger a user would actually say, and "interact with Dashbot.io data" gives good keyword coverage, though a few natural variations (analytics, chatbot) are missing.	4 / 5
Distinctiveness Conflict Risk	The skill is tied to a specific named product (Dashbot.io) with distinct brand triggers, giving it a clear niche with minimal conflict 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/dashbotio/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.