CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/postman-collections

Authors Postman collections (requests + tests + variables + environments), runs them headless via the Newman CLI, configures reporters (cli / json / junit / html) for CI artifact upload, and uses iteration data files (JSON / CSV) for data-driven runs. Use when the project ships HTTP API tests authored in Postman and the team needs CI execution alongside or instead of the Postman desktop runner.

71

Quality

89%

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

Overview
Quality
Evals
Security
Files

Quality

Content

80%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.

A well-structured, actionable body that delegates bulk detail to a single clearly-linked reference file. Its main weakness is workflow_clarity: a batch CI test run lacks an explicit inline validation/retry feedback loop, which the batch-operation cap holds at 3.

Suggestions

Add an explicit validate-and-retry checkpoint to the workflow, e.g. 'After `newman run`, inspect the JUnit/JSON report; on any assertion failure, fix the collection/environment and re-run with `--bail failure`' so the batch operation has an inline verification loop.

Collapse the repeated provenance parentheticals ('(Per [newman-readme][readme].)', '(Adapted from [newman-readme][readme].)') into a single References attribution to tighten token efficiency.

The worked example references examples/sample-collection.json, environment.json, and data.csv that are not in the bundle — ship a minimal example or note where to obtain them so the command is directly copy-paste runnable.

DimensionReasoningScore

Conciseness

Largely lean and assumes competence, but repeated provenance parentheticals ('(Per [newman-readme][readme].)' and '(Adapted from [newman-readme][readme].)') plus a slightly discursive Overview add minor over-explanation that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready install commands, the canonical `newman run <source> [options]` invocation, a fully specified worked example, a reporters table, and real `pm.test` JS snippets that cover the common cases.

5 / 5

Workflow Clarity

Sections are well sequenced (Install → Running → Reporters → Authoring → CI), but a Newman run is a batch operation and the body has no inline validate→fix→retry checkpoint; verification is implicitly deferred to `--bail` and the offloaded CI workflow, capping this at 3 per the batch-operation guidance.

3 / 5

Progressive Disclosure

Clear overview with the full flag table, CI workflow YAML, and anti-pattern catalog split into a single one-level-deep, well-signaled references/newman-reference.md (verified to exist); easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

92%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.

A strong, specific description that clearly states both capabilities and an explicit Use-when trigger. The only weak spot is trigger-term phrasing: the opening repair-scenario lead-in is diagnostic rather than something a user would naturally say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Authors Postman collections (requests, tests, variables, environments), runs them headless via the Newman CLI, configures reporters (cli / json / junit / html) ... drives data-driven runs from JSON / CSV iteration files' — covering authoring, execution, reporting, and data-driven iteration comprehensively.

5 / 5

Completeness

Explicitly answers both what (authors/runs/configures reporters/drives data-driven runs) and when via a concrete 'Use when HTTP API tests are authored in Postman and need to run, pace themselves, and report correctly in CI.' clause.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Postman', 'Newman', 'CI', 'HTTP API tests', 'reporters', 'JSON / CSV'), but the lead-in diagnostic phrasing ('a reporter that never writes the HTML file the pipeline expects') is atypical trigger language and file extensions like .postman_collection.json are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Postman/Newman headless HTTP API testing in CI) with distinct triggers and minimal overlap with adjacent skills; the named alternatives in the body further bound its scope.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents