adatree
Adatree integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adatree data.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/adatree/SKILL.mdQuality
Discovery
57%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 benefits from naming the specific product (Adatree) and including an explicit 'Use when' clause, but it is severely lacking in specificity about what the skill actually does. The actions described are generic enough to apply to virtually any data integration tool, making it hard for Claude to confidently select this skill over others in a large skill library.
Suggestions
Replace vague actions with specific Adatree capabilities, e.g., 'Query consumer data holders, manage consent flows, retrieve banking/energy data via CDR APIs'.
Add domain-specific trigger terms that users would naturally say, such as 'open banking', 'CDR', 'consumer data right', 'consent management', or 'data holder'.
Expand the 'Use when' clause with more specific triggers, e.g., 'Use when the user mentions Adatree, open banking, CDR data, or consumer data right integrations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The actions listed ('manage data, records, and automate workflows') are extremely vague and generic. There are no concrete, specific actions like 'create records', 'query consumer data holders', or 'configure consent flows'. This is essentially abstract language. | 1 / 3 |
Completeness | The description does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Adatree data). It has an explicit 'Use when' clause with a trigger condition, even though both parts are vague in substance. | 3 / 3 |
Trigger Term Quality | The term 'Adatree' is a specific product name that would serve as a natural trigger keyword. However, beyond that, the terms 'data', 'records', and 'workflows' are overly generic and wouldn't help distinguish this skill. Missing domain-specific terms like 'open banking', 'CDR', 'consent', or 'consumer data right' that users familiar with Adatree might use. | 2 / 3 |
Distinctiveness Conflict Risk | 'Adatree' as a product name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with dozens of other integration skills. Without specifying what kind of data or workflows, it risks conflicting with other data management or workflow automation skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, actionable CLI commands for integrating with Adatree via Membrane, with clear executable examples throughout. Its main weaknesses are the unnecessary introductory explanation of Adatree (which wastes tokens on context Claude doesn't need), the unexplained entity overview list, and the lack of explicit validation/error-handling steps in the workflow.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Adatree is — Claude doesn't need this context to execute the integration.
Either remove the entity overview bullet list or make it actionable by linking each entity to specific action examples or commands.
Add explicit error handling guidance for `membrane action run` failures and clarify the polling retry pattern (e.g., how many times to retry, what to do on timeout).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adatree is (Australian data sharing platform, sectors, etc.) is unnecessary context for Claude. The overview bullet list of entities adds little value without explaining what to do with them. However, the command examples themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Each command includes concrete flags and placeholders. | 3 / 3 |
Workflow Clarity | The workflow sequence (install → authenticate → connect → discover actions → create if needed → run) is present and logical. However, there are no explicit validation checkpoints or error-handling feedback loops for the action run step, and the polling workflow for action creation could be more explicit about retry logic. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the entity overview list is a wall of unexplained bullet points that adds no navigational value. There are no references to separate files for advanced topics, though the skill may not need them. The link to official docs is good but could be better signaled. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
56d7336
- Reviewed
Table of Contents
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.