[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DNJE690T2QPTFMRZTHFBCG":3,"skill-same:01M7DNJE690T2QPTFMRZTHFBCG":51},{"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":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DNJE690T2QPTFMRZTHFBCG","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,...","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\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: unknown\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},"unknown","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","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fnewman-cicd-integration",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill newman-cicd-integration",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill newman-cicd-integration",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill newman-cicd-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fnewman-cicd-integration\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]