adatree
Adatree integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adatree data.
58
67%
Does it follow best practices?
Impact
—
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 integration (Adatree) and including an explicit 'Use when' clause, but it is severely lacking in specificity of capabilities. The actions described are generic boilerplate that could apply to any data integration, failing to communicate what Adatree actually does or what unique capabilities this skill provides.
Suggestions
Replace generic actions with specific Adatree capabilities, e.g., 'Retrieve consumer banking data, manage consent flows, query data holders via the Adatree CDR platform'.
Add domain-specific trigger terms that users would naturally use, 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 sharing'.
| 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'. These could apply to virtually any integration. | 1 / 3 |
Completeness | The description does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with Adatree data) with an explicit 'Use when' clause. While the content is vague, the structural completeness requirement is met. | 3 / 3 |
Trigger Term Quality | The term 'Adatree' is a specific and useful trigger keyword that users would say when they need this skill. However, beyond that, the terms 'data', 'records', and 'workflows' are overly generic and don't include natural variations or domain-specific terms (e.g., 'open banking', 'CDR', 'consumer data right', 'consent'). | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Adatree' provides some distinctiveness as a named integration, but 'manage data, records, and automate workflows' is so generic it could easily overlap with dozens of other integration skills. Without domain-specific terms, only the brand name prevents conflicts. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity — the CLI commands are concrete and the connection state machine is well-documented with explicit feedback loops. The main weaknesses are unnecessary introductory context about Adatree (Claude doesn't need to know it's for Australian financial services) and the orphaned entity overview list that doesn't connect to any actionable guidance.
Suggestions
Remove or drastically shorten the introductory paragraph about what Adatree is — Claude doesn't need this context to use the CLI commands effectively.
Either remove the entity overview bullet list or make it actionable by linking each entity to example commands or a reference file showing how to interact with them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adatree is and its sectors is unnecessary context for Claude. The overview bullet list of entities adds little value without explaining what to do with them. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and feedback loops (poll until ready, handle client actions, then proceed). The authentication flow also handles headless environments with a clear fallback path. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic for its length. The entity overview list could link to detailed documentation rather than sitting as an unexplained bullet list. No bundle files are provided, so there's no evidence of content being appropriately split across files. | 2 / 3 |
Total | 10 / 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
f484c82
- 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.