adatree
Adatree integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adatree data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill adatree61
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description relies heavily on the proper noun 'Adatree' for distinctiveness but fails to explain what Adatree actually does or what specific capabilities this skill provides. The actions listed are generic enough to apply to dozens of different integrations, making it difficult for Claude to confidently select this skill over others.
Suggestions
Replace generic terms with Adatree-specific capabilities (e.g., 'Access consumer banking data via Open Banking APIs, retrieve account balances, transaction history')
Add domain-specific trigger terms users would naturally say (e.g., 'Open Banking', 'CDR', 'consumer data right', 'bank account access')
Expand the 'Use when...' clause with concrete scenarios (e.g., 'Use when the user needs to access Open Banking data, retrieve financial records, or connect to Australian CDR services')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. These are abstract capabilities that could apply to almost any integration. | 1 / 3 |
Completeness | Has a 'Use when...' clause which addresses the 'when', but the trigger is circular ('interact with Adatree data'). The 'what' is too vague to be useful for skill selection. | 2 / 3 |
Trigger Term Quality | Includes 'Adatree' as a specific keyword users might say, but 'data', 'records', and 'workflows' are overly generic terms. Missing domain-specific terminology that would help identify Adatree-specific use cases. | 2 / 3 |
Distinctiveness Conflict Risk | 'Adatree' as a proper noun provides some distinctiveness, but 'manage data, records, and automate workflows' could overlap with many other integration or data management skills. | 2 / 3 |
Total | 7 / 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.
This skill provides solid actionable CLI commands for Membrane integration with Adatree, making it practical for execution. However, it wastes tokens on introductory context about Adatree that Claude doesn't need, and the entity overview section adds no value without further context. The workflow lacks validation steps and error recovery guidance.
Suggestions
Remove the introductory paragraph explaining what Adatree is and the entity overview section, or link the entities to specific actions/documentation
Add validation checkpoints after key steps (e.g., 'Verify connection succeeded: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failure scenarios (authentication failures, connection timeouts)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., describing what Adatree is and its use cases, which Claude doesn't need). The overview section listing entities without context adds little value. However, the CLI commands are reasonably concise. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options. The proxy request section includes a helpful options table. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack explicit validation checkpoints. No feedback loops for error recovery (e.g., what to do if connection fails, how to verify a connection succeeded before running actions). | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the Adatree Overview section listing entities serves no purpose without linking to detailed documentation. The skill could better signal when to reference external docs vs. inline content. | 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 | |
- 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.