afas
AFAS Software integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in AFAS Software. Routes through Apideck with serviceId "afas".
75
71%
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 ./connectors/afas/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly identifies the specific integration (AFAS Software via Apideck HRIS API), lists concrete data entities it handles, and provides an explicit 'Use when' clause with natural trigger terms. The inclusion of technical details like serviceId adds precision without sacrificing clarity. Minor improvement could include mentioning file formats or additional action verbs, but overall it's well-crafted.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and specifies the integration mechanism (Apideck's HRIS unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both what ('AFAS Software integration via Apideck's HRIS unified API' with specific data types) and when ('Use when the user wants to read or sync employees, departments, payrolls, and time-off records in AFAS Software'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'AFAS Software', 'employees', 'departments', 'payrolls', 'time-off records', 'Apideck', 'HRIS', 'sync'. These cover the domain well and match how users would phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific product names (AFAS Software, Apideck), a specific serviceId ('afas'), and a clear niche (HRIS integration). Unlikely to conflict with other skills unless there are other AFAS-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has good structure and progressive disclosure with clear references to related skills, but suffers from significant verbosity — marketing language about Apideck's advantages, repeated explanations of the unified API concept, and content Claude doesn't need. The actionable content (code examples, curl commands) is solid but the workflow for handling coverage gaps could be more explicit with validation steps.
Suggestions
Remove the 'Portable across 58 HRIS connectors' section and the marketing language in the intro — Claude doesn't need to be sold on Apideck's value proposition. A single line noting portability via serviceId change suffices.
Trim the 'When to use this skill' section to just the serviceId and API mapping; Claude can infer activation criteria from context.
Add a clear sequential workflow: 1) Verify coverage (with example of parsing the response), 2) Call unified API, 3) Handle UnsupportedOperationError → fall back to Proxy, with explicit validation at each step.
Remove explanations of what Apideck handles (auth, pagination, rate limiting, retries) — this is covered in the best-practices skill and doesn't need repeating here.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. The 'Portable across 58 HRIS connectors' section repeats the marketing pitch from the intro. Explanations of what Apideck does (handles auth, pagination, rate limiting) and the 'compounding advantage' paragraph are unnecessary for Claude. The 'When to use this skill' section over-explains activation criteria. Much of this content is promotional rather than instructional. | 1 / 3 |
Actionability | The TypeScript example is executable and copy-paste ready, and the curl commands for coverage verification and proxy API are concrete. However, the skill is mostly reference/configuration information rather than step-by-step guidance. Key details like what specific HRIS resources are available for AFAS are missing, delegated entirely to external references. | 2 / 3 |
Workflow Clarity | There's an implicit workflow: check coverage → use unified API → fall back to proxy if unsupported. However, this isn't presented as a clear sequence with validation checkpoints. The coverage verification step exists but there's no guidance on interpreting the response or what to do with specific error cases beyond a reference to another skill. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and one-level-deep references to sibling skills (apideck-node, apideck-best-practices, apideck-connector-coverage). The 'See also' section provides clear navigation. Content is appropriately split between this connector-specific skill and the shared SDK/best-practices skills. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- apideck-libraries/api-skills
- Commit
9e04d86
- 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.