apollo-install-auth
Install and configure Apollo.io API authentication. Use when setting up a new Apollo integration, configuring API keys, or initializing Apollo client in your project. Trigger with phrases like "install apollo", "setup apollo api", "apollo authentication", "configure apollo api key".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 well-structured skill description with explicit trigger guidance and clear 'Use when' clauses. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., generating config files, storing secrets, testing connectivity). The description also uses second person ('your project') which is a minor style issue but doesn't severely impact functionality.
Suggestions
Add more specific concrete actions to the capability description, e.g., 'Generates configuration files, stores API secrets securely, and tests API connectivity' to improve specificity.
Rephrase 'initializing Apollo client in your project' to third person voice, e.g., 'initializing Apollo client in a project' to align with style guidelines.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io API) and some actions (install, configure authentication), but doesn't list multiple concrete actions beyond setup-related tasks. It's somewhat specific but not comprehensive in detailing what the skill actually does step-by-step. | 2 / 3 |
Completeness | Clearly answers both 'what' (install and configure Apollo.io API authentication) and 'when' (setting up a new Apollo integration, configuring API keys, initializing Apollo client). Has explicit 'Use when' clause and even a 'Trigger with phrases' section. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'install apollo', 'setup apollo api', 'apollo authentication', 'configure apollo api key'. These are realistic phrases a user would type when needing this skill. Also mentions 'API keys' and 'Apollo client' as additional natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Apollo.io API authentication setup, which is a clear niche. The explicit mention of 'Apollo.io' and authentication-specific triggers make it unlikely to conflict with other skills, though there could be minor overlap with a general API configuration skill. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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, actionable skill with executable code examples and clear workflow sequencing including verification steps and error handling. Its main weakness is verbosity from including complete implementations in two languages inline, which could benefit from splitting into separate files. The error handling table and cURL verification example are excellent practical additions.
Suggestions
Consider splitting TypeScript and Python implementations into separate referenced files (e.g., TYPESCRIPT.md and PYTHON.md) to reduce inline content length and improve progressive disclosure.
Remove the 'Output' section as it merely restates what the steps already produce, saving tokens without losing clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — providing both TypeScript and Python implementations inline makes it lengthy. The prerequisites and some explanatory text (e.g., 'There is no official SDK') are useful but could be tighter. The Output section restates what was already shown. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready across TypeScript, Python, and cURL. Specific file paths, environment variable setup, and verification scripts are provided with concrete commands. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced from installation through verification. Step 4 includes explicit validation with error handling for different failure modes (401, network errors), and the error handling table provides a clear feedback loop for troubleshooting. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but having both full TypeScript and Python implementations inline makes it a monolithic document. The Python client could be in a separate reference file. References to external resources and next steps are well-signaled, but no bundle files exist to offload the detailed implementations. | 2 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.