afas-software
AFAS Software integration. Manage data, records, and automate workflows. Use when the user wants to interact with AFAS Software data.
45
47%
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/afas-software/SKILL.mdQuality
Discovery
67%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 a specific software product (AFAS Software) and including an explicit 'Use when' clause, which provides clear triggering guidance. However, the actions described are vague and generic — 'manage data, records, and automate workflows' could apply to almost any integration skill. Adding AFAS-specific capabilities and terminology would significantly improve both specificity and distinctiveness.
Suggestions
Replace generic actions with AFAS-specific capabilities, e.g., 'Query data via GetConnectors, update records via UpdateConnectors, manage financial and HR data in AFAS Profit'.
Add AFAS-specific trigger terms users would naturally use, such as 'AFAS Profit', 'GetConnector', 'UpdateConnector', 'AFAS API', or 'AFAS Online'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AFAS Software) and some general actions ('manage data, records, and automate workflows'), but these actions are broad and not concrete — it doesn't specify what kinds of data, records, or workflows (e.g., 'create invoices, update employee records, sync financial data'). | 2 / 3 |
Completeness | The description answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with AFAS Software data'), providing an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | 'AFAS Software' is a strong specific trigger term that users would naturally say, but the remaining terms ('data', 'records', 'workflows') are very generic and don't include natural variations or specific AFAS-related terms users might mention (e.g., 'AFAS Profit', 'connectors', 'GetConnector', 'UpdateConnector'). | 2 / 3 |
Distinctiveness Conflict Risk | 'AFAS Software' is a distinctive trigger that reduces conflict with generic data/workflow skills, but the broad terms 'manage data, records, and automate workflows' could overlap with other integration or automation skills. The AFAS branding helps but the generic action terms weaken distinctiveness. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill suffers severely from an enormous, repetitive action catalog that dominates the content without adding value—Claude can discover actions via the CLI. The Membrane CLI integration instructions are reasonably actionable but lack AFAS-specific examples. The content would benefit dramatically from removing the action list, adding concrete AFAS workflow examples, and splitting reference material into separate files.
Suggestions
Remove or drastically reduce the action catalog (the 100+ List/Get bullet points) since `membrane action list --intent=QUERY` already provides discovery—replace with 2-3 concrete examples showing real AFAS workflows (e.g., retrieving an invoice, creating a connector filter).
Add concrete, end-to-end examples with actual AFAS-specific parameters and expected output shapes, such as listing invoices with filters or executing a workflow.
Extract any reference material (action categories, API endpoint patterns) into a separate REFERENCE.md file and link to it from the main skill.
Add validation/error handling guidance for action runs—what to do when an action fails, how to interpret error responses, and retry strategies.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with a massive list of 100+ actions that are all repetitive variations of 'List X / Get X — Use this to list/retrieve details of a specific X.' This is pure padding that Claude can infer from a single pattern. The overview section alone is ~120 lines of near-identical bullet points. | 1 / 3 |
Actionability | The CLI commands for authentication, connection setup, action discovery, and running actions are concrete and executable. However, there are no AFAS-specific examples (e.g., how to actually retrieve an invoice or create a connector filter with real parameters), and the massive action list provides no actionable detail beyond names. | 2 / 3 |
Workflow Clarity | The connection setup workflow has a reasonable sequence with state handling (READY, CLIENT_ACTION_REQUIRED, etc.) and polling instructions. However, there are no explicit validation checkpoints for the broader workflow of discovering and running actions, and no error recovery guidance for failed action runs. | 2 / 3 |
Progressive Disclosure | The entire content is a monolithic wall of text with no references to external files. The massive action catalog should be in a separate reference file or omitted entirely since `membrane action list` already provides discovery. No bundle files exist to offload this content. | 1 / 3 |
Total | 6 / 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.