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

Blog Docs Log in Get started

albato

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

Quality

Content

61%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 actionable and well-structured with executable CLI commands and a solid connection-state workflow. Its main gaps are unnecessary background/marketing prose and missing verification steps after destructive action/proxy operations.

Suggestions

Trim the background paragraph about what Albato is and who uses it, plus the "focus on integration logic rather than auth plumbing" phrasing, to improve token efficiency.

Add an explicit verification step after running actions and proxy requests (e.g. check the `output`/response status and confirm the expected change before proceeding).

Move the long entity list and proxy flag table into a reference file referenced one level deep to tighten the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary background ("Albato is a no-code platform... used by small to medium-sized businesses... lead generation, customer relationship management, and e-commerce operations") and marketing fluff ("so you can focus on the integration logic rather than auth plumbing").	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands throughout (install, login, connection ensure, action list/run, request) with placeholders like CONNECTION_ID and QUERY explained; minor gaps keep it below the fully-comprehensive 5.	4 / 5
Workflow Clarity	The connection setup has a clear state-feedback loop (poll READY/BUILDING/CLIENT_ACTION_REQUIRED and re-poll after the user acts), but destructive proxy (POST/PUT/PATCH/DELETE) and action-run operations have no validation/verification step, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested/deep references and no bundle files to mismanage; the long inline 30-entity list is a minor organization gap that keeps it from 5.	4 / 5
	Total	14 / 20 Passed

Description

70%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 states what the skill does and when to use it, anchored by a distinctive named platform. Its main weakness is generic action verbs and a vague when-clause that lacks concrete trigger phrases.

Suggestions

Replace generic verbs with concrete actions, e.g. "Create and run Albato automations, manage records and datastores, and connect cloud apps".

Expand the when-clause with explicit triggers, e.g. "Use when the user wants to automate workflows, manage Albato records, or integrate apps via Albato".

Add common synonyms/file-less trigger phrasing such as "Albato automation" or "connect Albato apps" to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Albato integration") plus a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, matching the 1-2-concrete-actions anchor rather than the comprehensive 5.	3 / 5
Completeness	Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Albato data"), but the when-clause is generic rather than listing concrete trigger phrases, fitting the 4 anchor.	4 / 5
Trigger Term Quality	Good keyword coverage with natural terms (Albato, integration, data, records, workflows, automate) a user would say; a few synonyms (e.g. "connect Albato apps", "Albato automation") are missing, so it sits above the 3 anchor but below 5.	4 / 5
Distinctiveness Conflict Risk	The named platform "Albato" gives a clear niche with minimal conflict risk, but secondary terms (data, records, workflows) are generic and could overlap with related integration skills, so it does not reach 5.	4 / 5
	Total	15 / 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/albato/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.