api-setup

Set up API integration with configuration and helper scripts

1.33x

Quality

—

Does it follow best practices?

Impact

91%

1.33x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, well-structured instruction skill with clear sequencing and verification, but its actionability is undermined by an abstract test step and references to bundle files that are not present. It scores high on clarity and disclosure, slightly lower on executable guidance.

Suggestions

Replace 'Test the connection' with a concrete command or script invocation so the verification step is copy-paste ready.

Either ship the referenced setup.sh and templates/config.template.json in the bundle or remove/qualify those references so the guidance does not point at missing files.

Provide a one-line example of a populated config field so the 'Update the config' step is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned with no concept padding Claude already knows; the only mild redundancy is the opening line restating the description, but every section earns its place.	3 / 3
Actionability	It gives concrete commands like 'Run setup.sh <api-name>' and a template path, but 'Test the connection' is abstract with no command, and the referenced setup.sh and templates/ files do not exist in the bundle.	2 / 3
Workflow Clarity	Steps are numbered and followed by an explicit verification checklist plus a troubleshooting section with error-recovery guidance for timeouts and auth errors, matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	At under 50 lines with no need for external references, the well-organized sections (Steps, Configuration, Verification, Troubleshooting) satisfy the simple-skill allowance for a top score.	3 / 3
	Total	11 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the domain and a few actions but reads as a flat capability statement without explicit use-when triggers or distinctive keywords. It is adequate but unremarkable, landing mid-scale across all dimensions.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when onboarding a new third-party REST API or when the user asks to wire up an API client').

List more concrete actions instead of generic nouns (e.g., 'generate config files, scaffold a client, and verify authentication' rather than 'configuration and helper scripts').

Include natural user-facing terms such as REST, endpoints, API key, and provider name to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase 'Set up API integration with configuration and helper scripts' names the domain and some actions but is not comprehensive; it lacks multiple concrete actions like the score-3 anchor.	2 / 3
Completeness	It states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	'API integration', 'setup', and 'configuration' are relevant keywords a user might say, but coverage of natural variations is thin and missing common terms like REST, endpoints, or provider names.	2 / 3
Distinctiveness Conflict Risk	'API integration' is somewhat specific but generic enough to overlap with other integration-oriented skills; it lacks the distinct niche triggers of the score-3 anchor.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: block/agent-skills
Commit: 329a55d

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.