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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-install-auth88
Quality
83%
Does it follow best practices?
Impact
100%
1.17xAverage score across 3 eval scenarios
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 cases. The main weakness is that the capability description could be more specific about the concrete actions performed (e.g., what files are created, what configuration steps are taken). The trigger terms are excellent and the scope is clearly defined.
Suggestions
Expand the capability description with more concrete actions like 'creates configuration files', 'validates API credentials', or 'sets up environment variables' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io API) and some actions (install, configure, authentication), but lacks comprehensive concrete actions like 'store credentials', 'validate API key', or 'create client instance'. | 2 / 3 |
Completeness | Clearly answers both what (install and configure Apollo.io API authentication) and when (setting up new integration, configuring API keys, initializing client) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'install apollo', 'setup apollo api', 'apollo authentication', 'configure apollo api key'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Apollo.io API setup with distinct triggers. Unlikely to conflict with other skills due to the specific product name and authentication focus. | 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 clear workflow steps and executable code examples. The main weakness is redundancy between the Instructions and Examples sections, which inflates token usage. The error handling table and verification step are strong additions that demonstrate good practice.
Suggestions
Remove the Examples section or consolidate with Instructions - the TypeScript and Python code appears twice with minor variations
Move the detailed class-based implementations to a separate EXAMPLES.md file and keep only the minimal setup in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy - both TypeScript and Python examples are shown twice (in Instructions and Examples sections), and the prerequisites section explains things Claude would know (like what a package manager is). | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for both TypeScript and Python. Commands are specific, code examples are complete with imports, and the error handling table gives concrete solutions. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit verification step (Step 4). The workflow progresses logically from installation to configuration to client creation to verification, with error handling guidance for troubleshooting. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the Examples section duplicates the Instructions content rather than being split to a separate file. The skill is somewhat long (~100 lines) and could benefit from moving detailed examples to a reference file. | 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 | |
- 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.