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

ataccama

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

Quality

Content

78%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 content is action-packed and executable with a clear connection workflow, but it is a monolithic single-file document with no progressive disclosure into supporting files and minor validation gaps. Splitting detailed material into references and adding explicit action-result validation would raise the weaker dimensions.

Suggestions

Move the proxy flag table and full action catalogue into a separate reference file (e.g. references/ataccama-actions.md) and link to it from SKILL.md to enable one-level-deep progressive disclosure.

Add an explicit validation/retry step after running actions (check the output field for errors, retry or surface clientAction on failure) to strengthen the workflow feedback loop.

Trim repeated auth-handling commentary and the 'Popular actions' preamble that restates the preceding search instructions to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-forward with command examples, but includes some light over-explanation (e.g. restating that Membrane handles auth) that could be trimmed, keeping it just below the lean benchmark.	4 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands covering the common cases (login, connection ensure, action list/run, request proxy) with concrete flags and example payloads.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with polling and state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but lacks an explicit validate-then-retry loop after actions and does not call out batch/destructive operation validation, leaving a minor validation gap.	4 / 5
Progressive Disclosure	There are no bundle files (references/, scripts/, assets/ absent), and the SKILL.md inlines reference-style material (full proxy flag table, popular actions) that is appropriate as a single overview but offers no one-level-deep split for deeper navigation.	3 / 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 covers the essentials with a clear what-and-when structure and a distinct niche, but its action verbs and trigger phrases are generic. Adding concrete capability terms and natural synonyms would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Ataccama capabilities such as 'profile, cleanse, and monitor data quality, run rules, and execute data governance workflows' to improve specificity.

Expand the 'Use when...' trigger with natural phrases users actually say, e.g. 'Use when working with Ataccama, data quality rules, data profiling, or data governance tasks'.

Add domain-specific synonyms (data quality, data governance, data stewardship, profiling) so the description matches varied user phrasings.

Dimension	Reasoning	Score
Specificity	Names the Ataccama domain plus a few concrete actions ('Manage data, records, and automate workflows'), but the actions are generic and not comprehensively enumerated, matching the anchor for 1-2 concrete actions rather than several specific ones.	3 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Ataccama data'), but the 'when' clause is somewhat generic and could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	'Ataccama' and 'data' are relevant keywords but natural synonyms and variations a user might say (e.g. 'data quality', 'data governance', 'profiling') are missing, leaving only some relevant terms.	3 / 5
Distinctiveness Conflict Risk	Ataccama is a clearly distinct niche with dedicated triggers, with only minor overlap risk against other generic data-integration skills.	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/ataccama/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.