CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

manual-api-curl-testing

Autonomous API & Microservices test suite runner for FinanceHub. Executes all health checks, RFC 7807 problem details validation, and Open Finance endpoints in a single command using an object parameter payload.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/manual-api-curl-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 skill body delivers a genuinely executable single-command runner with a precise enumeration of all 8 tests and their expected outcomes — strong actionability and organization. Its main weaknesses are the absence of any failure-handling guidance for the batch test run (which the rubric caps workflow clarity for) and a machine-specific file:// script link. Minor redundancy around the 'single command' framing could be trimmed.

Suggestions

Add a short 'Interpreting results' section: check summary.failed in the RESULT_JSON block and instruct what to do on failure (e.g., report failing endpoints with their error details before retrying).

Replace the machine-specific absolute file:/// link with a relative path to scripts/test-runner.js so the reference works in any checkout.

Briefly state where the PLUGGY_ACCESS_TOKEN and userId come from, or note that they should be sourced from existing session/config context.

DimensionReasoningScore

Conciseness

The body is largely efficient — a single executable command, a compact 8-item test table with URLs and expected status codes, and a short sample output. Minor trimmable redundancy exists: the 'single command' point is restated in the title, the Purpose section, and the Execution section ('all 8 health checks... in a single command permission request'). Not 5 because of that repeated framing and the decorative header padding.

4 / 5

Actionability

The execution command is concrete and nearly copy-paste ready ('node .agents/skills/.../test-runner.js' with a full JSON payload), and the 8 tests are enumerated with exact endpoints, methods, and expected status codes. Minor gaps keep it from 5: no guidance on where to obtain the PLUGGY_ACCESS_TOKEN and userId, and the file:// link to the script uses a machine-specific absolute path.

4 / 5

Workflow Clarity

The single action (run the node command with the JSON config) is unambiguous, which would normally merit a high score for a simple skill. However, the runner executes 8 tests in one batch including mutating POST /sync operations (full portfolio ingestion), and the skill provides no verification or failure-handling guidance — it shows a sample all-passed output but never says what to do when 'failed' is nonzero. Per the rubric's batch-operation cap, workflow clarity cannot exceed 3 without validation steps.

3 / 5

Progressive Disclosure

The body is well-organized into clearly labeled sections (Trigger, Purpose, Execution, Tests, Output) and the single bundle script (scripts/test-runner.js) exists and is appropriately kept out of the main file. Not 5 because the script reference uses a machine-specific absolute file:// URL ('file:///home/josemd12/Code/...') instead of a portable relative link, and the inline test enumeration could live in a reference file if the suite grows.

4 / 5

Total

15

/

20

Passed

Description

58%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 communicates a concrete, well-scoped capability but omits any 'when to use' trigger guidance, which is its most significant gap. It leans on domain jargon (RFC 7807, object parameter payload) rather than natural user phrasing. Adding an explicit 'Use when...' clause with natural trigger terms would substantially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to test FinanceHub APIs, run health checks, or validate Open Finance endpoints.'

Include natural trigger terms users would actually say, such as 'curl', 'API testing', 'endpoint testing', or 'run the test suite', alongside the technical terminology.

Consider briefly noting the single-command permission benefit in plainer language, since 'object parameter payload' is implementation detail rather than user-facing capability.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Executes all health checks, RFC 7807 problem details validation, and Open Finance endpoints in a single command using an object parameter payload' — which goes beyond naming the domain. It falls short of 5 because 'all health checks' and 'Open Finance endpoints' are category labels rather than enumerated concrete capabilities.

4 / 5

Completeness

The 'what' is clear (executes health checks, RFC 7807 validation, and Open Finance endpoint tests in a single command), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. Not 2 because the 'what' is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Relevant keywords like 'API', 'Microservices', 'test suite runner', 'health checks', and 'RFC 7807 problem details' are present, but common natural variations users would say — 'curl', 'endpoint testing', 'integration tests', 'API testing' — are missing. Not 4 because the technical jargon (RFC 7807, object parameter payload) dominates over natural phrasing.

3 / 5

Distinctiveness Conflict Risk

The description is anchored to a specific project ('for FinanceHub') and specific protocols (RFC 7807, Open Finance), giving it a clear niche with minimal conflict risk. Not 5 because 'API & Microservices test suite runner' is still a fairly broad category that could overlap with other general API-testing skills.

4 / 5

Total

14

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

JoseMD12/finance-hub

Path

.agents/skills/manual-api-curl-testing/SKILL.md

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.