Agent skill

Newman Cicd Integration

by sickn33 in sickn33/agentic-awesome-skills

Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing.

MITAuto-check passedDevOps & Cloud

Install Newman Cicd Integration

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill newman-cicd-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills newman-cicd-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/newman-cicd-integration .claude/skills/newman-cicd-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
newman-cicd-integration
GitHub stars
47k
Used in
1 other repo
Token cost
~2.2k tokens
SKILL.md length
498 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing.

  • Works in 7 steps: CI platform — GitHub Actions, GitLab CI,… → Collection source — local file in repo,… → Environment — local env file in repo, or… → …
  • Tasks that involve CI/CD
  • SKILL.md covers When to Use, What to Collect From the User, Platform Templates and Best Practices, plus 3 more sections
  • Needs API_KEY

What it does

Newman Cicd Integration is an agent skill from sickn33/agentic-awesome-skills. Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering CI/CD and API testing. It works with GitLab, Jenkins, Azure DevOps and GitHub Actions. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve CI/CD
  • Tasks that involve API testing

Example prompts

  • “/newman-cicd-integration”

Requirements

  • Node.js
  • Docker
  • A credential in API_KEY

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. CI platform — GitHub Actions, GitLab CI, Jenkins, Azure DevOps, CircleCI, Bitbucket?
  2. Collection source — local file in repo, or Postman API URL?
  3. Environment — local env file in repo, or env vars injected by CI secrets?
  4. Reporters needed — JUnit XML (for CI test results panel), HTML report, or both?
  5. Node.js version preference (default: 18)
  6. Trigger — on every push, pull request, schedule, or after deploy?
  7. Fail build on test failure? — almost always yes; confirm

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and groovy).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Newman Cicd Integration loads about 2.2k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 498 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 498 words, ~2,233 tokens.

Download SKILL.mdSave it as .claude/skills/newman-cicd-integration/SKILL.md (or your agent's skills folder).
name
newman-cicd-integration
description
Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing.
risk
critical
source
https://github.com/LambdaTest/agent-skills/tree/main/api-skill/newman/newman-cicd-helper
source_repo
LambdaTest/agent-skills
source_type
community
date_added
2026-07-01
license
MIT
license_source
https://github.com/LambdaTest/agent-skills/blob/main/LICENSE

Newman CI/CD Integration Generator

When to Use

Use this skill when you need generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing. Use this skill whenever the user wants to run Newman in a CI pipeline, integrate Postman collections into automated builds, set up API tests in GitHub Actions, GitLab CI, Jenkins,...

Generate complete, copy-paste-ready CI/CD pipeline configs that install Newman and run Postman collections as part of automated builds.


What to Collect From the User

Before generating a config, determine:

  1. CI platform — GitHub Actions, GitLab CI, Jenkins, Azure DevOps, CircleCI, Bitbucket?
  2. Collection source — local file in repo, or Postman API URL?
  3. Environment — local env file in repo, or env vars injected by CI secrets?
  4. Reporters needed — JUnit XML (for CI test results panel), HTML report, or both?
  5. Node.js version preference (default: 18)
  6. Trigger — on every push, pull request, schedule, or after deploy?
  7. Fail build on test failure? — almost always yes; confirm

Platform Templates

GitHub Actions
yaml
name: API Tests

on:
  push:
    branches: [main, develop]
  pull_request:

jobs:
  api-tests:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Set up Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '18'

      - name: Install Newman
        run: |
          npm install -g newman
          npm install -g newman-reporter-htmlextra

      - name: Run API tests
        run: |
          newman run ./collections/my-api.json \
            -e ./environments/staging.json \
            -r cli,junit,htmlextra \
            --reporter-junit-export ./results/junit.xml \
            --reporter-htmlextra-export ./results/report.html \
            --reporter-htmlextra-title "API Test Results"
        env:
          BASE_URL: ${{ secrets.BASE_URL }}
          API_KEY: ${{ secrets.API_KEY }}

      - name: Publish test results
        uses: dorny/test-reporter@v1
        if: always()
        with:
          name: Newman API Tests
          path: results/junit.xml
          reporter: java-junit

      - name: Upload HTML report
        uses: actions/upload-artifact@v4
        if: always()
        with:
          name: api-test-report
          path: results/report.html

GitLab CI
yaml
stages:
  - test

api-tests:
  stage: test
  image: node:18-alpine
  before_script:
    - npm install -g newman newman-reporter-htmlextra
  script:
    - |
      newman run ./collections/my-api.json \
        -e ./environments/staging.json \
        --env-var "BASE_URL=$BASE_URL" \
        --env-var "API_KEY=$API_KEY" \
        -r cli,junit,htmlextra \
        --reporter-junit-export results/junit.xml \
        --reporter-htmlextra-export results/report.html
  artifacts:
    when: always
    reports:
      junit: results/junit.xml
    paths:
      - results/report.html
    expire_in: 7 days
  variables:
    BASE_URL: $BASE_URL   # Set in GitLab CI/CD > Variables
    API_KEY: $API_KEY

Jenkins (Declarative Pipeline)
groovy
pipeline {
  agent any

  tools {
    nodejs 'NodeJS-18'   // Configure in Global Tool Configuration
  }

  stages {
    stage('Install Newman') {
      steps {
        sh 'npm install -g newman newman-reporter-htmlextra'
      }
    }

    stage('Run API Tests') {
      steps {
        sh '''
          newman run ./collections/my-api.json \
            -e ./environments/staging.json \
            -r cli,junit,htmlextra \
            --reporter-junit-export results/junit.xml \
            --reporter-htmlextra-export results/report.html \
            --reporter-htmlextra-title "API Tests - ${BUILD_NUMBER}"
        '''
      }
    }
  }

  post {
    always {
      junit 'results/junit.xml'
      publishHTML([
        allowMissing: false,
        alwaysLinkToLastBuild: true,
        keepAll: true,
        reportDir: 'results',
        reportFiles: 'report.html',
        reportName: 'Newman API Test Report'
      ])
    }
  }
}

Azure DevOps
yaml
trigger:
  branches:
    include:
      - main

pool:
  vmImage: 'ubuntu-latest'

steps:
  - task: NodeTool@0
    inputs:
      versionSpec: '18.x'
    displayName: 'Set up Node.js'

  - script: |
      npm install -g newman newman-reporter-htmlextra
    displayName: 'Install Newman'

  - script: |
      newman run ./collections/my-api.json \
        -e ./environments/staging.json \
        --env-var "API_KEY=$(API_KEY)" \
        -r cli,junit,htmlextra \
        --reporter-junit-export $(System.DefaultWorkingDirectory)/results/junit.xml \
        --reporter-htmlextra-export $(System.DefaultWorkingDirectory)/results/report.html
    displayName: 'Run API Tests'
    env:
      API_KEY: $(API_KEY)   # Set in Pipeline > Variables

  - task: PublishTestResults@2
    condition: always()
    inputs:
      testResultsFormat: 'JUnit'
      testResultsFiles: 'results/junit.xml'
      testRunTitle: 'Newman API Tests'

  - task: PublishBuildArtifacts@1
    condition: always()
    inputs:
      PathtoPublish: 'results/report.html'
      ArtifactName: 'api-test-report'

CircleCI
yaml
version: 2.1

jobs:
  api-tests:
    docker:
      - image: cimg/node:18.0
    steps:
      - checkout
      - run:
          name: Install Newman
          command: npm install -g newman newman-reporter-htmlextra
      - run:
          name: Run API Tests
          command: |
            mkdir -p results
            newman run ./collections/my-api.json \
              -e ./environments/staging.json \
              --env-var "API_KEY=$API_KEY" \
              -r cli,junit,htmlextra \
              --reporter-junit-export results/junit.xml \
              --reporter-htmlextra-export results/report.html
      - store_test_results:
          path: results
      - store_artifacts:
          path: results/report.html

workflows:
  test:
    jobs:
      - api-tests

Best Practices

Secrets — never hardcode credentials

Always inject sensitive values as CI environment variables/secrets:

  • GitHub: Settings > Secrets and Variables > Actions
  • GitLab: Settings > CI/CD > Variables
  • Jenkins: Manage Jenkins > Credentials
  • Azure DevOps: Pipelines > Variables

Reference in Newman via --env-var "KEY=$SECRET_NAME" or pre-set in the environment file.

Store collection and environment files in the repo
/
├── collections/
│   └── my-api.json
├── environments/
│   ├── staging.json
│   └── prod.json
└── results/         ← gitignored, created by Newman

Add results/ to .gitignore.

Always use if: always() / when: always

Ensure test result artifacts are published even when Newman exits with a failure code.

Exit codes

Newman exits with code 1 if any tests fail — this automatically fails the pipeline step. Use --bail if you want to stop on the first failure rather than running all tests.


Show full SKILL.md (213 more words)Show less

How to Generate Configs

  1. Confirm the CI platform and tailor the exact syntax
  2. Use the correct secret/variable injection syntax for that platform
  3. Include artifact publishing steps so test results appear in the CI UI
  4. Add comments explaining secrets that need to be configured
  5. Keep environment files in the repo (without secrets); inject sensitive values via CI vars

After Completing the Newman CICD output

Once the Newman CICD output is delivered, ask the user:

"Would you like me to generate Postman Test Cases for these commands? (yes/no)"

If the user says yes:

  • Check if the postman-testcase-generator skill is available in the installed skills list
  • If the skill is available:
    • Read and follow the instructions in the postman-testcase-generator skill
    • Use the CICD command output above as the input
  • If the skill is NOT available:
    • Inform the user: "It looks like the postman-testcase-generator skill isn't installed. You can install it and re-run.

If the user says no:

  • End the task here

Limitations

  • Use this skill only when the task clearly matches its upstream source and local project context.
  • Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
  • Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/newman-cicd-integration of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Newman Cicd Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Newman Cicd Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Newman Cicd Integration this skillsickn33/agentic-awesome-skills47k1 repos~2.2kAutomated safety check: PassMIT
Tirith PoliciesStackGuardian/tirith170—~1.8kAutomated safety check: PassApache-2.0
Playwright CIzebbern/claude-code-guide4.7k2 repos~675Automated safety check: PassMIT
Megalinter Checknvuillam/npm-groovy-lint2481 repos~3.9kAutomated safety check: NotesMIT
Authoring GitHub Workflowsdotnet/skills5.6k1 repos~2.3kAutomated safety check: PassMIT
CI CDRightNow-AI/openfang18k—~691Automated safety check: PassApache-2.0

Similar skills

  • Tirith Policies

    StackGuardian/tirith

    Write, validate, run and debug Tirith IaC governance policies, install Tirith, and add it to a CI pipeline (GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins, Azure DevOps, CircleCI or any…

    170 GitHub stars~1.8k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Playwright CI

    zebbern/claude-code-guide

    Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

    4.7k GitHub starsUsed in 2 repos~675 tokens
    DevOps & CloudAuto-check passed
  • Megalinter Check

    nvuillam/npm-groovy-lint

    Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.

    248 GitHub starsUsed in 1 repo~3.9k tokens
    DevOps & CloudAuto-check: notes
  • Official

    Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run.

    5.6k GitHub starsUsed in 1 repo~2.3k tokens
    DevOps & CloudAuto-check passed
  • CI CD

    RightNow-AI/openfang

    CI/CD pipeline expert for GitHub Actions, GitLab CI, Jenkins, and deployment automation

    18k GitHub stars~691 tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed
  • Building CI Pipelines

    ancoleman/ai-design-components

    Constructs secure, efficient CI/CD pipelines with supply chain security (SLSA), monorepo optimization, caching strategies, and parallelization patterns for GitHub Actions, GitLab CI, and Argo…

    525 GitHub stars~2.7k tokensUpdated 10 mo ago
    DevOps & CloudAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Newman Cicd Integration

What does Newman Cicd Integration do?

Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing. Newman Cicd Integration is an agent skill from sickn33/agentic-awesome-skills. Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing.

When should I use Newman Cicd Integration?

Newman Cicd Integration fits situations like: tasks that involve CI/CD; tasks that involve API testing.

How do I install Newman Cicd Integration in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill newman-cicd-integration -a claude-code`. Or copy the skill folder (skills/newman-cicd-integration in sickn33/agentic-awesome-skills) into .claude/skills/newman-cicd-integration in your project. Claude Code loads it when a task matches its description.

How do I install Newman Cicd Integration in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill newman-cicd-integration -a codex`. Or copy the skill folder (skills/newman-cicd-integration in sickn33/agentic-awesome-skills) into .agents/skills/newman-cicd-integration in your project. Codex loads it when a task matches its description.

Can I use Newman Cicd Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill newman-cicd-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/newman-cicd-integration, .gemini/skills/newman-cicd-integration, .github/skills/newman-cicd-integration and .opencode/skills/newman-cicd-integration in your project.

What does Newman Cicd Integration need to run?

Going by SKILL.md and its folder, Newman Cicd Integration needs credentials named API_KEY. Our summary lists: Node.js; Docker; A credential in API_KEY.

Does Newman Cicd Integration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Newman Cicd Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Newman Cicd Integration use?

Newman Cicd Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Newman Cicd Integration use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Newman Cicd Integration?

Skills that share tags, products or a category with Newman Cicd Integration: Tirith Policies (StackGuardian/tirith, 170 stars), Playwright CI (zebbern/claude-code-guide, 4.7k stars), Megalinter Check (nvuillam/npm-groovy-lint, 248 stars) and Authoring GitHub Workflows (dotnet/skills, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Newman Cicd Integration?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.