[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A719M4Z2ZT4GSCBKW8P73S":3,"skill-same:01M7A719M4Z2ZT4GSCBKW8P73S":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7A719M4Z2ZT4GSCBKW8P73S","newman-cicd-integration",null,"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,...","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fnewman-cicd-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: newman-cicd-integration\ndescription: 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,...\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 (default: 18)\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## 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: '18'\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:18-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        --env-var \"API_KEY=$API_KEY\" \\\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-18'   \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: '18.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        --env-var \"API_KEY=$(API_KEY)\" \\\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:18.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              --env-var \"API_KEY=$API_KEY\" \\\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\nReference in Newman via `--env-var \"KEY=$SECRET_NAME\"` or pre-set in the environment file.\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 (default: 18)\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## 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: '18'\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:18-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        --env-var \"API_KEY=$API_KEY\" \\\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-18'   \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: '18.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        --env-var \"API_KEY=$(API_KEY)\" \\\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:18.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              --env-var \"API_KEY=$API_KEY\" \\\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\nReference in Newman via `--env-var \"KEY=$SECRET_NAME\"` or pre-set in the environment file.\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":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Fapi-skill\u002Fnewman\u002Fnewman-cicd-helper",1782864000000,"LambdaTest\u002Fagent-skills","community","https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fnewman-cicd-integration",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add MHassan0000\u002FSkills --skill newman-cicd-integration",{"tool":45,"command":46},"bunx","bunx skills add MHassan0000\u002FSkills --skill newman-cicd-integration",{"tool":48,"command":49},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill newman-cicd-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fnewman-cicd-integration\u002FSKILL.md",true,[],[54,61,68,75,84,92],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]