[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F9CMAQX9A13Z830HS4PC54":3,"skill-same:01M6F9CMAQX9A13Z830HS4PC54":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":25,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":38,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6F9CMAQX9A13Z830HS4PC54","newman-cicd-integration",null,"Generate ready-to-use CI\u002FCD pipeline configurations that install and run Newman for automated API testing.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-newman-cicd-integration\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"newman","integration","newman cicd integration","cicd","cicd integration","api testing","2026","tree","lambdatest","CI\u002FCD","critical","wed","main","community","testing","ready","install","api","pipeline","ci","license","run","generate","2026-11-10 10:12:30",false,"---\nname: newman-cicd-integration\ndescription: \"Generate ready-to-use CI\u002FCD pipeline configurations that install and run Newman for automated API testing.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Fapi-skill\u002Fnewman\u002Fnewman-cicd-helper\nsource_repo: LambdaTest\u002Fagent-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Newman CI\u002FCD Integration Generator\n## When to Use\n\nUse this skill when you need generate ready-to-use CI\u002FCD 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,...\n\n\nGenerate complete, copy-paste-ready CI\u002FCD pipeline configs that install Newman and run Postman collections as part of automated builds.\n\n---\n\n## What to Collect From the User\n\nBefore generating a config, determine:\n1. **CI platform** — GitHub Actions, GitLab CI, Jenkins, Azure DevOps, CircleCI, Bitbucket?\n2. **Collection source** — local file in repo, or Postman API URL?\n3. **Environment** — local env file in repo, or env vars injected by CI secrets?\n4. **Reporters needed** — JUnit XML (for CI test results panel), HTML report, or both?\n5. **Node.js version** preference (choose a currently supported version compatible with Newman)\n6. **Trigger** — on every push, pull request, schedule, or after deploy?\n7. **Fail build on test failure?** — almost always yes; confirm\n\n---\n\n## CI trust and credential handling\n\nReview collection scripts and target URLs before executing: Postman scripts and requests can exfiltrate secrets or mutate services. Run only authorized sandbox collections; never expose production credentials to untrusted pull requests. Pin dependencies\u002Factions using the project’s reviewed lockfile\u002Fcommit policy instead of copying moving global installs unchanged. OS environment variables do not automatically populate Postman variables: supply a protected temporary environment JSON via `-e` or an explicitly reviewed runner integration. Avoid real secret command arguments, shell tracing and request\u002Fresponse-rich public HTML artifacts; redact reports, restrict access\u002Fretention and remove temporary secrets. Required test failures must remain failures.\n\n## Platform Templates\n\n### GitHub Actions\n\n```yaml\nname: API Tests\n\non:\n  push:\n    branches: [main, develop]\n  pull_request:\n\njobs:\n  api-tests:\n    runs-on: ubuntu-latest\n\n    steps:\n      - name: Checkout repository\n        uses: actions\u002Fcheckout@v4\n\n      - name: Set up Node.js\n        uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: '22'\n\n      - name: Install Newman\n        run: |\n          npm install -g newman\n          npm install -g newman-reporter-htmlextra\n\n      - name: Run API tests\n        run: |\n          newman run .\u002Fcollections\u002Fmy-api.json \\\n            -e .\u002Fenvironments\u002Fstaging.json \\\n            -r cli,junit,htmlextra \\\n            --reporter-junit-export .\u002Fresults\u002Fjunit.xml \\\n            --reporter-htmlextra-export .\u002Fresults\u002Freport.html \\\n            --reporter-htmlextra-title \"API Test Results\"\n        env:\n          BASE_URL: ${{ secrets.BASE_URL }}\n          API_KEY: ${{ secrets.API_KEY }}\n\n      - name: Publish test results\n        uses: dorny\u002Ftest-reporter@v1\n        if: always()\n        with:\n          name: Newman API Tests\n          path: results\u002Fjunit.xml\n          reporter: java-junit\n\n      - name: Upload HTML report\n        uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: api-test-report\n          path: results\u002Freport.html\n```\n\n---\n\n### GitLab CI\n\n```yaml\nstages:\n  - test\n\napi-tests:\n  stage: test\n  image: node:22-alpine\n  before_script:\n    - npm install -g newman newman-reporter-htmlextra\n  script:\n    - |\n      newman run .\u002Fcollections\u002Fmy-api.json \\\n        -e .\u002Fenvironments\u002Fstaging.json \\\n        --env-var \"BASE_URL=$BASE_URL\" \\\n        -r cli,junit,htmlextra \\\n        --reporter-junit-export results\u002Fjunit.xml \\\n        --reporter-htmlextra-export results\u002Freport.html\n  artifacts:\n    when: always\n    reports:\n      junit: results\u002Fjunit.xml\n    paths:\n      - results\u002Freport.html\n    expire_in: 7 days\n  variables:\n    BASE_URL: $BASE_URL   # Set in GitLab CI\u002FCD > Variables\n    API_KEY: $API_KEY\n```\n\n---\n\n### Jenkins (Declarative Pipeline)\n\n```groovy\npipeline {\n  agent any\n\n  tools {\n    nodejs 'NodeJS-22'   \u002F\u002F Configure in Global Tool Configuration\n  }\n\n  stages {\n    stage('Install Newman') {\n      steps {\n        sh 'npm install -g newman newman-reporter-htmlextra'\n      }\n    }\n\n    stage('Run API Tests') {\n      steps {\n        sh '''\n          newman run .\u002Fcollections\u002Fmy-api.json \\\n            -e .\u002Fenvironments\u002Fstaging.json \\\n            -r cli,junit,htmlextra \\\n            --reporter-junit-export results\u002Fjunit.xml \\\n            --reporter-htmlextra-export results\u002Freport.html \\\n            --reporter-htmlextra-title \"API Tests - ${BUILD_NUMBER}\"\n        '''\n      }\n    }\n  }\n\n  post {\n    always {\n      junit 'results\u002Fjunit.xml'\n      publishHTML([\n        allowMissing: false,\n        alwaysLinkToLastBuild: true,\n        keepAll: true,\n        reportDir: 'results',\n        reportFiles: 'report.html',\n        reportName: 'Newman API Test Report'\n      ])\n    }\n  }\n}\n```\n\n---\n\n### Azure DevOps\n\n```yaml\ntrigger:\n  branches:\n    include:\n      - main\n\npool:\n  vmImage: 'ubuntu-latest'\n\nsteps:\n  - task: NodeTool@0\n    inputs:\n      versionSpec: '22.x'\n    displayName: 'Set up Node.js'\n\n  - script: |\n      npm install -g newman newman-reporter-htmlextra\n    displayName: 'Install Newman'\n\n  - script: |\n      newman run .\u002Fcollections\u002Fmy-api.json \\\n        -e .\u002Fenvironments\u002Fstaging.json \\\n        -r cli,junit,htmlextra \\\n        --reporter-junit-export $(System.DefaultWorkingDirectory)\u002Fresults\u002Fjunit.xml \\\n        --reporter-htmlextra-export $(System.DefaultWorkingDirectory)\u002Fresults\u002Freport.html\n    displayName: 'Run API Tests'\n    env:\n      API_KEY: $(API_KEY)   # Set in Pipeline > Variables\n\n  - task: PublishTestResults@2\n    condition: always()\n    inputs:\n      testResultsFormat: 'JUnit'\n      testResultsFiles: 'results\u002Fjunit.xml'\n      testRunTitle: 'Newman API Tests'\n\n  - task: PublishBuildArtifacts@1\n    condition: always()\n    inputs:\n      PathtoPublish: 'results\u002Freport.html'\n      ArtifactName: 'api-test-report'\n```\n\n---\n\n### CircleCI\n\n```yaml\nversion: 2.1\n\njobs:\n  api-tests:\n    docker:\n      - image: cimg\u002Fnode:22.0\n    steps:\n      - checkout\n      - run:\n          name: Install Newman\n          command: npm install -g newman newman-reporter-htmlextra\n      - run:\n          name: Run API Tests\n          command: |\n            mkdir -p results\n            newman run .\u002Fcollections\u002Fmy-api.json \\\n              -e .\u002Fenvironments\u002Fstaging.json \\\n              -r cli,junit,htmlextra \\\n              --reporter-junit-export results\u002Fjunit.xml \\\n              --reporter-htmlextra-export results\u002Freport.html\n      - store_test_results:\n          path: results\n      - store_artifacts:\n          path: results\u002Freport.html\n\nworkflows:\n  test:\n    jobs:\n      - api-tests\n```\n\n---\n\n## Best Practices\n\n### Secrets — never hardcode credentials\nAlways inject sensitive values as CI environment variables\u002Fsecrets:\n- GitHub: `Settings > Secrets and Variables > Actions`\n- GitLab: `Settings > CI\u002FCD > Variables`\n- Jenkins: `Manage Jenkins > Credentials`\n- Azure DevOps: `Pipelines > Variables`\n\nMaterialize a protected temporary Newman environment file using a trusted secret provider, then pass only its path with `-e`. Do not put actual secret values in --env-var process arguments. The examples assume that protected file has been prepared; remove it after the job and redact reports.\n\n### Store collection and environment files in the repo\n```\n\u002F\n├── collections\u002F\n│   └── my-api.json\n├── environments\u002F\n│   ├── staging.json\n│   └── prod.json\n└── results\u002F         ← gitignored, created by Newman\n```\n\nAdd `results\u002F` to `.gitignore`.\n\n### Always use `if: always()` \u002F `when: always`\nEnsure test result artifacts are published even when Newman exits with a failure code.\n\n### Exit codes\nNewman 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.\n\n---\n\n## How to Generate Configs\n\n1. Confirm the CI platform and tailor the exact syntax\n2. Use the correct secret\u002Fvariable injection syntax for that platform\n3. Include artifact publishing steps so test results appear in the CI UI\n4. Add comments explaining secrets that need to be configured\n5. Keep environment files in the repo (without secrets); inject sensitive values via CI vars\n\n---\n\n## After Completing the Newman CICD output\n\nOnce the Newman CICD output is delivered, ask the user:\n\n\"Would you like me to generate Postman Test Cases for these commands? (yes\u002Fno)\"\n\nIf the user says **yes**:\n- Check if the postman-testcase-generator skill is available in the installed skills list\n- If the skill **is available**:\n  - Read and follow the instructions in the postman-testcase-generator skill\n  - Use the CICD command output above as the input\n- If the skill **is NOT available**:\n  - Inform the user: \"It looks like the postman-testcase-generator skill isn't installed.\n    You can install it and re-run.\n\nIf the user says **no**:\n- End the task here\n\n---\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Newman CI\u002FCD Integration Generator\n## When to Use\n\nUse this skill when you need generate ready-to-use CI\u002FCD 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,...\n\n\nGenerate complete, copy-paste-ready CI\u002FCD pipeline configs that install Newman and run Postman collections as part of automated builds.\n\n---\n\n## What to Collect From the User\n\nBefore generating a config, determine:\n1. **CI platform** — GitHub Actions, GitLab CI, Jenkins, Azure DevOps, CircleCI, Bitbucket?\n2. **Collection source** — local file in repo, or Postman API URL?\n3. **Environment** — local env file in repo, or env vars injected by CI secrets?\n4. **Reporters needed** — JUnit XML (for CI test results panel), HTML report, or both?\n5. **Node.js version** preference (choose a currently supported version compatible with Newman)\n6. **Trigger** — on every push, pull request, schedule, or after deploy?\n7. **Fail build on test failure?** — almost always yes; confirm\n\n---\n\n## CI trust and credential handling\n\nReview collection scripts and target URLs before executing: Postman scripts and requests can exfiltrate secrets or mutate services. Run only authorized sandbox collections; never expose production credentials to untrusted pull requests. Pin dependencies\u002Factions using the project’s reviewed lockfile\u002Fcommit policy instead of copying moving global installs unchanged. OS environment variables do not automatically populate Postman variables: supply a protected temporary environment JSON via `-e` or an explicitly reviewed runner integration. Avoid real secret command arguments, shell tracing and request\u002Fresponse-rich public HTML artifacts; redact reports, restrict access\u002Fretention and remove temporary secrets. Required test failures must remain failures.\n\n## Platform Templates\n\n### GitHub Actions\n\n```yaml\nname: API Tests\n\non:\n  push:\n    branches: [main, develop]\n  pull_request:\n\njobs:\n  api-tests:\n    runs-on: ubuntu-latest\n\n    steps:\n      - name: Checkout repository\n        uses: actions\u002Fcheckout@v4\n\n      - name: Set up Node.js\n        uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: '22'\n\n      - name: Install Newman\n        run: |\n          npm install -g newman\n          npm install -g newman-reporter-htmlextra\n\n      - name: Run API tests\n        run: |\n          newman run .\u002Fcollections\u002Fmy-api.json \\\n            -e .\u002Fenvironments\u002Fstaging.json \\\n            -r cli,junit,htmlextra \\\n            --reporter-junit-export .\u002Fresults\u002Fjunit.xml \\\n            --reporter-htmlextra-export .\u002Fresults\u002Freport.html \\\n            --reporter-htmlextra-title \"API Test Results\"\n        env:\n          BASE_URL: ${{ secrets.BASE_URL }}\n          API_KEY: ${{ secrets.API_KEY }}\n\n      - name: Publish test results\n        uses: dorny\u002Ftest-reporter@v1\n        if: always()\n        with:\n          name: Newman API Tests\n          path: results\u002Fjunit.xml\n          reporter: java-junit\n\n      - name: Upload HTML report\n        uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: api-test-report\n          path: results\u002Freport.html\n```\n\n---\n\n### GitLab CI\n\n```yaml\nstages:\n  - test\n\napi-tests:\n  stage: test\n  image: node:22-alpine\n  before_script:\n    - npm install -g newman newman-reporter-htmlextra\n  script:\n    - |\n      newman run .\u002Fcollections\u002Fmy-api.json \\\n        -e .\u002Fenvironments\u002Fstaging.json \\\n        --env-var \"BASE_URL=$BASE_URL\" \\\n        -r cli,junit,htmlextra \\\n        --reporter-junit-export results\u002Fjunit.xml \\\n        --reporter-htmlextra-export results\u002Freport.html\n  artifacts:\n    when: always\n    reports:\n      junit: results\u002Fjunit.xml\n    paths:\n      - results\u002Freport.html\n    expire_in: 7 days\n  variables:\n    BASE_URL: $BASE_URL   # Set in GitLab CI\u002FCD > Variables\n    API_KEY: $API_KEY\n```\n\n---\n\n### Jenkins (Declarative Pipeline)\n\n```groovy\npipeline {\n  agent any\n\n  tools {\n    nodejs 'NodeJS-22'   \u002F\u002F Configure in Global Tool Configuration\n  }\n\n  stages {\n    stage('Install Newman') {\n      steps {\n        sh 'npm install -g newman newman-reporter-htmlextra'\n      }\n    }\n\n    stage('Run API Tests') {\n      steps {\n        sh '''\n          newman run .\u002Fcollections\u002Fmy-api.json \\\n            -e .\u002Fenvironments\u002Fstaging.json \\\n            -r cli,junit,htmlextra \\\n            --reporter-junit-export results\u002Fjunit.xml \\\n            --reporter-htmlextra-export results\u002Freport.html \\\n            --reporter-htmlextra-title \"API Tests - ${BUILD_NUMBER}\"\n        '''\n      }\n    }\n  }\n\n  post {\n    always {\n      junit 'results\u002Fjunit.xml'\n      publishHTML([\n        allowMissing: false,\n        alwaysLinkToLastBuild: true,\n        keepAll: true,\n        reportDir: 'results',\n        reportFiles: 'report.html',\n        reportName: 'Newman API Test Report'\n      ])\n    }\n  }\n}\n```\n\n---\n\n### Azure DevOps\n\n```yaml\ntrigger:\n  branches:\n    include:\n      - main\n\npool:\n  vmImage: 'ubuntu-latest'\n\nsteps:\n  - task: NodeTool@0\n    inputs:\n      versionSpec: '22.x'\n    displayName: 'Set up Node.js'\n\n  - script: |\n      npm install -g newman newman-reporter-htmlextra\n    displayName: 'Install Newman'\n\n  - script: |\n      newman run .\u002Fcollections\u002Fmy-api.json \\\n        -e .\u002Fenvironments\u002Fstaging.json \\\n        -r cli,junit,htmlextra \\\n        --reporter-junit-export $(System.DefaultWorkingDirectory)\u002Fresults\u002Fjunit.xml \\\n        --reporter-htmlextra-export $(System.DefaultWorkingDirectory)\u002Fresults\u002Freport.html\n    displayName: 'Run API Tests'\n    env:\n      API_KEY: $(API_KEY)   # Set in Pipeline > Variables\n\n  - task: PublishTestResults@2\n    condition: always()\n    inputs:\n      testResultsFormat: 'JUnit'\n      testResultsFiles: 'results\u002Fjunit.xml'\n      testRunTitle: 'Newman API Tests'\n\n  - task: PublishBuildArtifacts@1\n    condition: always()\n    inputs:\n      PathtoPublish: 'results\u002Freport.html'\n      ArtifactName: 'api-test-report'\n```\n\n---\n\n### CircleCI\n\n```yaml\nversion: 2.1\n\njobs:\n  api-tests:\n    docker:\n      - image: cimg\u002Fnode:22.0\n    steps:\n      - checkout\n      - run:\n          name: Install Newman\n          command: npm install -g newman newman-reporter-htmlextra\n      - run:\n          name: Run API Tests\n          command: |\n            mkdir -p results\n            newman run .\u002Fcollections\u002Fmy-api.json \\\n              -e .\u002Fenvironments\u002Fstaging.json \\\n              -r cli,junit,htmlextra \\\n              --reporter-junit-export results\u002Fjunit.xml \\\n              --reporter-htmlextra-export results\u002Freport.html\n      - store_test_results:\n          path: results\n      - store_artifacts:\n          path: results\u002Freport.html\n\nworkflows:\n  test:\n    jobs:\n      - api-tests\n```\n\n---\n\n## Best Practices\n\n### Secrets — never hardcode credentials\nAlways inject sensitive values as CI environment variables\u002Fsecrets:\n- GitHub: `Settings > Secrets and Variables > Actions`\n- GitLab: `Settings > CI\u002FCD > Variables`\n- Jenkins: `Manage Jenkins > Credentials`\n- Azure DevOps: `Pipelines > Variables`\n\nMaterialize a protected temporary Newman environment file using a trusted secret provider, then pass only its path with `-e`. Do not put actual secret values in --env-var process arguments. The examples assume that protected file has been prepared; remove it after the job and redact reports.\n\n### Store collection and environment files in the repo\n```\n\u002F\n├── collections\u002F\n│   └── my-api.json\n├── environments\u002F\n│   ├── staging.json\n│   └── prod.json\n└── results\u002F         ← gitignored, created by Newman\n```\n\nAdd `results\u002F` to `.gitignore`.\n\n### Always use `if: always()` \u002F `when: always`\nEnsure test result artifacts are published even when Newman exits with a failure code.\n\n### Exit codes\nNewman 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.\n\n---\n\n## How to Generate Configs\n\n1. Confirm the CI platform and tailor the exact syntax\n2. Use the correct secret\u002Fvariable injection syntax for that platform\n3. Include artifact publishing steps so test results appear in the CI UI\n4. Add comments explaining secrets that need to be configured\n5. Keep environment files in the repo (without secrets); inject sensitive values via CI vars\n\n---\n\n## After Completing the Newman CICD output\n\nOnce the Newman CICD output is delivered, ask the user:\n\n\"Would you like me to generate Postman Test Cases for these commands? (yes\u002Fno)\"\n\nIf the user says **yes**:\n- Check if the postman-testcase-generator skill is available in the installed skills list\n- If the skill **is available**:\n  - Read and follow the instructions in the postman-testcase-generator skill\n  - Use the CICD command output above as the input\n- If the skill **is NOT available**:\n  - Inform the user: \"It looks like the postman-testcase-generator skill isn't installed.\n    You can install it and re-run.\n\nIf the user says **no**:\n- End the task here\n\n---\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":36,"source":54,"license":14,"date_added":55,"description":7,"source_repo":56,"source_type":39,"license_source":57},"https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Fapi-skill\u002Fnewman\u002Fnewman-cicd-helper",1782864000000,"LambdaTest\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-newman-cicd-integration",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-13 14:20:47",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add boisenoise\u002Fskills-collections --skill newman-cicd-integration",{"tool":70,"command":71},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill newman-cicd-integration",{"tool":73,"command":74},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill newman-cicd-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-newman-cicd-integration\u002FSKILL.md",true,[],[79,107,132,158,177,200],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":49},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,36,103,104,105,106,32],"web","access","web access","official","development","browser","search","data","Tools","read","fetch","only","youtube","free tools","platform","free","cover","normal","when",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":117,"publishedAt":49},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[109,118,119,120,91,92,46,96,121,122,123,124,125,126,127,36,128,129,130,131,32],"MCP","cli","github","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped","blob",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":144,"publishedAt":49},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[134,120,91,46,145,146,147,148,149,150,36,151,152,153,129,154,155,156,157,131,109,32],"https","email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":49},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[166,167,168,120,91,46,169,170,145,171,121,172,173,174,149,36,175,176,131,109,32],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":181,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":49},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[185,186,120,187,91,188,46,189,190,191,192,193,36,194,195,196,197,198,199,131],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":204,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":49},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[208,209,210,120,91,46,211,212,148,41,213,36,214,215,216,217,218,219,220,131],"signals","lead","lead signals","how","find","as","how to","qualify","people","information","enrich","changes","funding"]