close
Close 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 Close. Routes through Apideck with serviceId "close".
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 (Close), the integration mechanism (Apideck unified API), the concrete actions supported (read, write, search), and the specific entities (contacts, companies, leads, opportunities, activities, pipelines). It includes an explicit 'Use when' clause with natural trigger terms and is distinctive enough to avoid conflicts with similar CRM skills for other connectors.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, or search contacts, companies, leads, opportunities, activities, and pipelines'. Also mentions the integration mechanism (Apideck's CRM unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both 'what' (read, write, search CRM entities via Apideck unified API) and 'when' (explicit 'Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in Close'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Close', 'CRM', 'contacts', 'companies', 'leads', 'opportunities', 'activities', 'pipelines', 'Apideck'. These cover the main entities and the product name well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Close', the routing mechanism 'Apideck with serviceId "close"', and the explicit CRM entity types. This would clearly distinguish it from other CRM connector skills for different services. | 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 well-structured connector skill with strong actionability (executable code examples) and excellent progressive disclosure to related skills and references. Its main weaknesses are moderate verbosity from repeated portability messaging and marketing-style language, plus a workflow that could be more explicitly sequenced with validation checkpoints.
Suggestions
Remove the 'Portable across 21 CRM connectors' section — the portability point is already made in the intro and the code example could be folded into the minimal example section.
Present a clear numbered workflow: 1) verify coverage → 2) call unified API → 3) handle errors → 4) fall back to proxy if needed, with explicit validation at each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity — e.g., the 'Portable across 21 CRM connectors' section repeats the portability point already made in the intro, and the 'compounding advantage' paragraph is marketing fluff Claude doesn't need. The 'When to use this skill' section also over-explains. However, the code examples and quick facts are lean. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing contacts, a working curl command for coverage verification, and a complete proxy API curl example with all required headers. These are copy-paste ready with clear variable substitution. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (connect → verify coverage → use unified API → fall back to proxy), but it's not presented as a clear sequence with validation checkpoints. The coverage verification step is mentioned but not integrated into a coherent 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. The 'See also' section provides clear navigation to related resources. | 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.