Name: unifiedto
Rating: 61.6 (1 reviews)
Author: membranedev

unifiedto

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

Quality

72%

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

Quality

Content

82%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, highly actionable CLI guide with executable commands and a real error-recovery workflow for connection states. Its main weaknesses are minor prose padding and inconsistent step numbering that lightly undercuts the workflow sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — dominated by executable commands and a flag table — with only minor padding such as 'Developers use it to simplify integrations...' and the vague 'Use action names and parameters as needed.' line, matching 'efficient; minor instances of over-explanation that could be trimmed' rather than a 5.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get with --wait, action list/run with JSON input, and a full proxy flag table, covering the common cases fully, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connect flow is sequenced with state-based feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, poll until ready), but step numbering is inconsistent ('skip to Step 2' has no matching numbered header), fitting 'clear sequence with most checkpoints; minor validation gaps' rather than a 5.	4 / 5
Progressive Disclosure	No bundle files exist and the single-file guide is well-organized with clear section headers, but at ~140 lines some content (agent types, the proxy flag table) could arguably be split out, matching 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	17 / 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, names a clear product niche, and includes an explicit 'Use when' clause, but its action list is generic and its trigger terms lack synonyms or variations. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Search and run Unified.to actions, proxy raw API requests, and manage connections' instead of 'Manage data, records, and automate workflows'.

Expand trigger terms with natural variations users would say, such as 'Unified.to API', 'unified.to integrations', or 'connect to SaaS apps via Unified.to'.

Make the 'when' clause more concrete by listing the situations that trigger the skill, e.g. 'Use when the user wants to query, mutate, or automate Unified.to records and integrations'.

Dimension	Reasoning	Score
Specificity	It names the domain (Unified.to) and lists actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor; not a 4 because no specific operations are enumerated.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Unified.to data'), matching the 'has both what and when; when could be more explicit or specific' anchor rather than a 5 because the trigger phrases are not concrete.	4 / 5
Trigger Term Quality	It surfaces 'Unified.to data', 'records', and 'workflows' as triggers, but misses common variations, synonyms, or file/extension terms a user would naturally say, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Unified.to gives it a clear niche with minimal conflict risk, but the generic action verbs ('manage data, records') leave minor overlap with general data skills, so it sits between 'mostly distinct' and 'clear niche'.	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/unifiedto/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.