addressfinder-australia
AddressFinder Australia integration. Manage data, records, and automate workflows. Use when the user wants to interact with AddressFinder Australia data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill addressfinder-australia61
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 identifies a specific integration (AddressFinder Australia) but fails to explain what the service actually does or when users would need it. The generic phrases 'manage data, records, and automate workflows' could apply to almost any integration, and the 'Use when' clause is circular rather than providing actionable trigger guidance.
Suggestions
Replace vague actions with specific capabilities like 'Validate Australian addresses, autocomplete address fields, verify postcodes and suburbs, standardize address formats'
Expand the 'Use when' clause with natural trigger terms: 'Use when validating Australian addresses, looking up postcodes, autocompleting address fields, or verifying suburb/state combinations'
Add common user phrases that would trigger this skill: 'address validation', 'postcode lookup', 'Australian address', 'suburb finder'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what AddressFinder Australia actually does (address validation, autocomplete, verification, etc.). | 1 / 3 |
Completeness | Has a 'Use when' clause but it's circular ('interact with AddressFinder Australia data'). The 'what' is vague ('manage data, records') and the 'when' doesn't provide meaningful trigger guidance beyond the product name. | 2 / 3 |
Trigger Term Quality | Includes 'AddressFinder Australia' as a specific product name which is useful, but lacks natural user terms like 'address lookup', 'validate address', 'Australian addresses', 'postcode', or 'suburb search'. | 2 / 3 |
Distinctiveness Conflict Risk | 'AddressFinder Australia' is a specific product name providing some distinctiveness, but 'manage data, records, and automate workflows' is generic enough to overlap with many 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 integrating with AddressFinder Australia via Membrane, with good structure and executable examples. However, it includes unnecessary explanatory content about what AddressFinder is, and lacks validation checkpoints in workflows. The content could be more concise by removing the SaaS description and tightening the authentication explanations.
Suggestions
Remove the opening paragraph explaining what AddressFinder Australia is - Claude already knows this and it wastes tokens
Add validation steps after key operations (e.g., 'Verify connection succeeded: membrane connection list --json | grep CONNECTION_ID')
Add error handling guidance for common failures like authentication timeout or invalid credentials
Consolidate the repeated mentions of Membrane handling authentication into a single, brief statement
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what AddressFinder Australia is, which Claude likely already knows. The Membrane CLI setup instructions are necessary but could be tighter. Some redundancy exists in explaining authentication benefits multiple times. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax. Commands are copy-paste ready with placeholders clearly marked (CONNECTION_ID, CONNECTOR_ID). The proxy request section includes a comprehensive options table. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming actions completed successfully. Missing feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one file. The API overview section is minimal, and there's no reference to external files for advanced usage, examples, or detailed API documentation beyond the external link. | 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.