Name: datatrails
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

datatrails

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/datatrails/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 a well-structured, mostly executable guide to the Membrane CLI integration with good connection-state feedback loops. Its main weaknesses are marketing padding, a 'Popular actions' section that under-delivers, and a lack of validation on the destructive proxy path.

Suggestions

Add a verification step to the proxy workflow (e.g., re-fetch the resource or check the response status/headers after DELETE/PUT/PATCH) so destructive requests have an explicit feedback loop.

Trim marketing prose ('so you can focus on the integration logic rather than auth plumbing', the awkward agent-types sentence) and the product-intro paragraph to improve token efficiency.

Either populate 'Popular actions' with concrete example DataTrails actions (e.g., list records, fetch event trail) or remove the heading so it does not promise content it does not deliver.

Dimension	Reasoning	Score
Conciseness	The bulk is lean executable commands, but several padded/marketing phrases ('so you can focus on the integration logic rather than auth plumbing', 'Those will be used to adjust tooling to be used best with your harness', 'burn less tokens') and the product-intro paragraph could be tightened.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands across the full flow (install, login, connect, poll, search, run, proxy) plus a flags table; minor gaps remain such as the 'Popular actions' heading that only re-states discovery rather than listing common actions.	4 / 5
Workflow Clarity	The connection flow has an explicit state machine with polling/feedback loops, but the proxy path supports destructive methods (DELETE/PUT/PATCH) with no validation or verification checkpoint, which caps clarity per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files needed; the inline reference material (clientAction object structure, flags table) is reasonable, though the skill exceeds 50 lines so the simple-skill exception does not fully apply.	4 / 5
	Total	14 / 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 functional and includes an explicit 'Use when' trigger plus a named product, but its action verbs are generic and the trigger phrase is narrow. It is distinguishable mainly because of the DataTrails product name rather than crisp capability language.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete DataTrails operations (e.g., 'track data lineage, audit record history, and automate compliance workflows').

Expand the 'Use when' clause to mirror those concrete triggers so users naturally say them (e.g., 'Use when the user wants to trace data lineage, review audit records, or automate compliance checks in DataTrails').

Add common synonyms/extensions users might say (e.g., 'data lineage', 'audit trail', 'compliance') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the DataTrails domain and lists several actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete API-level operations, so coverage is not comprehensive.	3 / 5
Completeness	Answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with DataTrails data'), though the 'when' clause is explicit but narrow and could name the concrete triggers from the 'what' clause.	4 / 5
Trigger Term Quality	Includes the strong product keyword 'DataTrails' plus 'data', 'records', and 'workflows', but relies on generic terms and misses common synonyms or file/format variations a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	The named product 'DataTrails' gives a clear niche with minimal conflict risk, but the broad 'manage data, records, automate workflows' phrasing creates minor overlap with general data-skill triggers.	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/datatrails/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.