factorialhr
Factorial 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 Factorial. Routes through Apideck with serviceId "factorialhr".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 platform (Factorial), the integration mechanism (Apideck HRIS unified API), concrete actions (read/sync employees, departments, payrolls, time-off records), and explicit trigger conditions. It uses proper third-person voice and is concise without unnecessary fluff. The description would allow Claude to confidently select this skill when a user mentions Factorial HR data operations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and explains the integration mechanism via Apideck's HRIS unified API with serviceId switching. | 3 / 3 |
Completeness | Clearly answers both 'what' (read/sync employees, departments, payrolls, time-off records via Apideck HRIS unified API) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Factorial'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Factorial', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'factorialhr', and 'sync'. These cover the terms a user working with Factorial HR would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Factorial HR via Apideck with serviceId 'factorialhr'. The combination of the specific platform (Factorial), the integration layer (Apideck), and the serviceId makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured connector skill with strong actionability and excellent progressive disclosure to related skills. Its main weaknesses are marketing-style verbosity (repeating the portability pitch multiple times) and a lack of explicit workflow sequencing — particularly around verifying connection state before making calls and handling coverage gaps. Trimming the sales pitch and adding a numbered workflow would significantly improve it.
Suggestions
Remove or consolidate the 'Portable across 58 HRIS connectors' section — the portability point is already made in the intro and the code example can be folded into the minimal example section.
Add a sequenced workflow: 1) Verify connection is callable, 2) Check coverage for needed operations, 3) Make API calls, 4) Fall back to proxy if unsupported — with explicit validation at each step.
Trim the 'When to use this skill' section to just the numbered list; Claude doesn't need activation trigger examples explained in prose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the portability pitch already made in the intro, and phrases like 'This is the compounding advantage of using Apideck over integrating Factorial directly' are marketing copy that wastes tokens. The 'When to use this skill' section also over-explains activation triggers Claude can infer. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing employees, a concrete curl command for verifying coverage, and a complete proxy API escape hatch with real headers. All examples are copy-paste ready with clear environment variable references. | 3 / 3 |
Workflow Clarity | The skill covers multiple operations (list employees, verify coverage, proxy fallback) but doesn't sequence them into a clear workflow with validation checkpoints. There's no explicit 'verify connection is callable before making API calls' step or error handling flow for when coverage checks fail. The connection lifecycle (available → added → authorized → callable) is mentioned but not turned into actionable verification steps. | 2 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references to sibling skills (apideck-node, apideck-best-practices, apideck-connector-coverage) with clear signals about what each contains. The main file stays focused on Factorial-specific concerns while pointing to detailed materials for SDK patterns, Vault setup, and coverage checks. | 3 / 3 |
Total | 10 / 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.