freshteam
Freshteam integration via Apideck's HRIS, ATS unified API — same methods work across every connector in HRIS, ATS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Freshteam. Routes through Apideck with serviceId "freshteam".
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 integration (Freshteam via Apideck), lists concrete data entities it handles (employees, departments, payrolls, time-off records), and provides an explicit 'Use when' clause with natural trigger terms. The description is concise, uses third-person voice, and is distinctive enough to avoid conflicts with similar connector skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and mentions the integration mechanism (Apideck unified API, serviceId). It also describes the cross-connector switching capability. | 3 / 3 |
Completeness | Clearly answers both 'what' (Freshteam integration via Apideck for reading/syncing employees, departments, payrolls, time-off) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Freshteam'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Freshteam', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'ATS', 'Apideck', and 'serviceId'. These cover the domain well and match what users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Freshteam', the Apideck routing mechanism, and the explicit serviceId 'freshteam'. This creates a clear niche that is unlikely to conflict with other HRIS/ATS skills for different providers. | 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.
This is a solid connector-specific skill that provides actionable code examples and excellent cross-referencing to related skills. Its main weaknesses are some marketing-style verbosity (the portability pitch is repeated) and a lack of explicit workflow sequencing with validation checkpoints for the multi-step process of setting up and using the integration.
Suggestions
Remove or condense the 'Portable across 58 HRIS connectors' section — the intro already explains portability, and the code comparison adds little beyond what Claude can infer.
Add an explicit numbered workflow combining coverage verification, API call, and error handling into a clear sequence with validation checkpoints (e.g., 'If coverage check shows unsupported → use proxy API').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the marketing pitch from the intro, and the 'compounding advantage' paragraph is filler Claude doesn't need. The sibling connectors list is extensive but arguably useful for navigation. Overall mostly efficient but could be tightened. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing employees, a concrete curl command for verifying coverage, and a concrete curl command for the proxy escape hatch. The serviceId, auth setup, and SDK initialization are all copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (authenticate → verify coverage → call API → use proxy if needed) but it's not explicitly sequenced with numbered steps or validation checkpoints. The coverage verification step is mentioned but not integrated into a clear workflow with error handling/feedback loops. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview and well-signaled one-level-deep references to SDK skills, best practices, connector coverage, OpenAPI specs, and official docs. Content is appropriately split between this skill and referenced materials. | 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.