folk
Folk integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in Folk. Routes through Apideck with serviceId "folk".
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 CRM platform (Folk), the integration mechanism (Apideck unified API with serviceId), the concrete actions supported (read, write, search), and the specific entity types. The explicit 'Use when' clause with natural trigger terms makes it easy for Claude to select this skill appropriately and distinguish it from other CRM connector skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, or search contacts, companies, leads, opportunities, activities, and pipelines.' Also explains the integration mechanism (Apideck unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both 'what' (Folk integration via Apideck CRM unified API for reading/writing/searching CRM entities) and 'when' (explicit 'Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in Folk'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Folk', 'contacts', 'companies', 'leads', 'opportunities', 'activities', 'pipelines', 'CRM', 'Apideck'. These cover the domain well and match how users would phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Folk', the serviceId 'folk', and the Apideck routing mechanism. Clearly distinguishable from other CRM integrations by the explicit serviceId differentiation pattern. | 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 progressive disclosure through well-signaled references to related skills. Its main weaknesses are moderate verbosity (repeating the portability message, marketing language) and a workflow that could be more explicitly sequenced with validation checkpoints for the coverage-check-then-call pattern.
Suggestions
Consolidate the portability message — remove the 'Portable across 21 CRM connectors' section since the intro already covers this; the code example could move to the minimal example section.
Present the coverage-check → unified-API-call → proxy-fallback pattern as a numbered workflow with explicit decision points (e.g., 'If coverage check shows unsupported → use Proxy API').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 21 CRM connectors' section repeats the portability point already made in the intro, and the 'When to use this skill' section over-explains activation triggers. The marketing-style language ('compounding advantage') adds no instructional value. However, it's not egregiously padded. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing contacts, a working curl command for coverage verification, 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 | There's an implicit workflow (check coverage → use unified API → fall back to proxy if unsupported), but it's not presented as a clear sequential process with explicit validation checkpoints. The coverage verification step and proxy fallback are in separate sections without a cohesive flow connecting them. | 2 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references to sibling skills (apideck-node, apideck-best-practices, apideck-connector-coverage) and external resources. The 'See also' section is well-organized, and the skill keeps its own content at overview level while clearly pointing to detailed 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.