afas-software
AFAS Software integration. Manage data, records, and automate workflows. Use when the user wants to interact with AFAS Software data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill afas-software75
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
75%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 adequately identifies the AFAS Software domain and includes a proper 'Use when' clause, making it complete. However, the capabilities listed are generic ('manage data, records, automate workflows') and could benefit from more specific actions. The trigger terms rely heavily on the product name without covering variations users might use.
Suggestions
Add more specific actions like 'query employee records', 'sync financial data', 'manage HR workflows', or other AFAS-specific operations
Include trigger term variations such as 'AFAS API', 'AFAS connector', 'AFAS Profit', or common use cases like 'Dutch ERP system'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AFAS Software) and mentions some actions ('Manage data, records, and automate workflows'), but these are fairly generic and not comprehensive - doesn't specify what types of data, records, or workflows. | 2 / 3 |
Completeness | Clearly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with AFAS Software data') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'AFAS Software' which is the key product name users would mention, but lacks variations or related terms users might say (e.g., 'AFAS API', 'AFAS connector', specific module names, 'Dutch ERP'). | 2 / 3 |
Distinctiveness Conflict Risk | 'AFAS Software' is a specific product name that creates a clear niche - unlikely to conflict with other skills since it's a distinct software platform. | 3 / 3 |
Total | 10 / 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 actionable CLI commands for AFAS Software integration via Membrane, with good coverage of setup, connection, and action execution. However, it suffers from excessive verbosity in the entity/action listing section which could be dramatically condensed or moved to a reference file. The workflow lacks explicit validation steps for confirming successful operations.
Suggestions
Move the extensive entity and action list to a separate REFERENCE.md file, keeping only a brief summary of available entity categories in the main skill
Add validation checkpoints after key steps (e.g., 'Verify connection with: membrane connection list --json | grep CONNECTION_ID')
Remove repetitive 'Use this to...' descriptions - a single note explaining the List/Get pattern for all entities would suffice
Add error handling guidance for common failure scenarios (auth failures, invalid connection IDs, action not found)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains significant repetition in the overview section listing every entity and action with nearly identical descriptions ('Use this to list/get/retrieve...'). This could be condensed to a reference to available entity types with a note about standard CRUD operations. | 2 / 3 |
Actionability | Provides concrete, executable CLI commands for installation, authentication, connection setup, action discovery, and running actions. Commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The setup workflow is reasonably clear (install → login → connect), but lacks validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections, but the massive entity/action list should be in a separate reference file. The skill would benefit from a concise overview pointing to detailed action references rather than inline listing. | 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.