api-tester

Test and document API endpoints - validate responses, check status, generate examples

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/research-tools/capabilities/api-tester/SKILL.md

Quality

Content

57%

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

The skill is well-structured and lean but undermined by broken curl/JSON examples and a mismatched GET-vs-POST step, plus missing validation checkpoints in a skill explicitly about validation. Fixing the malformed commands and adding verify steps would most improve it.

Suggestions

Repair the malformed JSON payloads in Steps 2 and 4, Example Usage, and Discover More so each -d body is a single valid JSON string.

Make Step 1 actually test GET endpoints (or relabel it) and add an explicit response-validation step that checks status codes and schema against expected fields.

De-duplicate the curl boilerplate and the repeated 'Discover More' search example to recover token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused with no padding of basic concepts, but the identical curl auth/header boilerplate is repeated across nearly every section and the 'Discover More' block is duplicated, so it could be tightened.	2 / 3
Actionability	Concrete curl commands are provided, but several JSON payloads are malformed (mismatched braces, fields placed outside the -d string, a stray 'api show riveter' token), so the examples are not copy-paste executable as written.	2 / 3
Workflow Clarity	Steps are numbered and sequenced, but the 'Test GET Endpoints' step actually issues a POST and there are no validation/verification checkpoints despite the skill being about validating responses, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist; the single self-contained doc is organized into clear sections (Setup, Workflow, Example Usage, Tips, Discover More), which for a simple skill satisfies well-organized sectioning.	3 / 3
	Total	9 / 12 Passed

Description

60%

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 is specific and action-oriented but lacks an explicit 'Use when' trigger and natural-term coverage, leaving it solid but not exemplary. Adding trigger guidance and common user phrasings would raise completeness and trigger quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when testing or validating an API, documenting endpoints, or checking response status and schemas.'

Add natural trigger terms users would actually say, such as 'API testing', 'test an endpoint', 'REST API', or 'API documentation'.

Sharpen the niche by referencing response/schema validation specifically to reduce overlap with generic documentation skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'test', 'document', 'validate responses', 'check status', 'generate examples' — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It clearly answers what the skill does but provides no 'Use when...' trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'API endpoints', 'validate responses', and 'check status' are relevant but it misses common natural variations a user would say (e.g. 'test an API', 'API testing', 'REST endpoints'), so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	'Test and document API endpoints' defines a recognizable niche, but 'document API endpoints' could overlap with general documentation skills, so it is not clearly distinct from all similar skills.	2 / 3
	Total	9 / 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: gooseworks-ai/goose-skills
Path: skills/research-tools/capabilities/api-tester/SKILL.md
Commit: 8866b2a

Reviewed: 1 day 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.