Name: datto-autotask
Rating: 56.8 (1 reviews)
Author: membranedev

datto-autotask

Datto Autotask integration. Manage data, records, and automate workflows. Use when the user wants to interact with Datto Autotask 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/datto-autotask/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 body is highly actionable with comprehensive executable CLI commands and a clear connection workflow, but lacks validation/verification feedback loops for destructive or batch operations and contains a few motivational sentences that could be trimmed. Organization is strong for a single-file skill.

Suggestions

Add explicit validation checkpoints before destructive or batch operations (e.g., verify a connection's READY state and confirm before running proxy DELETE/PATCH requests) to establish a validate->fix->retry loop.

Trim motivational padding such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" to improve conciseness.

Consolidate the thin "Popular actions" section with "Searching for actions" to reduce redundancy and tighten structure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and minimal background padding, but motivational lines like "so you can focus on the integration logic rather than auth plumbing" and a few restatements could be trimmed, matching anchor 3 rather than 4.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands across install, auth, connection, action list/run, and proxy with concrete flag examples and a flags table, covering the common cases comprehensively per anchor 5.	5 / 5
Workflow Clarity	The connection flow is a clear sequenced workflow with state-based branches (READY/BUILDING/CLIENT_ACTION_REQUIRED), but operations like proxy DELETE and action runs are destructive/batch with no validate->verify->retry feedback loop, so workflow clarity is capped at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized single-file structure with clear sections and no nested external references, but at ~167 lines (not under 50) with minor organization gaps (a thin "Popular actions" section overlapping "Searching for actions"), fitting anchor 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 clearly identifies the platform and includes both a capability summary and an explicit use-when trigger, but the listed actions are generic verbs and lack richer natural-language synonyms. Strengthening the trigger phrasing with concrete domain terms would raise it.

Suggestions

Replace generic verbs ("Manage", "automate workflows") with concrete platform operations like "create and update tickets, manage accounts and contacts, track time entries" to lift specificity.

Add natural trigger synonyms users would say, e.g. "Use when the user mentions Autotask tickets, accounts, projects, or PSA data" to improve trigger term quality.

Make the use-when clause more concrete by listing the specific objects (tickets, contacts, contracts) the skill operates on.

Dimension	Reasoning	Score
Specificity	Names the Datto Autotask domain with concrete actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than comprehensive specific operations, matching anchor 3 and not warranting 4.	3 / 5
Completeness	Provides a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Datto Autotask data"); the when-clause is present but not as specific as the anchor-5 example, so 4 rather than 5.	4 / 5
Trigger Term Quality	Contains relevant keywords ("Datto Autotask", "data", "records", "workflows") with an explicit trigger clause, but misses common variations/synonyms such as PSA, tickets, MSP, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named commercial platform with a platform-specific trigger, giving low conflict risk, but the generic manage/automate verbs leave minor overlap risk, fitting anchor 4.	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/datto-autotask/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.