api-setup
Set up API integration with configuration and helper scripts
54
32%
Does it follow best practices?
Impact
91%
1.33xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./api-setup/SKILL.mdQuality
Discovery
14%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 description is too vague and generic to be effective for skill selection. It lacks specific actions, explicit trigger conditions, and distinguishing details that would help Claude choose it over other skills. The broad terms 'API integration' and 'helper scripts' provide minimal guidance for when this skill should be activated.
Suggestions
Specify which APIs or types of APIs this skill handles (e.g., REST APIs, specific third-party services) and list concrete actions like 'generate API client code, configure authentication, create request/response handlers'.
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to connect to an external API, set up API authentication, or generate API integration boilerplate.'
Include distinguishing details about what makes this skill unique compared to general coding or configuration skills, such as the specific frameworks, languages, or API patterns it supports.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description is vague — 'API integration' is broad, and 'configuration and helper scripts' doesn't specify what kind of APIs, what configuration, or what the helper scripts do. No concrete actions are listed. | 1 / 3 |
Completeness | The description weakly addresses 'what' (set up API integration) but provides no 'when' clause or explicit trigger guidance. The lack of a 'Use when...' clause caps this at 2 per the rubric, and the 'what' is also too vague, bringing it to 1. | 1 / 3 |
Trigger Term Quality | 'API integration' and 'configuration' are somewhat relevant keywords a user might say, but the description lacks common variations or specific terms like 'REST API', 'API key', 'endpoint', 'webhook', or specific API names that would help match user intent. | 2 / 3 |
Distinctiveness Conflict Risk | 'API integration' is extremely broad and could conflict with many other skills involving APIs, web services, backend development, or configuration management. There is nothing to distinguish this from other API-related skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable structure for API setup but falls short on actionability—key steps like 'Test the connection' lack concrete commands, and the config template content is described but not shown. The troubleshooting section adds bulk with advice Claude already knows, and the absence of bundle files (setup.sh, config template) undermines the skill's practical utility.
Suggestions
Add the actual content of `templates/config.template.json` as a code block or include it as a bundle file, and provide a concrete test connection command or script
Replace the vague 'Test the connection' step with an executable command like `curl` or a script invocation with expected output
Remove or significantly trim the troubleshooting section—Claude already knows basic debugging steps like checking network connections and verifying credentials
Add a validation step after running setup.sh (e.g., verify directory structure was created correctly) and provide a feedback loop for the verification checklist failures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation (e.g., 'This skill helps you set up a new API integration with our standard configuration' is filler, and the troubleshooting section explains basic debugging steps Claude already knows like 'Check your network connection'). | 2 / 3 |
Actionability | Provides some concrete guidance (setup.sh command, config fields, checklist) but lacks executable code examples, doesn't show the actual config template content, and the 'Test the connection' step is vague with no specific command or code provided. | 2 / 3 |
Workflow Clarity | Steps are listed in sequence and there's a verification checklist, but the workflow lacks explicit validation checkpoints between steps (e.g., no check after step 1 that the directory was created, no feedback loop if the test connection fails, and 'Test the connection' has no concrete command). | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the troubleshooting section could be in a separate file, and there are no references to external files despite mentioning templates/config.template.json and setup.sh which should exist in a bundle but don't. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- block/agent-skills
- Commit
60bfdad
- 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.