CtrlK
BlogDocsLog inGet started
Tessl Logo

api-tester

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

49

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

53%Weight 40%Scale 1-5

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

The body is reasonably well-structured and provides concrete curl examples, but malformed JSON payloads and missing validation checkpoints undermine both actionability and workflow clarity for a skill whose stated purpose is validating API responses.

Suggestions

Fix the broken JSON payloads in steps 2, 4, and Example Usage so the curl commands are copy-paste executable (correct the `-d '{...}'` quoting and brace matching).

Add explicit validation/verification checkpoints (e.g. "check the HTTP status code", "assert the response matches the expected schema") after each request, since this skill's purpose is validating responses.

Correct the Step 1 mismatch where the section is titled "Test GET Endpoints" but the command issues a POST to the proxy, or add a genuine GET example.

DimensionReasoningScore

Conciseness

Mostly efficient credential setup and curl examples with little concept padding, but the "Example Usage" section repeats steps 2-3 and the repeated curl boilerplate across four steps could be tightened.

3 / 5

Actionability

Provides concrete curl commands, but several are malformed JSON (steps 2, 4, and Example Usage have mismatched braces, a missing opening `-d '` quote, and stray `}`), so they are not copy-paste executable.

3 / 5

Workflow Clarity

Steps 1-4 are sequenced, but a skill whose purpose is validating responses has no validation checkpoints, and Step 1 is mislabeled (titled "GET Endpoints" but issues a POST); missing validation for batch API operations caps this at 3.

3 / 5

Progressive Disclosure

Single self-contained file with well-organized sections (Setup, Workflow, Example Usage, Tips, Discover More) and no nested references; minor overlap between the workflow and Example Usage sections keeps it just below 5.

4 / 5

Total

13

/

20

Passed

Description

55%Weight 40%Scale 1-5

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 lists several concrete, relevant actions but omits any "Use when..." trigger guidance, leaving its activation conditions implicit. It is competent but not comprehensive enough to score at the top of the scale.

Suggestions

Add an explicit "Use when..." clause naming the natural triggers (e.g. "Use when testing or documenting REST/API endpoints, validating responses, or generating example requests").

Include common synonyms and file/extension cues users would actually say, such as "REST", "API testing", or "endpoints".

Tighten the niche by specifying a distinct context (e.g. testing external APIs via the Gooseworks proxy) to reduce overlap with other API skills.

DimensionReasoningScore

Specificity

Quotes concrete actions: "Test and document API endpoints", "validate responses", "check status", "generate examples" — several specific actions with only minor gaps in coverage.

4 / 5

Completeness

States a clear "what" (test, document, validate, generate examples) but provides no "when"/"Use when..." clause; per the guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant terms like "API endpoints", "validate responses", "check status" but misses common variations/synonyms (e.g. "API testing", "REST") and lacks a natural trigger phrase.

3 / 5

Distinctiveness Conflict Risk

"Test and document API endpoints" names a niche but is broad enough to overlap with other API-oriented skills, so it is only somewhat specific.

3 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.